2017-06-05 AdminSets as type of Collection

Date: Mondays at 12pt/3et

Connection Information

Zoom:

Click to see more connection options...

Join from PC, Mac, Linux, iOS or Android: https://cornell.zoom.us/j/469937166

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

Or Telephone:
    Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)
    Meeting ID: 469 937 166
    International numbers available: https://cornell.zoom.us/zoomconference?m=xRra7nBf1kSXKVIuBZMKJptAI2TvTXUE

Or an H.323/SIP room system:
    H.323:
        162.255.37.11 (US West)
        162.255.36.11 (US East)
        221.122.88.195 (China)
        115.114.131.7 (India)
        213.19.144.110 (EMEA)
        202.177.207.158 (Australia)
        209.9.211.110 (Hong Kong)
    Meeting ID: 469 937 166

    SIP: 469937166@zoomcrc.com

Or Skype for Business (Lync):
    https://cornell.zoom.us/skype/469937166

Attendees:

Regrets

jamie

References

Requirements - Display Sets (milestones)
List of required mockups for Collections

Agenda

Discuss Potential to have Admin Set as a type of Collection
- OPTION 1: presented to the user as a Collection type in the UI only, but underlying code for AdminSets and Collections remains separate
- OPTION 2: convert AdminSets to a type of Collection
- OPTION 3: treat AdminSets and Collections as completely separate in the UI and in the underlying code
- OPTION 4: single UI on public pages (similar to Option 1), but separate on admin pages (similar to Option 3)

Notes

Option 1: separate supporting code, listed together as a collection in UI, but uses separate new/edit forms and show pages

Challenges:

- Two code bases to maintain
- Resolution of restrictions related to workflows, visibility, participants.
  - Are AdminSets and Collections equal?
  - Does one take precedence?
  - How to make the interactions intuitive?

Pros

- Very little change to AdminSets which has become an integral part of Hyrax
- No need to retrain the community on AdminSets (although there is still lots of confusion about what they are and how to use them), except on finding them under Collections in the Admin Menu
- Some training on Collections and how they relate to AdminSets
- Potentially less confusion because all grouping constructs are together

Option 2: same supporting code, same in UI

Challenges:

- Getting community support
- Resolution of restrictions related to workflows, visibility, participants.
  - How to apply workflows, visibility, participants when all collection types can have these AND works can be in more than one collection AND there may be conflicts in the way these things are defined?
  - Does one take precedence?
  - How to make the interactions intuitive?
- Lots of time spent bringing the community up to speed on AdminSets. Would have to retrain again.

Pros

- Going forward, have a single approach for collecting works

Option 3: separate supporting code, separate in UI

Challenges:

- Two concepts of collections things. When to use AdminSets and when to use Collections
- Lots of time spent bringing the community up to speed on AdminSets. Would have to retrain again.
- Two code bases to maintain
  - Resolution of restrictions related to workflows, visibility, participants.
    - Are AdminSets and Collections equal?
    - Does one take precedence?
    - How to make the interactions intuitive?

Pros

- No change to AdminSets which has become an integral part of Hyrax
- No need to retrain the community on AdminSets (although there is still lots of confusion about what they are and how to use them)
- Some training on Collections and how they relate to AdminSets

Action Items:

Lynette - comparison chart of Admin Sets and the expected common Collection types to show how AdminSets can be configured as a type of Collection
Gary - Mockups showing AdminSets as type of Collection