Page Comparison

5min

External group report

Dana

30min

Single vs. separate campus repositories

David

• Context: The need for multi-tenancy

  • Our other systems all use some kind of multi-tenancy

    • Alma, Primo, apps developed by the CO

  • DSpace

    • In the beginning: Separate instances, lots of problems

    • Now: Atmire custom multi-tenant DSpace

  • Samvera Hyrax

    • Hyku was meant to fill this role

      • Overdue, still in-development

      • Upgrades after customizations would be difficult (compared to Hyrax)

    • Aaron’s model: Separate front-end instances, consolidated back-end

      • 25 prod servers + equal number development servers

      • Complex AWS, version control set-up

      • More flexibility than what we’ve previously had

      • Separate design, metadata, authentication workconfigurations

        • Some of this can be copied between instances, with attending overhead

• Single instance alternative – see demo.

  • Pros:

    • Simpler set-up, can focus limited resources on this one instance

    • Uniform design, metadata, authentication

    • Improved discovery

    • More easily accommodate systemwide initiatives?

      • Academic technology projects

      • AB 2192

  • Cons

    • Little flexibility for local metadata

    • Little to no flexibility for branding, institutional identity

      • Was listed as very important by campuses

    • Unknown scaling issues

    • Unknown issues around third-party integrations if not all campuses participate

      • e.g., DOI minting

    • Requires consensus on most decisions

      • Scope of the repository (see next issue)

      • Metadata

What to do with desire for digital library platform?

David

Secondary systems: Faculty profiles, open access publishing

David