Skip to end of banner
Go to start of banner

Further Suggestions for Data Cleanup

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Data Clean Up Recommendations

The following recommendations for data cleanup may or may not be necessary for all libraries.

  • Fines, fees: clean up fines, fees, or other transactions that are older than a certain date and/or less than a certain amount, that should be forgiven;

  • Patron files: clean up and/or purge patron records that are inactive or expired and have no outstanding items, fines, fees, or other transactions;

  • Clean up of brief order records that are old, should have been closed, or have been inactive for years;

  • Statuses and codes: standardize and clean up any coding/tagging errors that may prevent items from being mapped to your designated Alma locations, e.g., 852$k BK, Book, Monograph;

  • Weeded items: purge prior to cutover;

  • Barcodes: identify and re-barcode any duplicate or unintentionally empty item barcodes;

For a more complete list of data clean up suggestions, Ex Libris has prepared Getting Ready for Alma and Discovery Implementation, Appendix B - Optional Data Preparations.

Cleanup Subject to Met & Cat Subcommittee Consideration

Please wait for further guidance before doing any cleanup on the items below. Information will be posted as it becomes available.

  1. Control field coding: records that need to be brought up to minimum standard, e.g., records for visual resources that need to be updated. Further discussion is needed to determine if this work can be done prior to final cutover or after Go-Live.

  2. Local tagging 09x, 59x, 69x, 77x/78x: ensure that local tags (if any) identified in your records are marked with subfield 9 with only the word LOCAL (no spaces, punctuation, or any other characters). For more information, see Alma Migration Considerations for Consortia - Ex Libris Knowledge Center (exlibrisgroup.com) Note: if you become aware of additional local tags in your data cleanup, ensure line 21 in your final migration form is adjusted to reflect the additional local fields.**

  3. Local tagging 950 - 999: will need to be considered once the Met/Cat has defined local tags for the consortia.

Additional Resources

Primo https://knowledge.exlibrisgroup.com/Primo/Training

The training links below will help you become familiar with Primo discovery configuration. This training section contains separate sections for Primo Training (for configuration via Primo Back Office) and Primo VE Training (for configuration via Alma dashboard):

  • No labels