Match every output to its receiving role.
ENG-024_0007.tifStart with the target library and its rules
A SharePoint administrator identifies the target site, document library, folder or document-set convention, and the content types that govern each record. We use that information to organize the delivery package around the customer’s required columns, controlled choices, date format, and required-versus-optional values.
The discovery record also names the Microsoft 365 environment, product version or migration tooling in use, destination owner, and a permitted test location. If permissions, retention labels, ownership values, or user mapping affect the release, the customer administrator defines how those values are handled before the production batch is assembled.
Build a reviewable file and metadata package
A typical package pairs TIFF masters or PDF/PDF-A derivatives where requested with OCR text, a stable record identifier, a UTF-8 metadata sidecar, and a manifest of file counts and checksums. The field map makes each source value, normalization rule, destination column, and exception visible for review.
Microsoft migration tasks have their own prescribed CSV or JSON job fields. They are distinct from a project metadata map, so we transform the approved record data only into the customer’s selected task, import, or upload format. Creator or owner carry-forward is treated as a separately approved user-mapping concern when it is in scope.
- Document file and relative path tied to one record ID
- Content type and destination path confirmed by the library owner
- Required columns, controlled values, and exception codes documented
Test the approved workflow before release
A representative test batch checks that files land in the intended library location, expected columns are populated, OCR and file formats meet the stated use case, and exceptions are reported. National Microfilm reconciles the delivered identifiers, file counts, and checksums with the agreed acceptance criteria. The customer’s authorized administrator runs or approves the destination-side workflow and resolves tenant-specific permission, retention, or policy decisions.
Illustrative SharePoint field map
Actual column names and required values come from the target library. This example shows the kind of crosswalk reviewed before a test batch.
| Prepared field | Example value | Target use |
|---|---|---|
| record_id | NM-000241 | Reconciliation key / agreed column |
| title | 1958 purchasing correspondence | Title column |
| record_date | 1958-06-14 | Approved date column |
| document_type | Correspondence | Content type or controlled column |
| relative_path | pdf/NM-000241.pdf | Approved library folder path |
Common questions
Can you load records directly into our SharePoint library?
We prepare the files and metadata for the delivery method approved by your Microsoft 365 and SharePoint administrators. Direct loading is scoped only after destination access, permissions, schema, and the selected workflow are confirmed.
Can OCR text be delivered with the documents?
Yes. OCR can be supplied as searchable PDF text, separate text, or another agreed output. The administrator confirms how the selected SharePoint workflow should receive and retain that output.
Sources & further reading
These references explain technical formats, standards or destination requirements. They do not imply endorsement of National Microfilm.