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

      • Complex AWS, version control set-up

      • Separate design, metadata, authentication work

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

    True of other systems we use

    • Alma, Primo, apps developed by the CO

• Single instance alternative – see demo.

  • Pros:

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

    • Uniform design, metadata, authentication

    • More easily accommodate systemwide initiatives?

      • Academic technology projects

      • AB 2192

  • Cons

    • Unknown scaling issuesLittle flexibility for local metadata

    • Little to no flexibility for metadata, brandingTrading technical costs for organizational costs?branding, institutional identity

      • Was listed as very important by campuses

    • Unknown scaling issues

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

      • DOI minting

    • Requires consensus on most decisions

What to do with desire for digital library platform?

David

Secondary systems: Faculty profiles, open access publishing

David