The metadata export is an important part of the library management system as the exported metadata is used not only for editing/cleaning records but also for integration with external systems. The purpose of this epic is to cover FOLIO exporting functionality of inventory records (instances, holdings and items) and underlying MARC records if those are available. The user of the system should be able to export all inventory data or selected records based on a different search criteria. The search criteria should allow for identifying records based on administrative data (cataloged date, created date, etc), inventory records (instance, holdings, items) or MARC fields The exported records should include bibliographical records (FOLIO instance record and/or MARC bib record), holding records (FOLIO and/or MARC) and holding records with Items. It should also be possible to export bibliographic records with holdings and items data. The supported format of the export should support most commonly used formats, like MARC, MARC-JSON, delimited files, PICA+, MARC XML, PICA XML It should be possible export records on as needed basis but also have them scheduled for re-occurring tasks. Exported files should be stored in a determined/configured location for a specific or configurable period of time. Access to the export functionality and exported files should be permission based. The order of the implemented functionality will be determined by SME. At this point FOLIO doesn't have functionality for storing authority records so for now Authority records are out of scope for this epic.

The metadata export is an important part of the library management system as the exported metadata is used not only for editing/cleaning records but also for integration with external systems. The purpose of this epic is to cover FOLIO exporting functionality of inventory records (instances, holdings and items) and underlying MARC records if those are available. The user of the system should be able to export all inventory data or selected records based on a different search criteria. The search criteria should allow for identifying records based on administrative data (cataloged date, created date, etc) or MARC fields The exported records should include bibliographical records (FOLIO instance record and/or MARC bib record), holding records (FOLIO and/or MARC) and holding records with Items. It should also be possible to export bibliographic records with holdings and items data. The supported format of the export should support most commonly used formats, like MARC, MARC-JSON, delimited files, PICA+, MARC XML, PICA XML It should be possible export records on as needed basis but also have them scheduled for re-occurring tasks. Exported files should be stored in a determined/configured location for a specific or configurable period of time. Access to the export functionality and exported files should be permission based. The order of the implemented functionality will be determined by SME. At this point FOLIO doesn't have functionality for storing authority records so for now Authority records are out of scope for this epic.

The metadata export is an important part of the library management system as the exported metadata is used not only for editing/cleaning records but also for integration with external systems. The purpose of this epic is to cover FOLIO exporting functionality of inventory records (instances, holdings and items) and underlying MARC records if those are available. On a high level the functionality should include: # The user of the system should be able to export all inventory data or selected records based on a different search criteria. # The exported records should include: ## Bibliographical records ## Holding records ## Holding records with Items ## Bibliographical records with holding and items # The export should support most common formats: ## MARC ## MARC-JSON ## PICA+ ## delimited files ## MARC XML ## PICA XML # The export should be possible on as needed basis but also be scheduled for re-occurring exports # Exported files should be stored in a determined/configured location for a specific period of time # Access to the export functionality and exported files should be permission based. The order of the implemented functionality will be determined by SME. Allows exporting of metadata records (instances, holdings and items) to a supported output format. Options for holdings to be included as integrated or separate files. Will need to export MARC bib records (including holdings and item data), and MARC holdings records? Will we need to export MARC authority records? What formats for output, especially Inventory records? maybe MARC, Inventory-JSON formats, delimited? * Inventory Instance: output as Instance-JSON, delimited, MARC (if MARC, use the SRS if available, otherwise simplified Instance to MARC mapping) * Inventory Holding: output as Holdings-JSON, delimited, MARC (if MARC Holdings in SRS, use that, otherwise simplified Holdings to MARC Holdings mapping) * Item records: output as Item-JSON, delimited [Question: is MARC output needed, if so would have to be in 9xx fields of a MARC bib or MARC holdings] * For MARCcat: only output as MARC or are additional formats needed? Make sure that Inventory records can be output as MARC bibs, MARC holdings, but with MARC being created on the fly, and NOT stored. That way libraries can output MARC if necessary, but can still edit as Inventory Instances or Holdings, rather than being forced to edit in MARCcat or outside of FOLIO Make sure the exported file is stored someplace (especially being sent to a 3rd party) in case it needs to be sent again or reviewed See/listen to MM SIG discussion of 25 July 2019. Scope of this epic currently defined as Inventory and MARC records; how will export of other types of records (Order records, Organizations, Users, etc) Note: confirmed with [~accountid:5af5ed55244bc90a106063c7] and [~accountid:712020:5d8e7a2f-2a77-4bb8-8d8d-368eaea8b5eb]: for the requests csv output (UIREQ-102), punctuation being used: * comma separating fields (data elements) * semi-colon separating multiple values within the same field (data element) Per [~accountid:70121:8d96963c-ce4c-478d-9023-2de35bc14b67], would be helpful to be able to output MARC SRS as MARC-JSON, which would allow us to offer the data as part of the reporting system, so that analysts could query them as part of creating reports. If we can only get them in MARC format, then we will need to come up with our own conversion process to JSON. FMIDs: ID541, ID542, ID543

