...
Current Roadmap | Proposed/Beyond One Year | Completed |
|---|
| HTML Comment | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||
Colors to use with panels to show status...
|
The Hyku
...
Project
“Hyku” is the result of the Hydra-in-a-Box, IMLS grant-funded project. It was developed as a turnkey solution bundle for digital asset management by the Samvera (previously known as Hydra) community. Hosted solutions are in development with a goal to lower the barrier of entry and expand the number and diversity of institutions capable of leveraging this powerful digital repository platform.
...
Targeted within the Next Year (from today)
...
| Panel | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
Bulk Export | hyraxprojects] | Bugfixes & Ongoing Maintenance WorkThe 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 item1475 Required to allow full system backup and restore. Required to allow movement of tenants between stacks or between hosting providers. Required to allow for hand-off of content on tenant exit. Required for service exit strategy. Status Summary/Major Activities:
Working Group: Hyrax Working Group | Issues |
|
| Panel | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| |||||||||||||||
DOI Integrationhttps://github.com/samvera-labs/hyrax-doi Adds support for minting and storing a DOI for a work. When supplying an existing DOI, user can autofill the deposit form by looking up metadata associated with a DOI. Status Summary/Major Activities:
| Target Date: TBD | Lead: LaRita Robinson (Notre Dame) | Working Group: Samvera Permissioning Analysis and Design Working Group
| Target Date: Fall 2020 | Lead: Chris Colvard | Project: Advancing Hyku |
| Panel | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
| Target Date: TBD | Lead: TBD | Working Group: TBD |
Code Requirements
...
Requirement
...
Met?
...
How?
...
Code must be released at version >= 1.0
...
YES
Version 1.0.1
| |
Migration Tool |
...
Good unit test coverage measured by community (e.g. 100% or 75% of what’s important)
...
YES
...
93%
...
YES
...
Travis
https://travis-ci.org/samvera-labs/hyku
...
uses Coverage tool (coveralls or simplecov)
...
YES
...
Coveralls
https://coveralls.io/github/samvera-labs/hyku?branch=master
...
Show compatibility with current Rails versions and other dependencies, when was it last tested; note compatibility with prior versions when available. Compatibility can be specified in the gemspec(s) or verified via CI matrix.
...
YES
...
Travis tests against ruby 2.4.1
v.1.0.1: Rails 5.1.6; Hyrax 2.3.3
...
Hierarchy of promises asserted in clearly defined acceptance tests
...
YES
Documentation Requirements
...
Requirement
...
Met?
...
How?
...
LICENSE file, Apache 2 (or compatible)
...
YES
...
...
...
YES
...
...
Statement of purpose
...
YES
...
Basic install steps
...
YES
...
...
Identify any volatile/experimental features
...
N/A
...
How to contribute
...
YES
...
...
How/Who to contact for help
...
YES
...
...
Known issues documented in github Issues tickets (not just listed in text)
...
Most of the current pilot institutions have stated that they would not subscribe to a Hyku service until there is a clear migration path from CONTENTdm. Status Summary/Major Activities:
|
| Panel | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
Custom License and Rights StatementsRightsstatement.org statements can be selected from a controlled list. However, no custom statement is possible. We need two rights statement fields, one controlled and one customizable[RK12] . Status Summary/Major Activities:
|
| Panel | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
More Work Types |
...
Tutorial / Walkthrough / Example usage
...
YES
...
...
Resolve TODO items in documents and remove them
...
NO
...
There are 10 TODO items in the code.
...
All Contributors should have signed Hydra Contibutor License Agreement (CLA)
...
YES
...
Compare https://github.com/samvera-labs/hyku/graphs/contributors
With https://wiki.duraspace.org/pages/viewpage.action?pageId=87460368
...
Requirement
...
Met?
...
How?
...
Community use by three or more institutions
...
YES
...
PALNI/PALCI with Notch8, King’s Fund with CoSector, British Library with Ubiquity, Texas Digital Library - Bridge2Hyku Project
...
In active use for six months
...
YES
...
Notch8, Ubiquity, CoSector and TDL have been working with the software for over 6 months. Prior to that DuraSpace, Stanford and DPLA were working on the software. Throughout that time the software has been in active development.
...
Has an ongoing maintenance plan.
...
YES
...
ETDs, Publications (articles, journals, books), and Datasets - Required to be competitive with alternative IR/Publishing solutions. Samvera community members are working on Fulcrum, which is a publishing platform recently migrated to Hyrax. Newspaper, Journal, Serial - Requested specifically by pilot institutions. Status Summary/Major Activities:
|
...