Attendees:
Steve Van Tuyl (oregon state university; hyrax fella)
Lynette Rayle (Cornell)
Brian McBride (University of Utah)
Agenda:
- Plan S Requirements https://www.coalition-s.org/https://www.coalition-s.org/wp-content/uploads/271118_cOAlitionS_Guidance.pdf (jrudder )
- Admin Sets, Visibility, and You! (???) - https://github.com/samvera/hyrax/issues/3432
- Resourcing for WG and Feature Builds (AKA Gird Your Loins; Steve Van Tuyl)
- The doc here - with annotation: https://docs.google.com/document/d/1hbiOnr3MQudkCdyqB1RChCZ0a3hXs_MJ5L_2X9SbQKI/edit
- Current work that may match roadmap (???) - rsteans
- batch import? etc...? - what are people currently working on that matches the roadmap - review from the resourcing doc
- Valkyrie in January - rsteans
- who is going from this group? Do we have any specific things we need to accomplish? Do we see any hurdles that are Hyrax specific?
- WG report - rsteans
- Hyku Report/ Bridge2Hyku - rsteans
Julie - Plan S - Trying to make all funded research accessible in a public acccess repo or platform. Doesn't need to be an IR, but does need to be publicly available. Response to Elsevier.
Requirements that repos have to follow - 10.2 provides IR requirements - more of a question of: are we ready as a Hyrax group to respond to these requirements
Requirements are super vague - hard to know how to implement, hard to prepare Hyrax to comply with the list of requirements - What is the body that's going to define the requirements.
AI: contact Ubiquity Press and ask what they're doing. (maybe Notch8) - kind of stuff we can't do/ no capacity for it
Workflow and process - what's being implemented at a particular location -
Steve - Admin Sets, Visibilty and You - most recent Hyrax WG sprint - part of testing, something we have to look at in 2019 - how do admin sets behave and why? Matter of understanding how it functions. Do we need to change the functionality or clarify the behaviors in documentation? This time - address in documentation.
Issue: