National Digital Platform
Hyku, the repository software produced by the Hydra-In-a-Box project, was built as a part of the Institute for Museum and Library Services’ National Digital Platform initiatve. It strives to be “a feature-rich, robust, flexible digital repository that is easy to install, configure, and maintain.”
Hyku vs Hyrax vs Omeka
Hyku is an “out of the box” version of the Samvera community’s Hyrax repository platform. If you do not have any web developers on staff or already plan to use a consortium to help offload technical issues, Hyku might be the right fit for you. Check out this article on Hyku’s wiki. If you have developers on staff and are looking to have customized workflows and tech specs, consider using Hyrax and joining the Samvera community. If you’re looking to build an online exhibition or digital humanities project, Omeka is a wonderful tool. If you’re looking to build a robust institutional repository or digital collections system, you might be better served by the Fedora/Solr/Blacklight-backed Hyku.
These are just some of the features listed in Hyku’s current documentation.
- Responsive interface – Displays clearly and is usable on the range of screen sizes and mobile devices.
- Redesigned, consolidated dashboard – A single interface with advanced tooling to access all administrative and management tasks and reporting.
- Batch work upload – Upload multiple files to create multiple works of the same work type.
- Highlighted Work – A depositor can designate works to be highlighted on their User Profile.
- DPLA ready – Crosswalks directly to DPLA Metadata Application Profile v4.
- Faceted search and browse – Powered by Blacklight, an intuitive interface makes it easy to search and find content quickly.
Hyku Metadata Schema
In Hyku, the metadata is based around work types. The Generic work that comes standard out of the box includes 16 fields that comply with DPLA harvesting and are listed below.
|Title||✓||dct:title||A name to aid in identifying a resource.|
|Creator||✓||dce:creator||The person or group responsible for the resource. Usually this is the author of the content. Personal names should be entered with the last name first, e.g. “Smith, John”.|
|Keyword||✓||dce:relation||Words or phrases you select to describe what the resource is about. These are used to search for content.|
|Rights statement||✓||edm:rights||Indicates the copyright and reuse status of the resource. While licenses cannot always be asserted, a rights statement can be. See RightsStatements.org for more information.|
|Contributor||dce:contributor||A person or group you want to recognize for playing a role in the creation of the resource, but not the primary role.|
|Description||dce:description||Free-text notes about the resource. On Hyku's dashboard it is called “Abstract or Summary"|
|License||dct:rights||Licensing and distribution information governing access to the work.|
|Publisher||dce:publisher||The person or group making the resource available.|
|Date created||dct:created||The date on which the resource was created. Strongly recommended to select a particular date encoding (such as EDTF) to guide date formats.|
|Subject||dce:subject||Headings or index terms describing what the resource is about; these need to conform to an existing vocabulary (Keywords should be used for uncontrolled values).|
|Language||dce:language||The language of the resource’s content. Best practice is to select a language representation to follow, such as ISO 639-1 or full names taken from a controlled vocabulary.|
|Identifier||dct:identifier||A unique handle identifying the resource. This does not affect the identifier minted for managing your resource in Hyku.|
|Location||foaf:basedNear||A place name related to the resource, such as its site of publication, or the city, state, or country the work contents are about. Best practice is to select, if possible, one definition (such as ‘place of origin of the work’) for this field across objects in a collection or collections in your repository.|
|Related URL||rdfs:seeAlso||A link to a website or other specific content (audio, video, PDF document) related to the resource.|
|Source||dct:source||An identifier for a related resource from which the described resource is derived, in whole or in part.|
|Resource Type||dct:type||Pre-defined categories in Hyku to describe the type of content being uploaded. More than one type may be selected.|
Hyku is a good fit for institutional repository use cases, with out of the box support for self-deposit workflows and robust access controls.
Cultural Heritage Repository
The Hyku development community is still working on adding functionality for cultural heritage use cases. The Hyku Pilot that occured in 2017 included a gap assessment document that should help determine whether or not Hyku is a good fit for your institution.