Task #4687 (closed)

Opened 3 years ago

Last modified 2 years ago

Investigation on alternative views of data

Reported by: saloynton Owned by:
Priority: minor Milestone: Usability Backlog
Component: Search Version: n.a.
Keywords: n.a. Cc: wmoore, atarkowska, jburel, jamoore, dgaudioso
Remaining Time: 0.0d Sprint: n.a.
Resources: n.a. References: n.a.
Referenced By: n.a.

Description (last modified by saloynton) (diff)

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."

References

Attachments

flickr calendar.png Download (393.0 KB) - added by saloynton 2 years ago.
flickr calendar 2.png Download (340.6 KB) - added by saloynton 2 years ago.
Google web history activity.png Download (112.1 KB) - added by saloynton 2 years ago.
alternative views of image history.graffle.zip Download (1.3 MB) - added by saloynton 2 years ago.
A couple of draft ideas
bbc schedule viewer.png Download (106.7 KB) - added by saloynton 2 years ago.
carhartt-streetwear com.png Download (244.2 KB) - added by saloynton 2 years ago.
Further possible ideas to consider
motigo com.png Download (121.2 KB) - added by saloynton 2 years ago.
teehanlax com.png Download (109.6 KB) - added by saloynton 2 years ago.
calendar yahoo com.png Download (189.5 KB) - added by saloynton 2 years ago.
jide fr.png Download (123.0 KB) - added by saloynton 2 years ago.
la everyblock com.png Download (195.3 KB) - added by saloynton 2 years ago.
boxes & arrows calendar.png Download (91.0 KB) - added by saloynton 2 years ago.
lastfm events.png Download (97.2 KB) - added by saloynton 2 years ago.
cphdox.dk.png Download (286.6 KB) - added by saloynton 2 years ago.
talks and lectures for londoners.png Download (144.6 KB) - added by saloynton 2 years ago.

Change History

comment:1 Changed 3 years ago by cxallan

  • Sprint changed from 2011-04-07 (9) to 2011-04-21 (10)

Moved from sprint 2011-04-07 (9)

comment:2 Changed 3 years ago by saloynton

  • Sprint 2011-04-21 (10) deleted
  • Milestone changed from OMERO-Beta4.3 to Unscheduled

comment:3 Changed 3 years ago by jburel

  • Milestone changed from Unscheduled to Usability Backlog

comment:4 Changed 3 years ago by saloynton

Referencing ticket #3777 has changed sprint.

Changed 2 years ago by saloynton

Changed 2 years ago by saloynton

comment:5 Changed 2 years ago by saloynton

  • Description modified (diff)

comment:6 Changed 2 years ago by saloynton

  • Description modified (diff)

comment:7 Changed 2 years ago by saloynton

  • Sprint set to 2012-01-17 (6)
  • Milestone changed from Usability Backlog to OMERO-Beta4.4

Changed 2 years ago by saloynton

comment:8 Changed 2 years ago by saloynton

  • Description modified (diff)

comment:9 Changed 2 years ago by saloynton

  • Status changed from new to accepted

Changed 2 years ago by saloynton

A couple of draft ideas

comment:10 Changed 2 years ago by saloynton

  • Owner saloynton deleted
  • Status changed from accepted to new

comment:11 Changed 2 years ago by saloynton

  • Owner set to saloynton
  • Remaining Time changed from 0.75 to 0.25

comment:12 Changed 2 years ago by saloynton

There is a couple of ideas that require some discussion.

Changed 2 years ago by saloynton

comment:13 Changed 2 years ago by saloynton

comment:14 Changed 2 years ago by 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.

Last edited 2 years ago by saloynton (previous) (diff)

comment:15 Changed 2 years ago by saloynton

  • Status changed from new to accepted

Changed 2 years ago by saloynton

Further possible ideas to consider

Changed 2 years ago by saloynton

Changed 2 years ago by saloynton

Changed 2 years ago by saloynton

Changed 2 years ago by saloynton

Changed 2 years ago by saloynton

Changed 2 years ago by saloynton

Changed 2 years ago by saloynton

Changed 2 years ago by saloynton

Changed 2 years ago by saloynton

comment:16 Changed 2 years ago by saloynton

  • Owner saloynton deleted
  • Status changed from accepted to new

comment:17 Changed 2 years ago by saloynton

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

comment:18 Changed 2 years ago by saloynton

  • Owner set to saloynton
  • Remaining Time changed from 0.25 to 0.75

comment:19 Changed 2 years ago by saloynton

  • Sprint changed from 2012-01-17 (6) to 2012-02-14 (8)

comment:20 Changed 2 years ago by 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).

comment:21 Changed 2 years ago by saloynton

  • Cc jmoore, dgaudioso added

comment:22 Changed 2 years ago by saloynton

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

comment:23 Changed 2 years ago by jburel

  • Sprint changed from 2012-02-14 (8) to 2012-02-28 (9)

Moved from sprint 2012-02-14 (8)

comment:24 Changed 2 years ago by jmoore

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

comment:25 Changed 2 years ago by 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.

comment:26 Changed 2 years ago by jburel

  • Sprint changed from 2012-02-28 (9) to 2012-03-13 (10)

Moved from sprint 2012-02-28 (9)

comment:27 Changed 2 years ago by 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.

comment:28 Changed 2 years ago by saloynton

  • Status changed from new to accepted

comment:29 Changed 2 years ago by saloynton

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

comment:30 Changed 2 years ago by saloynton

  • Status changed from accepted to new
  • Owner saloynton deleted

comment:31 Changed 2 years ago by saloynton

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

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.

comment:32 Changed 2 years ago by saloynton

  • Sprint 2012-03-13 (10) deleted
  • Component changed from Usability to Search
  • Remaining Time changed from 0.75 to 0.5
  • Milestone changed from OMERO-Beta4.4 to Usability Backlog

comment:33 Changed 2 years ago by saloynton

  • Status changed from new to closed
  • Resolution set to fixed
  • Remaining Time changed from 0.5 to 0

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

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.2-PRO © 2008-2010 agile42 all rights reserved (this page was served in: 2.778024 sec.)

We're Hiring!