...
Brian McBride (University of Utah)
Maria Whitaker (Indiana)
Juliet Hardesty (Indiana)
Chris Colvard (Deactivated) (Indiana University)
Collin Brittle (Emory)
rsteans (Avalon/ Northwestern)
Moira Downey (Deactivated) (Duke)
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
...
Lynette will take a look and see if she has more response to that. Fold in older conversations about merging admin sets and collections.
Steve - Resourcing - Ask was moderately successful. Folks in community asked for a single resourcing ask - got an okay response. 14 of 30 partners reponded , 2 non partners. All items are partially resourced at minimum.
What additional resourcing do we need to get the individual things done? See doc for staffing numbers.
Bulk roundtripping is now batch roundtripping. (Oregon Digital) Oregon and OSU putting out an RFP for getting this work done. Meet needs of broader community. Getting collected sense for what needs to get done.
work on permissions - 4 devs, need a coordinator - Sprint/ Scrum master (AI)
Analytics not getting much love - coordinator and 1 Dev. Need to find more or we lose analytics. Tom and Steve will look at this.
Have someone's ear toward resourcing - point them at the document.
Work and batch types at WGBH were very different - they have their own readers to read their batch types. They have worktypes with PBCore for inputs. Instantiations and different worktypes that they ingest.
AI: Steve will reach out to Sadie - but aware that not everything will get covered. Architecture of thing will be open and documented enough so that people can make local changed.
Ask and result: hard to get resources that we all say we need and want. Not nearly enough to get Hyrax WG going - right now Hyrax WG will not exist anymore.
Disconnect between what we say we want to do and need, versus what we do and resource
Indiana just hired a front end developer - she may be coming when she has some experience.
Sprint in January - 9 people, some are the folks resourced for the VoH. Working through coordinating what work we're expecting to see there.
Intent to have the Valkyrie functionality built in? Not after January - indciate in early summer we'll do that work.
Working group finished final sprint for 6 month charter - working through a bunch of issues that can be highlighted for a 3.0 release. Tightening things up. Some outstanding issues we need to rally some troops around. Hopeful to get 3.0 out before EoY. That WG was pretty awesome. Critical to allowing Hyrax to allowing us to have more frequent and less painful releases that worked with Semantic Versioning. WG a good.
- we need to resource the WG for another 6 months.