Match every output to its receiving role.
ENG-024_0007.tifDefine the repository model first
Laserfiche organizes content around folders, metadata, templates, and full-text indexing. Before production, the customer identifies the repository and destination folder structure, selected template, named fields, field data types, required values, and any records or security rules that affect import preparation.
The administrator also identifies the approved ingest process, the responsible access owner, and the environment where a sample can be reviewed. This keeps record classification and controlled values anchored to the customer’s configuration rather than to generic field names. OCR expectations are stated separately: searchable text, an external text file, or an exception flag for material needing review.
Prepare files and a conservative metadata crosswalk
Each record receives a stable identifier used across the image or PDF, OCR output, metadata row, and reconciliation report. The data dictionary records the source value, the normalized value, target template field, format, repeatability, and handling for blanks or unrecognized values. File names and folder paths follow the agreed repository preparation rules.
Where a customer supplies a template or import worksheet, we map to that approved artifact. We do not presume a particular automated connection, API, or import utility. The delivery package remains useful even when the final repository load is performed by the customer’s authorized staff through their established process.
- Template name and required field list approved by the repository owner
- Folder hierarchy and document naming convention documented
- OCR status and source-image references retained for traceability
Review a representative test batch
A sample batch lets the customer confirm folder placement, template selection, field values, document readability, and search or retrieval expectations before full delivery. National Microfilm reconciles file counts and identifiers and flags records that lack a required value or need a customer decision. The repository administrator confirms permissions, records policies, and final acceptance within the customer environment.
Illustrative Laserfiche preparation map
The final template and field names are customer-provided. This neutral example is designed for review and transformation into the approved import process.
| Prepared field | Example value | Repository mapping review |
|---|---|---|
| record_id | NM-000392 | Delivery and reconciliation identifier |
| folder_path | Administrative Files/1958 | Customer-designated folder |
| template | Correspondence | Selected customer template |
| record_date | 1958-11-03 | Approved date field |
| ocr_status | complete | Search-text or exception tracking |
Common questions
Do you provide a Laserfiche connector?
We prepare an import-ready delivery package around the repository structure, templates, and workflow your team approves. The final ingest method is selected after the specific environment, access, and test process are confirmed.
What does our Laserfiche administrator need to provide?
The destination repository and folders, selected template and fields, required values and formats, security or records considerations, approved ingest process, and a test/acceptance contact.
Sources & further reading
These references explain technical formats, standards or destination requirements. They do not imply endorsement of National Microfilm.