Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

Date

Attendees

Goals

Notes

  • KriKri Datastore Requirements
    • Based on assumptions that we need LDP and SPARQL; need to support generalized schema for RDF (i.e., not just DPLA MAP).
    • Scaling up vs. Scaling out - need to scale up first. We scale out if we have use cases to support it. 
    • Open source - part of assumption that we prefer FLOSS is based on our mission. 
      • Cost/benefit - internal business need trumps tech team principle if there's no other option
      • Keeping smaller scale is OK as well. 
      • New requirements:
        • MUST be a production-ready FLOSS persistence implementation that the software supports
        • SHOULD be a FLOSS implementation for DPLA that provides commercial support, etc. 

Action items

  •  
  • No labels