1. E-library / Digital Repository
  2. Connections and source data
Reference

Connections and source data

Plan source identifiers, mapped fields and delivery receipts.

  • E-library / Digital Repository
  • Source collection
  • Document storage
  • Receiving repository
  • Identity directory

Systems to connect

  • Source collection. Bring item identifiers, file references and project context from the system that holds incoming material. Preserve the source record identifier with each requirement where it applies.
  • Document storage. Attach or reference the supporting file and retain its document date, external reference and verifier.
  • Receiving repository. Capture the delivery reference and the receiving endpoint’s receipt so a completed action can be reconciled to a particular item revision.
  • Identity directory. Match staff identities to People and role assignments before permitting review decisions or organization-scoped work.

How connections are governed

Agree field mappings per project, including source and target types, transform rules, versions and effective dates. Test one source item and one corrected item before a wider import. The delivery endpoint’s acknowledgement should be tied to the original operation key and source revision. If a result is uncertain, inspect the stored attempt, run and receipt before another action. Keep access to attached evidence within the roles used for the item and its organization.

Plan the import and inspect the data model.

Set up E-library / Digital Repository your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started