Open one run for one asset or coherent asset package. Record why it is entering the repository, who supplied it, and its intended use. Keep unrelated assets in separate runs so rights, retention, and approvals remain auditable. Confirm the submitter can answer source and ownership questions before proceeding.
1
New acquisition
2
Newly created asset
3
Replacement or revised asset
4
Legacy asset migration
5
External partner submission
Register asset identity and source
Create the durable identity record before files are transformed. Capture the originating party and source location, then assign the repository identifier under the organization's naming policy. Do not reuse an identifier or derive it from a filename that may change.
Transfer source files securely
Transfer the source package through an approved secure channel and preserve it unchanged as received. Include sidecars, captions, manifests, and licenses that form part of the package. If transfer is incomplete, pause and obtain the missing components rather than creating a partial record.
Validate file integrity and safety
Run the approved malware scan and calculate a fixity value for each received file before editing or conversion. Compare any supplied manifest with the received package. Quarantine suspicious files and do not open them in production tools until the security exception is resolved.
1
Passed with no findings
2
Passed after remediation
3
Quarantined for investigation
4
Scan tool unavailable
5
Scan not applicable
Assess format and preservation needs
Identify the actual format using file-signature evidence where possible, not the extension alone. Compare it with the organization's preferred and acceptable format policy and document any dependency, encryption, or obsolescence risk. Keep the original file even when a preservation copy will be created.
1
Still image
2
Moving image
3
Audio recording
4
Text or document
5
Dataset
6
Design or three-dimensional asset
7
Web or interactive content
8
Mixed media package
1
Retain original only
2
Create normalized preservation copy
3
Create migration plan
4
Preserve software dependency
5
Escalate format assessment
Describe asset with controlled metadata
Create descriptive metadata using the local application profile, drawing on Dublin Core terms where they fit. Use controlled vocabularies for subjects, types, languages, and audiences; retain supplied spellings in provenance notes when normalization is necessary. Dates should follow the repository's ISO 8601 convention.
Confirm ownership and usage rights
Identify the rights holder and the evidence authorizing storage, transformation, and delivery. Record restrictions in operational language, including territory, channel, audience, and expiry. Never infer permission from file possession; an unknown or pending status must enter the rights-exception path.
1
Organization owned
2
Public domain
3
Licensed without material restrictions
4
Licensed with restrictions
5
Third-party permission pending
6
Rights status unknown
Resolve rights clearance exception
Hold release while the responsible owner resolves missing or uncertain permission. Obtain written evidence, narrow the planned use, or reject the asset. Record the decision and its authority; do not select a permissive outcome merely to advance the workflow.
1
Permission obtained
2
Use narrowed and approved
3
Restricted internal use only
4
Asset rejected from repository
5
Pending further legal review
Apply access classification and controls
Set repository access to the minimum audience needed for the authorized purpose. Align access with the rights record and information-classification policy, and distinguish viewing, downloading, editing, and administrative privileges. Where access is temporary, record an expiry or review trigger.
1
Public
2
Organization wide
3
Department restricted
4
Named users only
5
Legal or security hold
Create preservation copy and replicas
Create the approved preservation representation without replacing the received original. Store verified copies across the required failure domains and retain the transformation log. Recalculate fixity after transfer and conversion so the repository can detect later change.
1
Primary managed repository
2
Secondary managed repository
3
Geographically separate replica
4
Offline preservation copy
5
Approved cloud archive
Produce accessible delivery derivatives
Create delivery copies suited to the intended channel while leaving preservation masters unchanged. Apply accessibility features supported by the format and content, such as alternative text, captions, transcripts, structure, and reading order. Document why a provision is not applicable rather than silently omitting it.
1
Alternative text
2
Closed captions
3
Transcript
4
Tagged document structure
5
Accessible reading order
6
Not applicable with rationale
Perform metadata and media quality control
Review the files and record as a user would receive them. Verify identity, metadata completeness, rendition quality, accessibility behavior, rights markings, links, and checksum evidence. Return material defects for correction and repeat the affected checks before requesting approval.
1
Passed without changes
2
Passed after correction
3
Minor issue accepted
4
Returned for rework
5
Rejected from intake
Approval: Asset curator
Will be submitted for approval:
Register asset identity and source
Will be submitted
Validate file integrity and safety
Will be submitted
Assess format and preservation needs
Will be submitted
Describe asset with controlled metadata
Will be submitted
Confirm ownership and usage rights
Will be submitted
Resolve rights clearance exception
Will be submitted
Apply access classification and controls
Will be submitted
Create preservation copy and replicas
Will be submitted
Produce accessible delivery derivatives
Will be submitted
Perform metadata and media quality control
Will be submitted
Stage approved asset for delivery
After curator approval, place the approved derivative in the authorized delivery location and keep the preservation master protected. Verify the public or internal record resolves to the correct asset and honors access restrictions. Do not publish an asset rejected or still pending in the approval task.
1
Published publicly
2
Published with access controls
3
Staged for scheduled release
4
Deposited for internal use
5
Withheld from delivery
Record retention and review plan
Assign the applicable retention category and the next review date based on policy, contractual obligations, rights expiry, and business value. Link the disposition authority rather than making deletion an ad hoc action. Legal or security holds override routine disposition until formally released.
1
Permanent preservation
2
Contract term plus retention period
3
Business value review cycle
4
Regulatory retention schedule
5
Legal or security hold
Close asset intake record
Confirm the asset record, files, rights evidence, preservation replicas, delivery location, and review plan are linked under the persistent identifier. Summarize unresolved follow-up work and transfer ownership explicitly. Close only when another operator can reconstruct what happened from the record.
Optional cookies and similar technologies support analytics, advertising and visitor identification, and embedded content. Change or withdraw consent in Cookie settings. Cookie policy.