The metadata export is an important part of the library management system as the exported metadata is used not only for editing/cleaning records but also for integration with external systems. The purpose of this epic is to cover FOLIO exporting functionality of inventory records (instances, holdings and items) and underlying MARC records if those are available. On a high level the functionality should support: # The user of the system should be able to export all inventory data or selected records based on a different search criteria. # The exported records should include: ## Bibliographical records ## Holding records ## Holding records with Items ## bibliographical records with holding and items # The export should support most common formats: ## MARC ## MARC-JSON ## PICA+ ## delimited files ## MARC XML ## PICA XML # The export should be possible on as needed basis but also be scheduled for re-occurring exports # Exported files should be stored in a determined/configured location # Access to the export functionality and exported files should be permission based. The order of the implemented functionality will be determined by SME Allows exporting of metadata records (instances, holdings and items) to a supported output format. Options for holdings to be included as integrated or separate files. Will need to export MARC bib records (including holdings and item data), and MARC holdings records? Will we need to export MARC authority records? What formats for output, especially Inventory records? maybe MARC, Inventory-JSON formats, delimited? * Inventory Instance: output as Instance-JSON, delimited, MARC (if MARC, use the SRS if available, otherwise simplified Instance to MARC mapping) * Inventory Holding: output as Holdings-JSON, delimited, MARC (if MARC Holdings in SRS, use that, otherwise simplified Holdings to MARC Holdings mapping) * Item records: output as Item-JSON, delimited [Question: is MARC output needed, if so would have to be in 9xx fields of a MARC bib or MARC holdings] * For MARCcat: only output as MARC or are additional formats needed? Make sure that Inventory records can be output as MARC bibs, MARC holdings, but with MARC being created on the fly, and NOT stored. That way libraries can output MARC if necessary, but can still edit as Inventory Instances or Holdings, rather than being forced to edit in MARCcat or outside of FOLIO Make sure the exported file is stored someplace (especially being sent to a 3rd party) in case it needs to be sent again or reviewed See/listen to MM SIG discussion of 25 July 2019. Scope of this epic currently defined as Inventory and MARC records; how will export of other types of records (Order records, Organizations, Users, etc) Note: confirmed with [~accountid:5af5ed55244bc90a106063c7] and [~accountid:712020:5d8e7a2f-2a77-4bb8-8d8d-368eaea8b5eb]: for the requests csv output (UIREQ-102), punctuation being used: * comma separating fields (data elements) * semi-colon separating multiple values within the same field (data element) Per [~accountid:70121:8d96963c-ce4c-478d-9023-2de35bc14b67], would be helpful to be able to output MARC SRS as MARC-JSON, which would allow us to offer the data as part of the reporting system, so that analysts could query them as part of creating reports. If we can only get them in MARC format, then we will need to come up with our own conversion process to JSON. FMIDs: ID541, ID542, ID543

All needs to be confirmed with SMEs: Allows exporting of metadata record to a designated output format - choice of formats depends on format of linked rich metadata records. Options for holdings to be included as integrated or separate files. Will need to export MARC bib records (including holdings and item data), and MARC holdings records? Will we need to export MARC authority records? What formats for output, especially Inventory records? maybe MARC, Inventory-JSON formats, delimited? * Inventory Instance: output as Instance-JSON, delimited, MARC (if MARC, use the SRS if available, otherwise simplified Instance to MARC mapping) * Inventory Holding: output as Holdings-JSON, delimited, MARC (if MARC Holdings in SRS, use that, otherwise simplified Holdings to MARC Holdings mapping) * Item records: output as Item-JSON, delimited [Question: is MARC output needed, if so would have to be in 9xx fields of a MARC bib or MARC holdings] * For MARCcat: only output as MARC or are additional formats needed? Make sure that Inventory records can be output as MARC bibs, MARC holdings, but with MARC being created on the fly, and NOT stored. That way libraries can output MARC if necessary, but can still edit as Inventory Instances or Holdings, rather than being forced to edit in MARCcat or outside of FOLIO Make sure the exported file is stored someplace (especially being sent to a 3rd party) in case it needs to be sent again or reviewed See/listen to MM SIG discussion of 25 July 2019. Scope of this epic currently defined as Inventory and MARC records; how will export of other types of records (Order records, Organizations, Users, etc) Note: confirmed with [~accountid:5af5ed55244bc90a106063c7] and [~accountid:712020:5d8e7a2f-2a77-4bb8-8d8d-368eaea8b5eb]: for the requests csv output (UIREQ-102), punctuation being used: * comma separating fields (data elements) * semi-colon separating multiple values within the same field (data element) Per [~accountid:70121:8d96963c-ce4c-478d-9023-2de35bc14b67], would be helpful to be able to output MARC SRS as MARC-JSON, which would allow us to offer the data as part of the reporting system, so that analysts could query them as part of creating reports. If we can only get them in MARC format, then we will need to come up with our own conversion process to JSON. FMIDs: ID541, ID542, ID543

Allows exporting of metadata record to a designated output format - choice of formats depends on format of linked rich metadata records. Options for holdings to be included as integrated or separate files. Will need to export MARC bib records (including holdings and item data), and MARC holdings records, Will we need to export ARC authority records? May also include output of EDIFACT orders. Make sure that Inventory records can be output as MARC bibs, MARC holdings, but with MARC being created on the fly, and NOT stored. That way libraries can output MARC if necessary, but can still edit as Inventory Instances or Holdings, rather than being forced to edit in MARCcat or outside of FOLIO Make sure the exported file is stored someplace (especially being sent to a 3rd party) in case it needs to be sent again or reviewed Note: confirmed with [~accountid:5af5ed55244bc90a106063c7] and [~accountid:712020:5d8e7a2f-2a77-4bb8-8d8d-368eaea8b5eb]: for the requests csv output (UIREQ-102), punctuation being used: * comma separating fields (data elements) * semi-colon separating multiple values within the same field (data element) Per [~accountid:70121:8d96963c-ce4c-478d-9023-2de35bc14b67], would be helpful to be able to output MARC SRS as MARC-JSON, which would allow us to offer the data as part of the reporting system, so that analysts could query them as part of creating reports. If we can only get them in MARC format, then we will need to come up with our own conversion process to JSON. FMIDs: ID541, ID542, ID543