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 the aspect aspects of data import profile design specifically for Cornell.
...
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.
...