2019-01-28 Meeting notes

5min

External group report

Dana

30min

Single vs. separate campus repositories

David

• Context: The need for multi-tenancy

  • 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 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

  • Cons

    • Unknown scaling issues

    • Little flexibility for metadata, branding

    • Trading technical costs for organizational costs?

What to do with desire for digital library platform?

David

Secondary systems: Faculty profiles, open access publishing

David