Data Export Overview
- Magda Zacharska
Settings
Default Mapping Profiles
| Default profile type | MARC | FOLIO | Notes |
|---|---|---|---|
| Default instance mapping profile | SRS | on the fly | List of fields generated on the fly for instance records: Data Export: Default Mapping Profiles |
| Default holdings mapping profile | SRS | on the fly | List of fields generated on the fly for holdings records: Data Export: Default Mapping Profiles |
| Default authority mapping profile | SRS | N/A |
When the record is exported from SRS (instance or holdings), it is exported in its entirety without any validation during the export job. If the record contains invalid data (for example, a public note is stored in the field for staff note), the record will be exported as is. If the MARC record is invalid, data export will also attempt to export the record as is. If the record exceeds the maximum size for a MARC record, the error will be displayed in the error log, as described in MDEXP-422.
Custom Mapping Profiles
Custom Mapping Profiles offer greater flexibility in defining the data to be included in the export. During the export, only one type of mapping profile can be used — either the default mappings profile or a custom mapping profile; they cannot be used simultaneously. Unlike default mapping profiles, custom mapping profiles can be edited. However, once a custom mapping profile is associated with a job profile used in an export job, it cannot be edited anymore; it can only be duplicated. The ability to edit mapping profiles after they have been used will be addressed in the future (UXPROD-2708)
When users create a custom mapping profile, their initial step involves selecting the inventory record types to be utilized in export jobs. They can choose either SRS or Instance records. If the 'Source Record Storage (entire record)' option is selected, and the instance lacks an underlying SRS record, a MARC record will be generated based on the default mapping rules. The Transformation form is used to specify mappings for other record types. The typical scenario involves exporting a MARC Bib record enriched with holdings and items data.
Examples of Custom Mapping Profiles
Example 1
Entire SRS record and holdings and items data as follows:
Holdings - HRID | 901 $a | both indicators blank |
Holdings - ID (UUID) | 901 $b | both indicators blank |
Item - Barcode | 876 $a | both indicators blank |
Item - HRID | 902 $a | both indicators blank |
Item - ID (UUID) | 902 $b | both indicators blank |
Example 2
Entire SRS record and holdings and items data as follows:
Holdings - Electronic access - Resource - Materials specified | 856 $3 | first ind: 4, second ind: 0 |
Holdings - Electronic access - Resource - URI | 856 $u | first ind: 4, second ind: 0 |
Holdings - Electronic access - Resource - Public note | 856 $z | first ind: 4, second ind: 0 |
Item - Barcode | 876 $a | both indicators blank |
Item - HRID | 902 $a | both indicators blank |
Item - ID (UUID) | 902 \\ $b | both indicators blank |
The recent bugfest has also examples of the mapping profiles that are close to the real life examples: https://bugfest-poppy.int.aws.folio.org/settings/data-export/mapping-profiles?sort=name
Note: Ideally, the transformation form should contain all fields for each record type but some fields were omitted in the initial implementation, some were added after the data export went live. The discrepancy is listed in https://folio-org.atlassian.net/wiki/x/RGwV