...
Title | Details | Links | Time Estimate | Proposed By | Facilitator | Interested in |
|---|---|---|---|---|---|---|
| Description: Want a community review and audit of the Samvera and Samvera Labs teams. Make sure that settings are applied properly, and that those who are no longer members of the community are not IDed as gem owners, etc. Need to clarify who has access and who to contact to push to Ruby gems and to do releases Will recommend that Admins must have 2FA enabled Will notify the community and do this organization discussion and implementation during the May Dev congress. Links: Time Estimate:
| 2 hours for discussion/action items | Roadmaps Alignment Group | |||
| Description: Discussion and strategizing and possibly development work around performance issues experienced using Hyrax 3.x. At least one example is what happens when trying to delete a work with many filesets (see issue link). Identify other issues / create issues Possibly review identified performance issues with Valkyrized Hyrax as well and see if there are differences or improvements. Links:
Time Estimate:
| 2 hours for discussion 2-3 days if there is development work Discussion, Tuesday, May 17, 3-5pm Eastern: https://iu.zoom.us/j/81955850246?pwd=NUVnSk9tVG1EZEJhclZGbWVVeEJVZz09 |
|
| ||
OAI-PMH feeds in Samvera Tech | Description: Providing harvestable OAI feeds for content is necessary for sharing to DPLA. Maybe this is just relevant for Hyrax but this might also be something to work on in the context of Hyku. Unclear if this is something that can be added to Hyrax or if this should be providing documentation of options for local implementation. Links:
Time Estimate:
| https://github.com/samvera/hyrax/issues/3328 ResourceSync is part of Hyrax already? https://github.com/samvera/hyrax/wiki/Feature-matrix Might be local examples that can provide options (SMIG meeting notes): Metadata Call 2022-2-22 | 1 day | |||
Hyrax Batch Edit Review/Design-a-thon | Description: Batch Edit is a specific interface for Works with a set of actions that is part of Hyrax. It is not behind a feature flip and is separate from the Bulkrax batch round-tripping that is a possible gem to add on to Hyrax. Batch Edit for Works could benefit from a redesign or a decision to remove it from Hyrax altogether. UX, design ideas, wireframes, use cases and opinions all welcome! Links: Time Estimate:
| https://github.com/samvera/hyrax/issues?q=is%3Aissue+is%3Aopen+batch+edit+label%3A%22batch+edit%22 | 1 day Thursday, 3pm Eastern: https://iu.zoom.us/j/81955850246?pwd=NUVnSk9tVG1EZEJhclZGbWVVeEJVZz09 | |||
Hyrax upgrade work for Blacklight 7/Rails 6 | Description: Upgrade work might still remain to support Blacklight 7 and Bootstrap 4, both of which are needed to upgrade Hyrax to use Rails 6. Currently, Hyrax uses Rails 5.7.2 and that is reaching end of life on June 1. Links:
|
Bootstrap 4 work: https://github.com/samvera/hyrax/issues/5276 |
| |||
| Description: Helping anyone who needs it to get Hyrax up and running locally (probably via Docker). Links: Time Estimate:
| 2-3 hours Monday, 2:30pm Eastern: https://iu.zoom.us/j/81955850246?pwd=NUVnSk9tVG1EZEJhclZGbWVVeEJVZz09 | ||||
| Description: Hyrax is still using the deprecated This might also bring dropping support of EOL Ruby versions (< 2.7) into question. Links:
Time Estimate:
| https://discuss.circleci.com/t/legacy-convenience-image-deprecation/41034 | 2-3 hours | |||
...