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. 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)
...
Panel | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
Bulk Import | hyrax/projects]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 item. Status Summary/Major Activities:
| Target Date: onging | Lead: (DCE) | Working Group: Hyrax Working
Target Date: | Lead: | Working Group: Hyku Interest Group | Issues |
Panel | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
Bulk Exporthttps://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:
|
Panel | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
Migration Toolhttps://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:
|
Panel | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
Persistent Short Linkshttps://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:
|
Panel | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
More Work Typeshttps://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:
|
Panel | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
Configurable Work Typeshttps://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:
|
Panel | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
Improved Notificationshttps://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:
|
Panel | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
Improved ReportingStatus Summary/Major Activities:
|
Panel | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
Track Storage Per Tenanthttps://github.com/samvera-labs/hyku/issues/1481 Status Summary/Major Activities:
|
Panel | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| |||||||||||||||
borderColor | #aaafaf | bgColor | #d7ddddFull Text and PDF ViewerThe lack of full-text indexing and a PDF viewer are critical components missing from this beta version. Status Summary/Major Activities:
| |||||||||||||
Target Date: TBD | Lead: LaRita Robinson (Notre Dame) | Working Group: Samvera Permissioning Analysis and Design Working Group | ||||||||||||||
Panel | ||||||||||||||||
|
Panel | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
Field Mapping for OAIThe 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:
|
Panel | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| |||||||||||||||
Image Upload PreviewA 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:
|
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:
|
...
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 |
...
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. |
...