List goals for this meeting (e.g., Set design priorities for FY19):
Updates from previous meeting
Report on testing and questions
Future steps
Discussion topics
Time
Item
Presenter
Notes
15m
Updates from previous meeting
David Kevin
File related issues with prod
Active Job deserialization error
Race conditions in jobs? Active fedora/noid
More work needed to resolve
Update to 2.5.1 to see if that fixes it
Controlled vocabularies
Creates a read block for non-related config files
Should be loaded into the db and code refactored to read from db
Workflows
From responses, two step is outlier rather than common
For now, I would suggest that campuses use the application as is
Too costly to refactor adminsets/etc
Create 1-2 admin sets per campus
Create a two step workflow for Sac (3 admin sets)
From other institutions experiences, this is a common sticking point
Some institutions have taken hyrax offline to provide workflow as backend operations – I like this idea to separate curatorial efforts from management/front end, but we’re not there yet
Running multiple apps in hydra cluster, with valk adapters possibly, ought to be a good solution to support