Submit enhancement requests here. Follow progress on Trello.
These are the principle development tasks that we have contracted with Notch8 to complete as part of our Hyrax implementation. In addition to these development tasks, Notch8 will be providing second-tier, in-depth technical support, which we will call upon for timely assistance with particularly challenging problems, bugs, or emergencies. Chancellor Office staff will be providing general management and first-tier support for the system.
1. Long-term Preservation Using Glacier
With the current DSpace system, the CSU has a custom-built process that pushes an archival copy of each submitted item to an EC2 / Glacier bucket for long-term preservation. There is also a custom-built process to retrieve the item from Glacier, should the CSU need to. The CSU needs a firm to put in place a similar long-term preservation and retrieval process for items submitted to Hyrax.
2. Handle Service Integration
One of the key features of any institutional repository is a persistent identifier for each item. The CSU used the Handle service in the past with DSpace for this purpose, and campuses have come to rely on it. We will need a firm to both (a) resolve existing handles to their new location in Hyrax using identifiers that are being migrated to the new system along with other metadata for each item from DSpace, and (b) mint new handles for new items that are submitted to Hyrax.
3. Campus-limited View
We are currently implementing a shared Hyrax instance where library staff and end-users from multiple CSU campuses will be working in the same instance. When users authenticate, they will be assigned to a group that represents their campus (e.g., ‘sandiego’, ‘fullerton’, ‘longbeach’, etc.). Currently, Hyrax allows users to set ‘private’, ‘public’, or ‘institution’ view access to items. The ‘institution’ view allows any authenticated user to view the item, so in our case, CSU user regardless of which campus they are at. The CSU needs a firm to add a fourth option, to allow only users from a particular campus to view the item – that is, only users from the same campus group as the user who uploaded the item.
4. SWORD Service
Several CSU campuses use third-party ETD management systems – including Proquest ETD Administrator and a home-grown system at Cal State Northridge – to manage the thesis and dissertation lifecycle. The final step in that lifecycle is the automated deposit of the thesis into ScholarWorks. These third-party thesis management systems all support SWORD, a lightweight protocol that allows external systems to deposit content into an institutional repository. The CSU needs a firm to build a SWORD service into Hyrax to support both these thesis and management system and other potential third-party systems that would utilize SWORD.
5. Speed-up Data Migration into Fedora, If Possible
By far the most time-consuming part of the project is migration of existing data and files from DSpace into Fedora. Based on the Current estimates, we are projecting 12 months for this part of the project. The CSU needs a firm to provide a review of our existing process and provide recommendations on ways to speed it up, if possible. Additionally, we need a firm to provide recommendations around the potential implementation of Valkyrie.