Current Roadmap | Proposed/Beyond One Year | Completed |
|---|
...
| 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 | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
Work Types Filters Per Tenanthttps://github.com/samvera-labs/hyku/issues/1485 As part of expanding the number of available Work Types we need to also be able to limit which work times are viewable in a given tenant. Status Summary/Major Activities:
|
...
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. |
...