Frameworks, Analyses & Workcycles

Frameworks & Analyses

• Data Feed Requirements & Use

  • Enable innovation and reduce bureaucratic drag

  • Appropriately apportion risk, responsibility and accountability to actors

  • Data Provider Minimum Standards

    • Contribute only data that may be shared to facilitate public discovery

    • Agree that data may be used by other POD libraries for purposes such as research, testing, or development

    • Encouraged to provide data under permissive terms, with license (e.g., a CC0 waiver).

  • Data Consumers

    • Data in the lake is available to any POD participant to extract and reuse.

    • Participant must consume and reuse the data responsibly.

    • Contact originating library for uses outside minimum standards

• Data Provider and Usage Framework for POD

• Chart of Data Providers' handling of e-resource records

• MVP Lessons Learned and Next Steps

• POD to Production Planning (Data Lake NEXT)
  

Workcycles

• MVP

  • Goal:

    • Infrastructure for transmitting and receiving MARC data from multiple institutions and serving it back out for external normalization, analysis, and discovery indexing.

      • Support receiving and transmitting both full dumps and delta change sets

      • Enable external normalization, analysis, and discovery indexing, and basic reporting and data reconciliation

      • Help POD refine and develop operational models for a service based on the MVP

  • Team

    • Product Owner: Mark Matienzo (Stanford)

    • Tech Lead: Chris Beer (Stanford)

    • Scrum Master: Jessie Keck (Stanford)

    • Developers:

      • Stanford: Chris Beer, Jessie Keck, Jack Reed, Camille Villa

      • Brown: Adam Bradley, Hector Correa, Birkin Diana, Justin Uhr

    • UX Design Consultant: Gary Geisler (Stanford)

    • Data Liaison/Wrangler: Bob Persing (Penn)

  • Workcycle #1: Oct 26 - Dec 11, 2020

  • Resulting Product: POD Aggregator Site