Samvera Community Wiki
Hyku User Survey Analysis (2026)
This report summarizes the results of a 2026 community survey of Hyku users, conducted to identify shared priorities, technical pain points, and areas of divergence across repository contexts. The survey received 28 responses from engaged practitioners representing a range of repository sizes, hosting models, and roles. Respondents were asked to force-rank both broad strategic goals and specific technical problem areas, allowing for comparative analysis across cohorts. While the sample reflects active and invested users rather than the full Hyku population, the results provide a meaningful snapshot of current needs and pressures shaping day-to-day repository work.
A PDF of this summary and analysis is attached at the bottom of this page.
1. Overview of respondents
The majority of respondents are hosted, either consortially or through HykuUp.
Respondents mostly self-identified as libraries or library-adjacent collections. While consortia host for individual libraries, three also described their consortial administrative use of Hyku.
The primary use cases for respondents are Institutional Repository, hosting cultural heritage materials, or educational materials including theses and dissertations. These are not mutually exclusive categories and respondents were free to select multiple.
The majority of respondents manage small repositories.
2. High-Level Priorities (Broad Goals)
Across all respondents, the primary focus remains on the end-user experience and the foundational health of the platform.
Top Priority: Patron Discovery and Ease of Use (Rank 1)
Secondary Priority: Stability and Maintainability (Rank 2)
Lowest Priority: Researcher Visibility and Impact (Rank 7)
Full rankings (Lower average indicates higher priority, i.e., 1 = highest priority):
Broad Goals (aggregate ranking) | ||
| Feature Area | Average |
1 | Patron Discovery and Ease of Use | 2.29 |
2 | Stability and Maintainability | 3.07 |
3 | Usability for Repository Managers and Cataloguers | 3.96 |
4 | UX and Design Improvements | 4.25 |
5 | Interoperability and Scholarly Discovery | 4.57 |
6 | Accessibility Improvements | 4.61 |
7 | Researcher Visibility and Impact | 5.25 |
This chart shows the full distribution of broad goals in the forced ranking. (Note that forced ranking did not permit ties.)
3. Technical Problem Areas: Ranked
When asked to rank 13 specific technical challenges, the community identified the following top concerns:
Search and Faceting Performance (Rank 1)
File Upload Reliability & Error Handling (Rank 2)
Collection Management Features (Rank 3)
Accessibility & UX Consistency (Rank 4)
Full rankings (Lower average indicates higher priority, i.e., 1 = highest priority):
Problem areas (aggregate ranking) | ||
| Problem Area | Average |
1 | Improve Search and Faceting Performance | 4.93 |
2 | Improve File Upload Reliability and Error Handling | 5.11 |
3 | Improve Collection Management Features | 5.43 |
4 | Improve Accessibility and UX Consistency | 5.57 |
5 | Improve Analytics and Reporting Tools | 5.61 |
6 | Improve Workflows for Works with Large Numbers of Files | 5.93 |
7 | Improve Metadata Flexibility and Validation Tools | 7.04 |
8 | Improve Bulkrax Stability, Coverage, and Error Clarity | 7.39 |
9 | Improve Preservation and Export / Backup Capabilities | 7.61 |
10 | Improve User Roles, Permissions, and Group Management | 7.68 |
11 | Improve Repository Branding and Theming Options | 8.25 |
12 | Improve Startup and Installation | 9.75 |
13 | Improve Hyrax Compatibility and Upgrade Path | 10.71 |
It is clear from comments on the survey that the “Search and Faceting Performance” priority blends two distinct concerns: internal in-app search (facets, relevance, navigation) and external discoverability (indexing in Google and similar search engines, including Google Scholar). HykuUp respondents prioritized this area more strongly than non-HykuUp respondents (avg rank 4.0 vs 5.3; 62.5% vs 30% in top 3), and open comments from HykuUp users explicitly frame discoverability as web search indexing, identifying a particular pain point for this cohort. This means the #1 “search” priority likely represents two related but distinct workstreams.
The lowest technical priorities were Hyrax Compatibility/Upgrade Paths and Startup/Installation, suggesting that for the majority of the community, the difficulty is not in getting the software, but in using it effectively at scale. However, this also reflects that most survey respondents are not self-hosted. For self-hosted respondents (3 out of 28), Startup/Installation was identified as the #2 problem area.
Improve Hyrax Compatibility and Upgrade Path ranks last, which reflects that this is a fairly opaque area to end users of the product.
4. Key Cohort Differences
A. Self-Hosted vs. Hosted Users
Self-hosted users appear to have different technical pain points. They rank Startup/Installation and Large File Workflows as their top concerns.
Hosted users (Notch8, PALNI/PALCI) focus almost exclusively on Search Performance and Analytics, as the infrastructure is managed for them.
B. Repository Size (Small <5k vs. Large 5k+ works)
Large Repositories are struggling with "Ingest" issues. Their top priorities are Workflows for Large Numbers of Files and Bulkrax Stability.
Small Repositories are focused on "Discovery." Their top priorities are Search Performance and Analytics/Reporting. This partially reflects high participation by Hyku 4 Consortia users, who did not have access to in-app analytics at the time of this survey.
Priority Gap Table by size of repository | ||||
Feature Area | Small Repo (<5k) Rank (larger number is lower rank) | Large Repo (5k+) rank | Priority Gap | Comments |
Bulkrax Stability | 8.7 | 4.3 | 4.4 | Large users are desperate for stable bulk imports; small users rely on it less. |
Search Performance | 3.8 | 6.9 | -3.1 | Discovery is the #1 pain point for small repos; for large repos, it's a secondary concern. |
Large File Workflows | 6.7 | 3.9 | 2.8 | Managing large files and file sets becomes a technical hurdle for larger repos. |
Metadata Flexibility | 7.4 | 5.1 | 2.3 | Large repositories require more sophisticated metadata validation and tools. |
C. Satisfaction Drivers
Beyond raw prioritization, satisfaction data reveals where improvements are most likely to shift user sentiment.
Dissatisfied users (Rank 1-3) are primarily frustrated by File Upload Reliability and Collection Management friction.
Satisfied users (Rank 4-5) have moved past core stability and are now asking for Search Optimization and better Data Insights.
5. Satisfaction and Confidence
Satisfaction and Confidence | ||
Measure (1–5 scale) | Responses | Mean rating (1-5) |
Current satisfaction with Hyku | 26 | 3.19 |
Confidence in Hyku’s future | 28 | 3.57 |
Across the full sample, respondents rated confidence in Hyku’s future modestly higher than current satisfaction (mean difference +0.38). Satisfaction and confidence also move together at a moderate level: respondents who are more satisfied today tend to be more confident about Hyku’s direction, while those who are less satisfied are generally less confident. In practical terms, the community’s outlook is not straightforwardly a reflection of current experience, but it is meaningfully shaped by it.
6. Next Steps
This 2026 analysis serves as a high-level diagnostic tool rather than a granular technical specification. By force-ranking broad strategic goals and technical challenges, the community has clarified that the immediate path forward must prioritize the foundational health of the platform and the end-user experience. While specific pain points like Search and Faceting Performance and File Upload Reliability have emerged as clear frontrunners for development, this survey was designed to identify these overarching pressures rather than dictate specific software solutions.
The findings demonstrate a community that is cautiously optimistic, with confidence in Hyku’s future (3.57 mean) slightly outstripping current satisfaction levels (3.19 mean). To bridge this gap and translate these high-level priorities into functional improvements, the community will undertake the following next steps:
Continuous Feature Refinement: We will continue to collect detailed community input regarding specific desired features and functional requirements via the Proposed Features and Needs wiki to ensure development aligns with the "Patron Discovery" and "Usability" goals identified here.
Data-Driven Roadmap Prioritization: Using the rankings from this survey—specifically the "Priority Gaps" identified between small and large repositories—we will continue to refine and prioritize the Hyku Technical Roadmap.
Governance and Sustainability: To address the secondary priority of "Stability and Maintainability," the community will focus on refining governance models and securing sustainable funding for long-term development and maintenance.
Annual Baseline Tracking: This survey will be conducted annually to track shifting priorities over time and measure our collective effectiveness in addressing the community's top technical concerns.