For the full release notes, see Hyku v6.2.0 on GitHub.
Hyku 6.2 is the first release with Flexible Metadata, the change we previewed in our Hyku 6.0 post. HykuUP customers were running 6.2 release-candidate code by late September, so the search and full-text changes below reached them about six weeks ahead of the release.
Flexible Metadata
Until now, a repository’s fields and work types were defined in code. Adding a field meant a code change and a deployment, and every customization made the next upgrade harder. In 6.2 they come from a metadata profile that each repository keeps for itself.
- A repository manager who needs a new field, such as a grant number on datasets, adds it to the profile instead of waiting on a developer.
- The profile also sets which work types a repository offers, so a repository that only collects theses and datasets doesn’t show depositors anything else.
- Field labels come from the profile, so the deposit form uses the names your staff already use.
- Hyku checks a profile before accepting it. A profile with a missing required field or an unsupported work type gets an error message on upload instead of breaking the repository, and Hyku won’t let you remove a work type that already has records.
Controlled vocabularies
A field can now take its values from a controlled vocabulary named in the profile, either a local list the repository maintains or a remote authority such as the Library of Congress. Depositors pick a term instead of typing one, so the same subject doesn’t end up entered several different ways.
Search controls
- Repository managers can leave chosen fields off the search results page, so results show only the fields visitors need to pick the right item.
- A collection can be hidden from search results without changing who can see it, which suits administrative or in-progress collections.
- PDFs with no text layer can still be searched in full. Upload a plain-text file alongside the PDF and Hyku searches its text, which helps with scans where OCR failed or a transcript already exists.
Bot traffic
Search pages are the ones crawlers scrape hardest, and Hyku 6.2 aims its rate limiting at them. Heavy bot traffic is throttled there, so pages stay fast for people.
Batch Create retired
The older Batch Create form, which made several works from one set of metadata, doesn’t work with Hyku’s new storage layer and is switched off in 6.2. Bulk Import covers the same job.
Questions about Flexible Metadata, or about running Hyku on HykuUP? Book a demo and we’ll show you a profile in action.
Post details (not part of the post)
- Title: Hyku 6.2 released!
- Slug: hyku-6-2-released
- Date: November 4, 2025
- Category: News
- Author: HykuUP Team
- Excerpt: Hyku 6.2 introduces Flexible Metadata, so each repository sets its own fields, work types, and controlled vocabularies without custom code.