Table of Contents

maxLevel	2

...

Anchor

	Current
	Current

Current Roadmap

Proposed/Beyond One Year

Completed

HTML Comment

hidden	true

Colors to use with panels to show status...

Panel title	Border color	Background color	Title background color	Title text color
In progress	#339860	#c8f3c8	white	green
Partial work completed	#caceac	#e0e5bd	white	#868c5b
Not Started	#aaafaf	#d7dddd	white	black
Completed	#5e95a5	#bddce5	white	#5e95a5

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 as the year proceedsbased on available resources and community interest.

Accessibility modifications and enhancements

Address the backlog of accessibility issues in Hyrax and inform the testing process to include more robust and regular accessibility testing

Lead: Tom Johnson? (DCE

Panel

borderColor	#339860
bgColor	#c8f3c8
titleColor	green
borderWidth	1
titleBGColor	white
borderStyle	solid
title	In progress

Target Date: Q3 2018

- [project board|https://github.com/samvera/hyrax/projects]

Bugfixes & Ongoing Maintenance Work

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

July-December 2021 Cycle - Focus on issue clean-up, documentation, and testing Valkyrie work
- moving forward without Tech Lead, preparing for pledge-driven maintenance work in 2022

Target Date:
December 31, 2021

Lead: Juliet Hardesty
(Indiana University)

Working Group:
Hyrax Maintenance Working Group

Status Summary/Major Activities:

Project Board

January-June 2021 Cycle - Focus on issue clean-up in general

Target Date: 
June 30, 2021

Lead: Juliet Hardesty
(Indiana University)

Working Group:
Hyrax Maintenance Working Group

Project Board

2018-08-13 Focus of sprint focused on Accessibility roadmap item

Target Date: onging

Lead: tamsin johnson (UCSB)

Working Group: Hyrax Working Group

sprint

Issues

Swappable backends (i.e., Valkyrie support)

Target Date: TBD
Lead: Justin Coyne (Stanford University)
Working Group: Samvera Data Mapper Working Group

Description:

Panel

borderColor	#caceac
bgColor	#e0e5bd
titleColor	#868c5b
borderWidth	1
titleBGColor	white
borderStyle	solid
title	Partial work completed

- [milestone|https://github.com/samvera/hyrax/milestone/9]

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 the Data Mapper pattern.

Status Summary/Major Activities:

Last commit Q1 2018 (commits/valkyrie-6, commits/valkyrie)Conversations at Samvera Connect 2018
In-person sprint at Penn State - January 2019
Upcoming Development Effort - https://github.com/samvera/hyrax/projects/14

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

Lead: tamsin woo (UCSB)

Working Group: Samvera Data Mapper Working Group

Bulk import/export

Target Date: TBD
Lead: TBD
Working Group: TBD

Description:

Panel

borderColor	#aaafaf#c8f3c8
bgColor	#c8f3c8
titleColor	#d7ddddgreen
borderWidth	1
titleBGColor	white
borderStyle	solid
title	Not started

In Progress - [milestone|https://github.com/samvera/hyrax/milestone/14]

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:

Panel

borderColor	#caceac
bgColor	#e0e5bd
titleColor	#868c5b
borderWidth	1
titleBGColor	white
borderStyle	solid
title	Partial work completed

Analytics , reporting, and related notifications

community effort planning for early 2018 - Lead: Steve Van Tuyl (Oregon State University)

Hyrax Analytics Working Group (HAWG)

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: Summer 2021

Lead: Rob Kaufman (Notch8 via Oregon State)

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

Issues

#5e95a5

Panel

borderColor	#caceac
bgColor	#e0e5bd
titleColor	#868c5b
borderWidth	1
titleBGColor	white
borderStyle	solid
title	Partial work completed

Panel

borderColor

#5e95a5

bgColor

#bddce5

titleColor

Group and responsibility management

re

2021-01-12 - Being worked on in Hyku
Re-architect groups and responsibilities to improve clarity of function
- Lead: LaRita Robinson (University of Notre Dame) Samvera Permissioning Analysis and Design Working Group
.
Status Summary/Major Activities:
Permissioning Analysis Working Group:
2018-07-16 Request for feedback on deliverables of working group focused on use cases

Panel

borderColor	#aaafaf
bgColor	#d7dddd
borderWidth	1
titleBGColor	white
borderStyle	solid
title	Not started

Enhanced batch edit interface

build out batch edit functionality to meet the needs, specifically, of digital collections-based repository implementations (UI mock-ups are available) - Lead: Undefined

Completed in the Last Year (from today)

- .
- 2018-09-21 Webinar
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 (Deactivated)(Duke)

Working Group:

NA (though see Permissioning Analysis Working Group above)

Project Board

...

Current Roadmap

Anchor

	Proposed
	Proposed

Proposed/Beyond One Year

Completed

Proposed or Future (more than a year out)

Enhancement Requests (in Issues)

HTML Comment

hidden	true

Colors to use with panels to show status...

Panel title	Border color	Background color	Title background color	Title text color
Proposed	#303d4d	#e5eef9	white	#303d4d
More than a year out	#303d4d	#e5eef9	white	#303d4d

Collection Extensions Working Groups Collection Extensions

A set of functionality to expand how collections work. It includes collection types which control what a collection can do, nesting, branding, control of discovery, control of multiple membership, etc. Completed Q2 of 2018 and released in Hyrax 2.1 - Lead: Lynette Rayle (Cornell University)

Panel

borderColor	#303d4d
bgColor	#e5eef9
titleColor	#303d4d
borderWidth	1
titleBGColor	white
borderStyle	solid
title	Completed

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: tamsin johnson(DCE)

Working Group: TBD

panel

Panel

borderColor	#5e95a5#aaafaf
bgColor	#bddce5#d7dddd
titleColor	#5e95a5black
borderWidth	1
titleBGColor	white
borderStyle	solid
title	CompletedProposed

Implementing remaining

UI

mockups

address the backlog of UI mockups in Hyrax and Hyku and backport any Hyku UI features that are valuable in Hyrax (ongoing since late 2017) - Lead: Aaron Collier and Justin Coyne (Stanford University)

Future (more than a year out)

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

Lead: Steve Van Tuyl

Working Group:

Project Board

Versions Compared

Old Version 37

New Version Current

Key

A Vision for Hyrax

Targeted within the Next Year (from today)

Accessibility modifications and enhancements

Bugfixes & Ongoing Maintenance Work

Hyrax-Valkyrie

Batch RoundTripping of Data (import, export, edit)

Analytics , reporting, and related notifications

Group and responsibility management

Enhanced batch edit interface

Completed in the Last Year (from today)

Proposed or Future (more than a year out)

Replace Actor Stack with DRY Transactions

UI

Future (more than a year out)

Rectification

Page Comparison

Versions Compared

Old Version 37

New Version Current

Key

A Vision for Hyrax

Targeted within the Next Year (from today)

Accessibility modifications and enhancements

Bugfixes & Ongoing Maintenance Work

Hyrax-Valkyrie

Batch RoundTripping of Data (import, export, edit)

Analytics , reporting, and related notifications

Group and responsibility management

Enhanced batch edit interface

Completed in the Last Year (from today)

Proposed or Future (more than a year out)

Replace Actor Stack with DRY Transactions

UI

Future (more than a year out)

Rectification