ReCON_Core_Concepts

Key Aspects of Retrospective Conversion:
Purpose:
To migrate historical or non-digital records into a searchable, accessible, and interoperable digital database.
To improve discovery, preservation, and management of library resources.

Scope:
Applies to bibliographic records (e.g., books, journals, manuscripts) and authority records (e.g., authors, subjects).
May include item-level data (e.g., barcodes, call numbers, circulation history).

Methods:
Manual Entry: Data is manually typed into the system, often used for small collections or highly specialized materials.
OCR (Optical Character Recognition): Scanned images of catalog cards or printed catalogs are converted to text using OCR software.
Outsourcing: Libraries may contract third-party vendors specializing in retrospective conversion services.
Batch Loading: Pre-existing digital records (e.g., from spreadsheets or older ILS exports) are imported in bulk using MARC (Machine-Readable Cataloging) standards or other formats like CSV, XML, or JSON.

Standards:
Records are typically converted to MARC 21, UNIMARC, or Dublin Core formats for compatibility with modern library systems.
Authority control (e.g., LC Subject Headings, Dewey Decimal Classification) is applied to ensure consistency.

Challenges:
Data Cleanup: Legacy records may contain inconsistencies, missing fields, or outdated terminology requiring normalization.
Cost and Time: Large-scale conversion can be resource-intensive.
Quality Assurance: Validation is critical to ensure accuracy, completeness, and adherence to cataloging standards.

Benefits:
Enhances accessibility for patrons and staff.
Facilitates interlibrary loan (ILL) and resource-sharing initiatives.
Supports preservation by reducing reliance on physical or obsolete formats.
Enables advanced search and analytics (e.g., faceted search, usage statistics).

Tools and Protocols:
MARC Edit Software (e.g., MarcEdit, MARC Report).
Library Services Platforms (e.g., Koha, Alma, Sierra).
Data Transformation Tools (e.g., OpenRefine, XSLT scripts).
Protocols: Z39.50, SRU, or OAI-PMH may be used for data exchange during conversion.

Example Workflow:
Inventory: Audit existing records to determine scope.
Digitization: Scan or export legacy records.
Conversion: Apply OCR or manual entry to create digital records.
Standardization: Map fields to MARC or another target schema.
Validation: Review for errors, duplicates, or missing data.
Loading: Import into the ILMS or catalog.
Testing: Verify searchability and integration with other systems.