Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Date

1pm EST 

Join from PC, Mac, iOS or Android: https://msu.zoom.us/j/478788119

Or join by phone: 

+1 646 558 8656 or +1 646 876 9923 US Toll

+1 877 369 0926 (US only, Toll Free)

Meeting ID: 478 788 119

International numbers available: https://msu.zoom.us/zoomconference?m=5ijYCsNkOSXaxe1liQZkWVqktcflC5qH

Or join from a H.323/SIP room system: 

Dial: 162.255.36.11 (US West) or 162.255.37.11 (US East)

Meeting ID: 478 788 119 

Attendees

Goals

  • Address any final unresolved topics within the specs.  If time, briefly summarize highlights of the specs.

Discussion items

TimeItemWhoNotes
Discussion of issues
  • Visual Layout:
    • should there be a forgot password function as mocked up?
    • Is there a way to navigate in and out of the resource tree via keyboard shortcut for screen readers?
    • One or two publish notes for multi-part notes?
  • Data Entry
    • Lump in Bulk delete/edit and keep Reorder Mode separate as a button (even if it is integrated also into REM)?
    • Location in Hierarchy bulk move clarification?
    • Autosave function - do we always want it?
    • Clone/copy elements vs data inheritance via linking Agent records?
  • Access points spec: Nix the term "Access Points"?  Discuss PUI-adapted terms for general understanding vs terminology in staff interface

    
  • Access Points: Agents and Subjects Spec

    • The spec defers to the Agent Team’s future recommendations.
    • Recommend a dedicated ad-hoc group to review Subjects module, similarly to the group that is reviewing the Agents module.
    • Agent records should show all earlier and later forms of itself within the record, following the cataloging source.
    • Adding functionality to bulk merge and/or edit agents and subjects.

     Navigation Spec

    • List navigation should be treated the same regardless of type of list to provide a consistent user experience
    • All linked records should link to one another.
    • Moved the Manage Users and Manage User Preferences into the same page.

     

    Organization of Menus Spec

    • Refactor the System and Cogwheel menus into a single menu (“System Administration” or “System Settings”)
    • Update Browse and Create buttons to be more inclusive of ASpace functionality (e.g., should be able to browse and create all high level records, including Container Profiles)
    Update Create button to elevate functionality lived deeper in submenu (e.g., Background job functions: Reports, Imports, Exports), and move Default Values (Accession, Resource /Component, and Digital Object / Component) to top level.

Action items

  •  
  • No labels