SUI - 2016-03-11 Work Show Pages (Final Review)

Agenda

• Work Show Pages - Final Review
  • Show Work (all variants) - Phase 1 - UI Wireframes
• Browse Pages

Attendance

• Lynette Rayle (Cornell University)
• David Trujillo (UCSD)
• Simone Sacchi (Columbia University)
• Linda Newman (University of Cincinnati)
  
  

Notes

Work Show Pages - Final Review

Location of actions when 1 item

• Option 1: Below primary thumbnail.  What happens if user clicks   to see technical metadata?  No place to expand below primary thumbnail.
  • Use Option 2 for Sufia 7.0.
  • Could come back to something similar to this for Sufia 7.1
  • Easier to add functionality than to take back a change.

• Option 2: Have an items table, just like or 2+ items, but with only 1 item and simplified set of controls for the list (i.e. remove all but column labels)
  • + keeps the interface consistent
  • Previews
    • For Sufia 7.0, limited if any preview functionality will be available. 
    • More exploration is needed to determine what types of files support preview and what the needs of the previewer are.
    • Using this option doesn't limit what we can do in Sufia 7.1 for addressing preview functionality
    • Not sure how preview will be handled in Sufia 7.0.  Could make the preview icon gray if no preview is available.
    • Need to explore if we can force a download when download icon is clicked instead of trusting the browser to download a file instead of using the browsers configured action for that file type.
    • ACTION: Document this information in the issue for Sufia 7.0 and allow for some developer discretion as they investigate the actual requirements of previewers.

We went for Option 2 for Sufia 7.0 with the plan to revisit for Sufia 7.1.

 

ACTION: Update wireframe to use Option 2 for location of actions when 1 item

Expand/Collapse for metadata, relationships, users, and share

• Option 1: Implement with expand and collapse areas
• Option 2: Always have fully expanded

We didn't talk about this very long.  There seemed to be agreement that expand/collapse benefits of having the list of items closer to the top outweigh the need for extra clicks.  

 

ACTION: Add issue(s) for Work Show Pages

 

Browse Pages

We began a discussion on Browsing.  The flexibility of the model makes this complex.  For instance, collections relationships with each other can be a graph that isn't necessarily structured hierarchically.  So what would be the starting point for Browsing Collections?  Would it be all collections, such that a collection and its sub-collections will all be at the top level?  What would be the drill down path to go from one collection to its sub-collections?  We decided to think about this some more.

ACTION: It would be good to see various wireframes and sketches from others.