Deprecated. Current page: Designing data import profiles in FOLIO
The FOLIO wiki contains documentation for Data Import. The batch processing confluence site contains specifications for specific data import jobs. This page covers aspects of data import profile design specifically for Cornell.
Job profiles
Naming conventions- vendor job profiles
Vendor loads that will be run by staff outside of batch processing should be carefully named in order to make it clear to the user what they are running. Job profiles differentiate based on the action being taken and the type of resource being acted on. In order to correctly apply statistical codes, some job profiles apply to specific acquisitions workflows. The person loading should carefully consider which type of record they are loading and ask batch processing if they have any questions.
Format: Vendor - verb(s) - resource type
Examples:
EBSCO - create and update - electronic monographs
Taylor and Francis - create - monographs
Coutts - update - shelf ready approval monographs
Naming convention- general purpose job profiles
FOLIO record type - verb - data source or description
Examples:
Holdings - create - location and call number from 952$b
Items - update - remove temporary location
Instances - mark for deletion
Naming convention- field mapping profiles
Mapping profiles should not have verbs
For holdings: Electronic (if applicable) - holding type - holdings
Example: Electronic journal holdings
For items: Item - status - barcode presence
Example: Item in process with barcode
Mapping profiles
Using CUL's statistical codes
Statistical codes replace, in part, some of the data we used to record in a 948. When you are building an import profile, consider the data batch processing used to rely on most frequently: source of acquisition, special format, date, and file name. When designing a profile for a specific type of acquisition or special format, make sure to add the appropriate statistical code to your profile.
Programmatic use of the 948
Use of the 948 is no longer required for catalogers, they are using the transaction stats note in the holdings record. However, the 948 remains in use for some batch processes and can be added to files as needed. Notably, POOF, ArchivesSpace and CaiaSoft integrations may use the 948.
If you add a 948, please continue to use the tag as defined in the confluence page "local tags". It is not recommended that you create 948s using dynamic data with the data import module. In other words, if you want to record the date and file name of what you are importing, add that data with MARC Edit prior to importing the file, don't use a data import mapping profile to add it. Adding this data with MARC Edit prior to loading may make it easier for you to locate and correct records if a mistake is made during an import. The data import logs may also help you do this.
If you want to add a new 948 to carry static special format and vendor information with data import, that is okay, but given other mappings in the profile should be unnecessary.