Current Roadmap | Proposed/Beyond One Year | Completed |
|---|
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. DuraSpace has been piloting Hyku as a hosted service, called HykuDirect, 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)
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.
Bulk Import
https://github.com/samvera-labs/hyku/issues/1474
The ability to perform content ingest in Hyku through an automated process. This is necessary for data migrations. Pilots mentioned this need specifically. Relevant for CONTENTdm, Digital Commons, and DSpace migrations. Not necessarily relevant to local Hyku or Hyrax migrations (that can be done via database (DB) dump and reindex).
Status Summary/Major Activities:
| Target Date: | Lead: | Working Group: Hyku Interest Group | Issues |
Bulk Export
https://github.com/samvera-labs/hyku/issues/1475
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:
| Target Date: | Lead: | Working Group: Hyku Interest Group | Issues |
Migration Tool
https://github.com/samvera-labs/hyku/issues/1491
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:
| Target Date: | Lead: | Working Group: Hyku Interest Group | Issues |
Persistent Short Links
https://github.com/samvera-labs/hyku/issues/1477
Pilots noted this as a requirement in order to allow for referencing and citation. Required to be competitive with other IR solutions.
Status Summary/Major Activities:
| Target Date: | Lead: | Working Group: Hyku Interest Group | Issues |
More Work Types
https://github.com/samvera-labs/hyku/issues/1485
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:
| Target Date: | Lead: | Working Group: Hyku Interest Group | Issues |
Configurable Work Types
https://github.com/samvera-labs/hyku/issues/1493
Required to support work types which have not been (and perhaps never will be) part of the default set, but for which there are distinct needs. Custom metadata will make this easier to accomplish.
Status Summary/Major Activities:
| Target Date: | Lead: | Working Group: Hyku Interest Group | Issues |
Improved Notifications
https://github.com/samvera-labs/hyku/issues/1500
Currently, notifications are available only within the interface of Hyku and not via email. Email notification options are needed to compete with similar systems.
Status Summary/Major Activities:
| Target Date: | Lead: | Working Group: Hyku Interest Group | Issues |
Improved Reporting
Status Summary/Major Activities:
| Target Date: | Lead: | Working Group: Hyku Interest Group | Issues |
Track Storage Per Tenant
https://github.com/samvera-labs/hyku/issues/1481
Status Summary/Major Activities:
| Target Date: | Lead: | Working Group: Hyku Interest Group | Issues |
Full Text and PDF Viewer
The lack of full-text indexing and a PDF viewer are critical components missing from this beta version.
Status Summary/Major Activities:
| Target Date: | Lead: | Working Group: Hyku Interest Group | Issues |
Field Mapping for OAI
The available fields are fixed and cannot be renamed or configured. Each available field is mapped to its corresponding Dublin Core element and cannot be unmapped or remapped to another element. Both of these affordances (remapping and unmapping) are central to the way we outbound metadata via OAI-PMH to our ILS and to aggregators like the DPLA[RK11] .
Status Summary/Major Activities:
| Target Date: | Lead: | Working Group: Hyku Interest Group | Issues |
Image Upload Preview
A cataloger cannot see the image they’ve uploaded when entering metadata. Our CONTENTdm cataloging workflow depends on student workers being able to upload a large number of images and then cataloging each image using a visual preview of the uploaded image as a reference point and guide. Built-in controlled vocabularies, absent in HykuDirect, are also an important part of our CONTENTdm image cataloging workflow[RK10] .
Status Summary/Major Activities:
| Target Date: | Lead: | Working Group: Hyku Interest Group | Issues |
Custom License and Rights Statements
Rightsstatement.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:
| Target Date: | Lead: | Working Group: Hyku Interest Group | Issues |
Promotion of Hyku from samvera-labs to samvera (Julie Allinson)
Code Requirements
Requirement | Met? | How? |
Code must be released at version >= 1.0 | YES | Version 1.0.1 |
Good unit test coverage measured by community (e.g. 100% or 75% of what’s important) | YES | 93% |
uses CI (Preferably Travis-CI, unless there is a compelling reason to do something else) | YES | Travis |
uses Coverage tool (coveralls or simplecov) | YES | Coveralls |
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 | See GH header: https://github.com/samvera-labs/hyku |
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) | YES | |
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 |
Use Requirements
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 | Hyku has a product owner, and an Interest Group. The group is working on a gap analysis and roadmap. |