Match every output to its receiving role.
ENG-024_0007.tifIdentify the object store and document-class rules
IBM documents FileNet Content Engine documents as objects with content elements, object properties, and API environments. The customer’s FileNet administrator identifies the target object store, document class, folder containment, required properties, choice lists, and data types. The team also defines expected MIME types, rendition roles, versioning behavior, security constraints, and the responsible owner for destination permissions.
These choices are captured in a data dictionary before production. The dictionary shows how source material and index values become FileNet property values, including date normalization, multi-value rules, required fields, and controlled choices. It also distinguishes an archival image master from the delivery derivative where both are requested.
Prepare content and properties for the approved ingest
A FileNet package ties each document file to a stable record ID, class, target folder or containment rule, property map, MIME declaration, OCR status, and checksum. It can include a neutral sidecar for review and reconciliation as well as the format required by the customer-approved loading process. The actual API or ingest procedure is selected and run with the customer’s FileNet team.
When the project includes content elements or renditions, the customer specifies the role of each file and the order or versioning rule to be tested. This prevents an access PDF, TIFF master, or extracted text file from being treated as interchangeable without a documented repository decision.
- Object store, document class, and containment location confirmed
- Properties, choice lists, and MIME/rendition expectations documented
- Security, versioning, and ingest ownership retained by the customer team
Test class, properties, content, and access
A representative test batch allows the authorized FileNet team to validate class assignment, required property values, content rendering, folder placement, permissions, and the chosen ingest process. National Microfilm reconciles identifiers, file counts, and exceptions against the delivery manifest. The customer confirms final release after destination-side validation and any class-specific correction decisions.
Illustrative FileNet property map
The target class controls actual property symbols and requirements. This sample shows the information normally reviewed in a FileNet delivery crosswalk.
| Prepared field | Example value | FileNet mapping review |
|---|---|---|
| document_class | Correspondence | Customer-designated document class |
| target_folder | /Administrative Files/1954 | Containment rule |
| title | Letter to Procurement | Required/optional property |
| record_date | 1954-04-19 | Date property |
| mime_type | application/pdf | Content element expectation |
Common questions
Can you load content through a FileNet API?
API-based loading is scoped with the customer’s FileNet team after the object store, class, permissions, access method, property validation, and test process are established.
What FileNet information is needed to start?
The object store, document class, folder rules, required properties and choice lists, expected file/MIME types, security and versioning needs, ingest owner, and acceptance test plan.
Sources & further reading
These references explain technical formats, standards or destination requirements. They do not imply endorsement of National Microfilm.