The scope of the feature is supporting is the export of resource descriptions in the Library of Congress' BIBFRAME 2 format. This output will allow LC to update its id.loc.gov site with metadata created natively in Marva. 

In scope

• FOLIO's data export module must be leveraged to support data export of BIBFRAME 2

• The data export module must point to an institution's Linked Data database as the sourcefile for conducting data export

• Setting the default export mapping profile to support LC's BIBFRAME 2 standard

  • Inclusive of Work entity and Instance entity

• Options for defining the data export, including

  • Export of a single resource description

  • Export of a set of resource descriptions 

    • a search query of bibliographic parameters

    • a set of system identifiers (e.g. UUIDs) Investigate creating immutable identifier for the purposes of overlaying

    • Delta updates: additions, updates and deletes

    • package (Work, Instance, Item) - Event / source data in scope , e.g. originated from Library of Congress

    • Administrative

      • Cataloging level

      • Cataloging rules applied to the creation of the resource

      • Timestamps

      • Conversion number

  • Export of the entire database of resource descriptions

  • Export of resources updated during a specified time range: e.g. daily, weekly, monthly

• Ability to create, edit, delete export jobs

• Ability to receive email notification when a job is completed

• NFR: ability to query and export automated jobs on predetermined schedule (e.g. every 5 minutes)

• Data export via API jobs

• Cataloger permissions governing data export (being addressed on MARC side)

Additionally, we will want to inherit / take advantage of existing and planned data export functionality including but not limited to:

• Ability to export large volumes into multiple files.

• Configurable maximum number of records per file

Out of scope

• Data export in other formats, such as MARC

• Data export functionality outside of FOLIO (e.g. for stand alone service)

• Item entity

• Hub entity (will be added to its own ticket)

Use case(s)

Proposed solution/stories

Links to additional info

• FOLIO data export redesign https://folio-org.atlassian.net/wiki/display/FOLIJET/Data+Export+redesign#DataExportredesign-ActivityDiagram

Questions

1. Will need to create new source type to be recognized in FOLIO.

2. Output of BIBFRAME 2 will also be dependent on data requirements for BIBFRAME 2

3. Rules for connecting resource descriptions with authorities

4. Need clarity / specificity on administrative data. "Start with all administrative data defined in the conversion and then determine if there are any fields that shouldn't be included in the export"

5. NOTE: discussed question about local fields. Local / tracking information should be handled and managed outside of the resource description. Referenced Local Fields Working Group examining this in Inventory Instance records. Differentiate between administrative local metadata vs. descriptive local data that pertains to a specific holding. 

6. Investigate options for data import to filter out / manipulate fields

7. Differentiate between local fields that should be discoverable vs. other local fields that should be suppressed from distribution. 

8. Jeff: Explore export of metadata through MARC and BF channels. Priority should be on export to id.loc.gov