Hyku for Consortia is excited to report the wrap-up of our metadata-focused development sprint with our partners at SoftServ. These developments will support robust item descriptions, data consistency, and discoverability of resources in Hyku Commons and beyond. Responding to feedback from our back-end user experience study in 2022 (see earlier post: Hyku Commons Experience Report), feedback from users in Basecamp, and legacy requests, we worked with our community to prioritize feature development around metadata needs that would fit within the span of a single sprint. More work is to come, but we are happy to share some exciting developments including new metadata fields, rich text support, fixing the value order bug, the ability to upload metadata only-records, and much improved OAI-PMH support. Since community development is a high priority of this project, developments will be contributed back to base Hyku wherever possible.
New metadata fields
Also, while not new, the Resource Type field is now a required field for all worktypes. This will improve the consistency of analytics reporting within our shared system.
Rich text support
Many aspects of text stylization are supported, but the most common are:
- Line breaks <br> <br>
- External URLs [Link text Here](https://link-url-here.org)
- Block quote >
- Paragraph <p></p>
- Numbered lists (1. 2. 3.) and unnumbered lists (- - -)
- See here for more guidance https://www.markdownguide.org/basic-syntax
Control over metadata value order
Improved OAI-PMH feed
Soon we will work to test the new data feed with external systems and make adjustments as needed. We will also create Hyku Commons-specific documentation, but initial guidance for those interested can be viewed here: https://playbook-staging.notch8.com/en/samvera/oai-feeds.
|Ability to configure which fields are required (per tenant)|
|Ability to customize controlled vocabularies (per tenant)|
|Ability to relabel metadata fields (per tenant)|
|Ability to reorder field display (per tenant)|
|Ability to suppress the visibility of metadata fields from public view (per tenant)|
|Ability to suppress the visibility of non-required fields in the metadata entry form (per tenant)|