Child pages
  • 2017-01-24 Personas, Workflows, APOs, Admin Sets
Skip to end of metadata
Go to start of metadata

Date:  Tues, 01-24-2017  at  8pt/11et

Connection Information



  Click to see more connection options...

Join from PC, Mac, Linux, iOS or Android:

Or iPhone one-tap (US Toll): +14086380968,346733833# or +16465588656,346733833#

Or Telephone:
Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
Meeting ID: 346 733 833
International numbers available:

Or an H.323/SIP room system:
H.323: (US West) (US East) (China) (India) (EMEA)
Meeting ID: 346 733 833


Or Skype for Business (Lync):


Expected Attendees:


Agenda & Notes

  • Discuss expected flow based on user personas
    • Terminology for the personas is different from institution to institution, some can be combined into one. Can be based on their roles
    • Decide on roles that can define the personas for Hyrax
    • DSpace has : Submitter, Admin, Curator
    • Hyrax roles: The possible roles could be Admin. Depositor, Approver, Reviewer
  • Review discussion on requirements related to:
    • Add Existing Resource
    • Resource Creation
    • Batch Upload
    • Workflow Control
    • APO Control
    • Mirror Admin Set

Questions that came up during our discussion:

  • How can we coordinate the work with UX/UI group?
  • How display sets are similar or different from Admin Set? It would be good to keep in mind, not to duplicate the work of Admin Set into Display Set. If institutions are not using Admin Sets, can they still use display sets? Can admin sets be nested? 
  • Question for community interested in admin set: The ability to nest and the ability to be in multiple display sets are the most important reasons to have display sets. Can admin sets be broaden to include these two?


  • No labels