Investigation on alternative views of data

[saloynton]

A mini-investigation to question the possible alternative views of data that could be provided within the context of Calendar-Trac Timeline-Images Tab. As well as questioning the different layouts that this could involve. This investigation will be completed before going back to scientists for feedback.

• A scenario the history view should look to be able to cater for

Referenced from the and the discussion on the forum on the access to the original metadata from script:
"People importing their data for the first time get hundred of images in one week, which is not very practical to sort them out. That's why I'd like to let them "adjust" the import date."

[cxallan]

Moved from sprint 2011-04-07 (9)

[saloynton]

Referencing ticket #3777 has changed sprint.

[saloynton]

A couple of draft ideas

[saloynton]

There is a couple of ideas that require some discussion.

[saloynton]

Additional material at - ​http://ui-patterns.com/patterns/CalendarPicker

[saloynton]

• A summary of some general issues to consider

• Event driven or planning calendar

The use of the calendar looks like it will have to be defined in terms of being a event driven calendar (i.e. this is when the import occurred) there is and must be a clear distinction to a planning driven calendar (i.e. google calendar).

For event driven calendars start times are more relevant, how applicable this might be to an import time would again need to be explored?

• Presentation of information

Make it easy for to scan an event based on the data that is important for the types of events you list.
This may include the ability to provide sort on options of the projects/datasets/images through the annotations made on them i.e. rating, comments,tags etc.
A general question for a user in presenting data, the more data that is held in particular projects/datasets is such an import more important than another if so this could be highlighted.

This becomes more and more important when there is a lot of data

If the subsequent list of import information is too big to show, we can further consider we can part it up based on either time constraints (buckets of time) or other annotation data.

See ​http://ui-patterns.com/blog/Design-considerations-for-event-calendars for full details.

[saloynton]

Further possible ideas to consider

[saloynton]

I have added some extra time to this to generate a few more ideas from the screenshots gathered.

[saloynton]

Given the focus for the next sprint (7) of the documentation smaller concepts/bit of information shall be added so that it may be reviewed for sprint (8).

[saloynton]

Josh if possible it would be useful to ask you a few questions on this while you are here.

[jburel]

Moved from sprint 2012-02-14 (8)

[jmoore]

Scott, sorry. I don't think we got a chance to cover this. Let me know when we should skype.

[saloynton]

Josh, the key points for this will be dealt with in Dom's presentation on the 21st Feb, so you can raise any initial questions then.

[jburel]

Moved from sprint 2012-02-28 (9)

[saloynton]

Josh: I will update the user story with the information Dom presented for searching and several of options and background information from the existing UX patterns for searching. The work can then be picked up after 4.4.

[saloynton]

Pulling together the information gathered into a pdf to put into the user story.

[saloynton]

There is a set of existing information that this work can pick up from:

• ​http://ui-patterns.com/patterns/LiveFilter
• ​http://www.slideshare.net/morville/search-patterns
• ​http://www.flickr.com/photos/morville/collections/72157603785835882/

Given Dom's search concepts and several of the attached design patterns looking at the variation on the searching data questions

• Given that this work will not come in for 4.4 it will be moved out of the milestone.

Next Action: Before arranging a mini group meeting on search after the 4.4. release I shall put together a collection of
examples to discuss against Dom's work to refine any more investigation work. The aim then is to be able support and reflect back into the necessary technical/infrastructure required for search.

[saloynton]

Closing task moved information into a word doc and up into the story.