Yüklənir

Passport Continuity

Passport Continuity records how a Digital Product Passport's publications and supporting evidence are preserved, verified and maintained through operational changes. A Passport Continuity Record is evidence of a preservation operation and its subsequent checks; creating it alone does not prove that a usable independent backup exists.

For example, a responsible company can preserve an item's publication history, download a ZIP containing its manifest and retained documents, place it in approved storage and retain a receipt. A later verification or restoration decision records whether the required material remains usable.

Preserving and verifying

An authorized passport publisher works in the passport detail's continuity section:

  1. Select Preserve publication history after at least one publication exists.
  2. Inspect the preservation record and download its archive.
  3. Use Verify preserved documents to check the preserved material.
  4. Place the archive in the company's approved destination and use Record offsite preservation receipt with genuine retained receipt evidence.

Actualog does not automatically transfer this archive to an external destination. Recording a destination name without actually storing the archive does not complete offsite preservation.

Restore missing preserved bytes verifies the ZIP and can restore missing private files. Restore Actualog's database metadata through the normal database-backup procedure first. This operation does not reconstruct the entire application database or overwrite existing files whose bytes differ.

Holds and retention

The selected profile supplies applicable preservation rules where configured. Hold decisions record a reason and retained decision evidence. A passport's active reader state and the retention of internal evidence are distinct decisions. A hold does not publish restricted documents or authorize new product editing.

The passport detail also supports a proposed transfer to a named receiving company, an effective date, a mandate revision and a reason. The receiving party must accept the transfer with its own authority. Historical publications retain their original information.

Where an accepted transformation event creates a successor, link the relevant predecessor passports and event. Multiple predecessors can be represented; cyclic lineage is rejected. A successor relationship must describe a supported physical transformation, not a way to reuse an old passport identifier for an unrelated item.

Who maintains continuity

Product Governance Managers and Company Administrators with publication authority maintain preservation operations. Responsibility transfers also require the relevant operator-management authority for the parties. Operational delegation can authorize a partner within its stated scope and validity.

Review verification issues, receipt evidence, access and restoration results periodically. Retirement or termination must follow the configured profile and accepted lifecycle facts. A supported recycling-based termination requires an accepted recycling event; ordinary catalog removal is not that event.

Related topics: Maintaining Published Passports, Passport Publication Versions, Product Lifecycle Events.