This Confluence wiki site, maintained by DuraSpace prior to the recent merger with LYRASIS, will transition from the duraspace.org domain to the lyrasis.org domain on Saturday, Nov 16 beginning at approximately 7pm ET. A period of downtime of 2-3 hours is expected. After the transition, this wiki will be available at https://wiki.lyrasis.org/. All links to duraspace.org wiki pages will be redirected to the correct lyrasis.org URL. If you have questions prior to or following the transition please contact: wikihelp@lyrasis.org.
Skip to end of metadata
Go to start of metadata


A Vision for Hyrax

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.


Targeted within the Next Year (from today)

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.


In progress - project board

Bugfixes & Ongoing Maintenance Work

The Hyrax 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:

  • 2018-08-13 Focus sprint focused on Accessibility roadmap item
Target Date: onging

Lead: Tom Johnson (UCSB)

Working Group: Hyrax Working GroupIssues




Partial work completed - milestone

Hyrax-Valkyrie

Minimum 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:

Target Date: March 11-April 5 (2, 2-week sprints)

Lead: Tom Johnson (UCSB)

Working Group: Samvera Data Mapper Working Group


In Progress - milestone

Batch RoundTripping of Data (import, export, edit)

Allow bulk ingest and export of content and/or metadata from Hyrax using both command line and user interfaces.

Status Summary/Major Activities:

  • Phase One WG outputs
  • Coordination of focus and scope with representatives from Batch WG, Avalon, Hyrax, and Hyku (completed Late 2018)
  • Oregon Digital is creating an RFP to fund the development of this feature set
Target Date: Winter 2019

Lead: steve van tuyl (Oregon State)

Working Group:
This work is related to, but not entirely encompassed by, Hyrax Batch Import-Export WG
Issues



Partial work completed

Group and responsibility management

Re-architect groups and responsibilities to improve clarity of function.

Status Summary/Major Activities:

  • Permissioning Analysis Working Group:
  • Hyrax Bridge Development Effort - the goal of this effort is to implement some new permission features for Hyrax in the near term, while the Permissioning Analysis Working Group completes it's pilot phase.
Target Date: Spring 2019

Lead: Moira Downey(Duke)

Working Group:

NA (though see Permissioning Analysis Working Group above)

Project Board






Current Roadmap

Proposed/Beyond One Year

Completed

Proposed or Future (more than a year out)

Enhancement Requests (in Issues)


Proposed

Replace Actor Stack with DRY Transactions

Use DRY Transactions instead of the actor stack to make process clearer and easier to back out when things go wrong.

Status Summary/Major Activities:

  • TBA
Target Date: TBD

Lead: Tom Johnson(DCE)

Working Group: TBD


Partial Work

Analytics

No efforts currently planned. Removed from Hyrax roadmap in early  2019 due to lack of resourcing.

Status Summary/Major Activities:

Target Date: TBD

Lead:

Working Group:Issues
Proposed

UI Rectification

Project to resolve UI-related issues in Hyrax.

Status Summary/Major Activities:

  • Proposed (DRAFT) Project Board
  • Coordinating among Hyrax Product Owner, UX Interest Group, and Repository Managers Interest Group
Target Date: TBDWorking Group:Project Board






  • No labels

4 Comments

  1. Format looks good, I suggest that it might be better to have old/released items on a separate history page that this one just links to

    1. That makes sense.  I'll look at doing that once I get feedback from others too.  Thanks for the review.

  2. Lynette Raylei think this is a great approach. Thanks for putting it together. Can we get a few folks from SIGAHR to flesh this out and officially get it on the SIGAHR wiki (instead of, or in addition to, the google doc version of the roadmap)?