Current Roadmap | Completed |
---|
Colors to use with panels to show status...
|
Our common needs and experiences over the past few years have moved the Samvera Community in the direction of, for a great many of us, convergence on using Hyrax as a platform for our repository work. It is not possible or sustainable for Hyrax to be all things to all parties; the goal of Hyrax is to be an opinionated — though configurable — base for both institutional & data repositories and digital collections management repositories. Thus, we plan to continue building Hyrax in a way that allows it to be used off-the-shelf and as a springboard for highly customized solutions.
While improving daily, the current implementation of Hyrax is more suited to institutional & data repository use cases than it is to digital collections management repository use cases. Expected functionality for managing digital collections such as bulk ingest, edit, and export; database performance; and flexibility around collections and collection types are all noticeably missing from Hyrax. In order to realize the vision of Hyrax serving as a base for both sets of use cases, we propose focusing the upcoming release series on functionality for digital collections repositories while bolstering functionality for institutional & data repositories. (Most of the prioritized functionality will, we believe, be useful in both use cases.)
Development of new features is not our only goal for Hyrax. Feedback from the community is clear that there is a need to shift some of our focus to building more sustainable community practices around code maintenance, documentation, testing, and communication. While not entirely specific to Hyrax, we include suggested improvements in these areas as they will impact Hyrax development and the broader Samvera Community. As we progress in these areas, we will better articulate the resource needs and processes for the continued development of our shared software.
Listed roughly in priority order and the expected order of implementation. Some efforts may be implemented at the same time. The priority order may shift based on available resources and community interest.
Bugfixes & Ongoing Maintenance WorkThe Hyrax Maintenance Working Group is charged with supporting core maintenance and development for Hyrax in order to provide a stable base of support for the solution bundle. This working group is not meant to be a replacement for community-led development efforts and/or contributions, but rather, it is meant to augment such efforts. This group may work on some Roadmap Items. When they do, the group will be identified in the Status Summary section of the item. Status Summary/Major Activities:
|
Hyrax-ValkyrieMinimum Viable Product (MVP) repository solution which enables the use of multiple disparate storage backends for both files and metadata using the Data Mapper pattern. Status Summary/Major Activities:
|
Batch RoundTripping of Data (import, export, edit)2021-01-12 - This is almost done and could be considered for inclusion in Hyrax or as an add-on/gem option. Might have feature flipper that doesn't install gem unless it is configured. Might also have this installed but not turned on without a configuration setting. Allow bulk ingest and export of content and/or metadata from Hyrax using both command line and user interfaces. Status Summary/Major Activities:
|
Group and responsibility management2021-01-12 - Being worked on in Hyku Re-architect groups and responsibilities to improve clarity of function. Status Summary/Major Activities:
|
Current Roadmap | Proposed/Beyond One Year | Completed |
---|
Enhancement Requests (in Issues)
Colors to use with panels to show status...
|
Replace Actor Stack with DRY TransactionsUse DRY Transactions instead of the actor stack to make process clearer and easier to back out when things go wrong. Status Summary/Major Activities:
|
UI RectificationProject to resolve UI-related issues in Hyrax. Status Summary/Major Activities:
|