Meeting Logistics:
Time: 9:00am PDT / Noon EDT
Zoom Meeting URL: https://princeton.zoom.us/j/7739591625
(link will launch Zoom client – if you do not have Zoom, expand the instructions below)
Agenda (meeting notes below)
Nurax instance management (Juliet Hardesty)
Considering change from CircleCI to Github Actions for automated testing for Hyrax and other Samvera tech (Bradley Watson)
Hyrax Question
Hyrax PR Review Request
<add your agenda item here (your name)>
Moderator: Juliet Hardesty (Indiana University)
Notetaker: James Griffin (Princeton University Library)
Attendees:
Bradley Watson (Emory University)
Mark Bussey (Data Curation Experts)
Collin Brittle (Emory University)
Chris Colvard (Indiana University)
Heather Greer Klein (Samvera Community)
Meeting Process
Notes
Nurax Instances
Who needs to be in the conversation for managing Nurax instances?
Two conversations need to be held, one today, one at a later day
DCE provided the hardware resources for Nurax some years ago (2016?)
DCE can provide support for the hardware with funding, however, there are very limited resources for maintaining the database administration
Someone with knowledge of Valkyrie needs to be accessible for addressing the database administration (this is a major shift for what was previously Hyrax)
DCE also does not have the resources for supporting reviewing and merging changes for the code base (e. g. CSS updates), or, for creating and managing tester administrative user accounts
DCE has been running low on disk space on the deployment servers
3 levels of support:
pull requests/day-to-day maintenance
who is in charge of the content which is ingested into Nurax? this consumes disk space - this is collection administration
when the server needs infrastructure changes/systems administration, this is going to require a conversation regarding whether this has been needed before
First level of support
This should be the Hyrax Tech Lead (perhaps Julie until this person is selected?)
Mark: Most experienced contributors can review and merge pull requests for adding/updating test users
The list for contributors for the Nurax code base may need to be updated
Second level of support
There should be a cleanup schedule in order to avoid unnecessary disk space consumption
Concept of data seeding - ideally repository should have seed data and content imports for feature testing
Third level of support
This is the level of support which is going to require a separate, focused conversation
nurax-pg labor is going to require significant changes for the server infrastructure and the deployment of Nurax