Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Table of Contents

The mapping and job profiles add flexibility to the data export functionality and provide a an easy way for a user to execute a different type of export on the same data set or the same type of export on different data sets.  For example on a given list of record identifiers the ,  one user can export instances in MARC bib record only or decide to append on a given data set and another user can export instances with appended  some elements of the holdings and items records using the same data set


Table of Contents


Mapping profile

Default mapping profile

The system comes with a default mapping profile.  Export records with the default job profile will provide file MARC bib records for provided record IDs.  For instances that have underlying MARC records  stored in SRS , those records will be used in the export.  The instances without underling MARC record will have simplified MARC bib record generated.

Job profile

Each export must be associated with a job profile. The job profile provides a way of connecting a specific list of record identifiers with the mapping profile.   

Default job profile

The system comes with a default job profile that is associated with the default mapping profile.  Export records with the default job profile will provide file MARC bib records for provided record IDs.  For instances that have underlying MARC records  stored in SRS , those records will be used in the export.  The instances without underling MARC record will have simplified MARC bib record generated.

Creating a new job profile

In order to create a job profile, navigate to Settings → Data Export → Job profile.

...

Populate at least the required fields ( Name and Mapping profile) and click Save and close.  You should see the newly created job profile listed:


Honeysuckle: 
Export profiles can not be edited
SRS cannot be exported what is exported is the inventory mapped using the transformation

Transformation syntax - in the Transformation field 900||$a   - field number + indicators +$ + subfield

  • there are no wildcards