Technical

How is the repository architected to allow for use by multiple institutions? How will it be hosted and maintained? What will be the processes to create specifications and implement plans for development?

A collaborative repository, particularly one that is open source, presents special technical demands for consideration.  Of particular importance is whether or not the repository is multi-tenant, one shared system, or a series of systems.  This and other factors (such as technical capacity) inform whether a repository should be hosted locally or through a service provider, and if/how the platform can be customized and improved.

Here are a few examples of technical strategies employed by Hyku for Consortia:

• Structural diagrams: Structural and Functional Vision and Collaborative Workflows
• Development Specifications and Management: GitHub Project Board
• Developer Statement of Work: Software Services by Scientist.com Hyku Commons 2022 Q4 SOW
• Platform Release/Update Notes: Hyku Commons Patch Notes
• Maintenance and Support: Hyku Commons Performance, Problem Reporting, and Maintenance
• Platform Monitoring: Hyku Commons Production Status - StatusIQ
• Accessibility: Hyku Accessibility Audit