Agenda

• Finalize the position and functionality of the toolbar
• Create New Work layout for metadata, components, files, and sidebar
• David and Simone's Batch Upload
• Accounting for the Browse Everything gem in our design
• Next Steps

Notes

Attendance

• Lynette Rayle (Cornell University)
• Anna Headley (Chemical Heritage Foundation)
• Michael Tribone (Penn State)
• David Trujillo (UCSD)
• Simone Sacchi (Columbia University)
• Sonya Betz (University of Alberta)
• Andy and Shawn (Univ. of Houston)

Discussion

• existing menu bar and toolbar
  • some feel that it is odd being sandwiched together
  • Drupal menu/toolbar as an example
  • toolbar appears only when user is logged in and on an "administrative" page
• hamburger versus cog
  • some question whether the hamburger menu will be immediately recognizable to users
• toolbar
  • suggest reordering menu options and put "admin" functions at the end of the list
    • manage collections and manage works are for "power admin"
    • only show when admin is logged in
• highlights and shares
  • put under works
  • can't highlight collections?
  • shares
    • share works with people
    • merge two lists
      • sharing my own uploads
      • sharing the work of others
    • use facet to filter
    • shared with me could have an icon or a label to make it more explicit
  • highlights on the dashboard
    • highlight collections in the future
    • what will it look like when you list works and collections?
    • how will people discern between works and collections?
      • icons or labels
      • layout
• Create New Work Form and Layout
  • questions around "required" and "optional" headings on form
    • suggest "core" and "additional"
      • each institution will have their own set of core and additional
      • configurable
    • required or core
      • use an "asterisks"
      • don't separate and keep all form elements together
      • optionally use javascript to show/hide to keep the form lighter visually
      • what happens when resource type changes metadata fields?
        • all fields are in the form just not displayed (core and additional) 
          • what happens when you hit save?
    • some people have noticed that users only fill out form fields that are visible
  • others feel that they would like having some headings
  • again how do we make it easy for users?
    • give sites control over required and layout of the form
    • can we auto populate creator and depositor with the same info?
      • may be different depending on material being uploaded and by whom
• Sidebar
  • suggested changes to headings
    • Add to Collection instead of Collection
    • Add to Work instead of Works
  • save button
    • most people like having the save button at the top in the sidebar
      • some question if this may confusing if we actually go through certain workflows; for example, adding files, draft status
    • save to Fedora but not visible
    • grouping
      • add timestap
      • save and cancel
    • what happens when you save?
      • uploads right away?
      • what happens if I hit cancel after uploading files?
    • always goes to show page after saving?
    • grey out save button until certain conditions are met
    • two buttons
      • save
      • save and add files
• workflow
  • some individuals feel that this wireframe may be too advanced for some users
    • how do we usher user to the next step?
      • if the create a new work show message "do you want to upload some files?"
      • almost like onboarding
      • save and exit
      • save draft versus publish
      • save without files
      • how do we visually represent the workflow
  • utilizing the private status as an interim step to draft