Spike card to investigate transformation of BIBFRAME resource descriptions into MARC. 

The Library of Congress must have the ability to capture cataloging work performed in the Marva application as MARC records to be included in its CDS - Cataloging Distribution Service.  This work is inclusive of edits made to existing resources as well as resource descriptions cataloged from scratch natively in Marva. 

Secondarily, creating MARC records derived from BIBFRAME resource descriptions provides a path for keeping FOLIO in synch with the BIBFRAME database. For example, a common cataloging use case could involve metadata that is input into FOLIO as a MARC record, and upgraded in Marva as a full resource. Returning the completed resource description back to FOLIO SRS as a derived MARC record reinforces the integrity and completeness of both databases. 

To keep the size of the scope manageable, the investigation for transforming BIBFRAME into MARC should be limited to the same "stub" fields described in MODLD-131

The goal of the spike card, then, is to investigate how to "recreate" MARC stub records by deriving them from the corresponding BIBFRAME resource descriptions. 

Question(s)

• For fields that map to multiple MARC tags, need direction in how values in the BIBFRAME resource description can be mapped accurately to multiple tags and subtags.

• Governance rules around BIBFRAME resource descriptions will also impact transformation rules needed for keeping FOLIO and BIBFRAME databases in synch

• Spell out use cases for synching, e.g. when should a BF resource description overlay a record in FOLIO SRS? When should it merge with a record in SRS? Specifically identifying tags in the MARC record that aren't present (mapped) in the BF resource description.