As its beta-2 already, we should be working towards a 1.0 version. I will put down a list of interface elements that need to be finished before we throw out a 1.0. Boombatower can you say what you need to do before a 1.0 code wise?

  1. Participant UI
  2. Creating a study UI
  3. Analyze Dashboard
  4. Analyze Participant

All of the other interfaces still need quite some work, but are not necessary in need of a lot of work to serve there goal.

Comments

boombatower’s picture

Codewise I think it is were I want it to be.

Bojhan’s picture

One notion on the code which I do think is necessary, when you create a task you have to save, and then record. Is it possible to this at once, so as you create a task you somehow save it(AJAX?), so you don't have to click save, in order to record a task. Because its kind of a broken interaction, which I think should be solved - for me to push the create a study page.

boombatower’s picture

Status: Active » Postponed (maintainer needs more info)

I have some time away from school and I will attempt to get everything that needs to be done for 1.0 and possible more if I have time. Can we patch up what you are looking to have done with issues so that I know what to complete.

#2: I'm not sure that creates a more consistent interface since that adds a number of edge-cases. For instance when you press record the task is "save"? or just kinda hanging there waiting for you to finish recording? If I were to decided I don't want to create the task and navigate away and then come back to create a task should it fill in the previous values? Not to mentions the extra/interesting code that would need to be written to accomplish something like that. I would vote for leaving it alone until we have a better idea, especially with #351460: Record ideal path in base environment if specified

Please confirm the issues and provide any corrections.

Bojhan’s picture

Participant UI has upmost priority, after that Creating a Study UI #320222: Create a study/task workflow - not 307846. Both should have finished mockups in them (if you need the PSD's ping skilip on IRC)

Analyze Dashboard
Study Dashboard #307946: Study Dashboard
Task Dashboard
Particpant Analysis (Leave this one for later - you can display what we do now the form data, and paths)

#2 Well the thing is, no one will press Save before Record unless we implicitly tell them to - its a counter intuitive interaction. So saving the task when you click record - for the user looks like the same thing (they will complete the form anyway). For the edge case that they don't, I think its a trade off we have to make (for now atleast).

Bojhan’s picture

Sounds right, with the how-to I will only cover Creating a study and part of the participant ui. Not the Analyze UI.

webchick’s picture

How the heck was I not subscribed to this?! Subscribe. :)

boombatower’s picture

If we decide to hold on #320222: Create a study/task workflow as I'm not sure we have a workable solution, and may take a bit to figure out how we want it to work then I can release a 1.0.

So Bojhan please respond on that issue and if we hold on it then go ahead with the screencast.

boombatower’s picture

I can role a all-in-one tar.gz to make it easier to get dependencies.

Although I think ideally we should try and get something like usability.drupal.org or uts.drupal.org with this setup so that global (Drupal) studies can be conducted in one place.

Bojhan’s picture

If you can roll a all-in-one tar.gz it would be great, not sure how far we can get that second idea yet.

boombatower’s picture

I have rolled a release candidate 1.

I currently do not have the time to implement the kind of ajax interface requested for study/task management. The system works perfectly fine currently and since it will primarily be used by Bojhan and others who should be able to understand the much improved work flow I think we can make a release candidate.

@bojhan: If you are fine with calling this a 1.0 then go ahead and create the howto screencast to be included in 1.0 release.

Bojhan’s picture

I am currently deeply busy with planning and organising the usability sprint, but I think you can roll a 1.0 without the screencast. I simply don't have time to do one right now, and I dont think its worthwhile to make a screencast on an interface that is not ready yet.

boombatower’s picture

Assigned: Bojhan » boombatower
Status: Postponed (maintainer needs more info) » Fixed

As we discussed in previous IRC chats, the study UI will be included in UTS 1.1. This seems like the proper way since we have a fully functioning suite with a RC which should contain all features.

I have completed all other issues, per #5. We just need the #351500: Create howto screencast before I can release.

EDIT: I guess it could be an annoyance to have to create the screencast again, so I'll just hold off on 1.0 and we can break the RC protocol.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.