Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

Current Roadmap
(6 mos - 1 yr)

Proposed/Beyond One YearCompleted

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.


In Progress

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 GroupIssues
Not Started

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 GroupIssues
Not Started

Work Types Filters Per Tenant

https://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:

Target Date:

Lead: 

Working Group: Hyku Interest GroupIssues
Not Started

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 GroupIssues

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

https://github.com/samvera-labs/hyku/releases/tag/v1.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

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

LICENSE

README.md

YES

README.md

Statement of purpose

YES

See GH header: https://github.com/samvera-labs/hyku

Basic install steps

YES

Running the stack

Identify any volatile/experimental features

N/A


How to contribute

YES

CONTRIBUTING.md

How/Who to contact for help

YES

SUPPORT.md

Product Owner

Known issues documented in github Issues tickets (not just listed in text)

YES

https://github.com/samvera-labs/hyku/issues

Tutorial / Walkthrough / Example usage

YES

Wiki

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.

  • No labels