Within our IMLS grant project, we have been working hard with our product management team and developer Notch8 to define and develop consortially-focused improvements to Hyku. For example, last month we shared some logistics for building collaborative workflows, working towards a master dashboard to control multi-tenant user permissions.
At the same time as these development activities are taking place, this project has also focused on the practical aspect of making the existing version of Hyku usable for our consortial partners to pilot as a working institutional repository. Our work has thus branched into two separate areas: Development and Production.
The Production arm of our work focuses on readying the existing Hyku Commons product for real-world pilot use starting this summer. As a result of user testing from both the PALNI and PALCI sides, we’ve been submitting tickets for small bug fixes and minor improvements which are now happening parallel to the development of features as outlined in the IMLS grant. Notch8 has devoted a lot of resources to our project in both arenas, and we’ve established a great working relationship and clear communication of needs from both sides.
To date we’ve created two clear and separate working instances of Hyku for Development and Production. First, the Development instance acts in a number of purposes:
Second, the Production instance is where work is deployed once tested in the Development environment and also where pilot repositories will be built. It will be publicly available as a working repository soon.
We’ll share the Hyku Commons product (ie, our Production instance) when it has pilot content that is ready to be viewed. For now, checkout the demo video below for a brief look at our Development environment. PALCI and PALNI libraries can request a test repository in the Development instance using this form.
Five minute Hyku Commons demo