Appearance
The OAIS reference model (ISO 14721) is a conceptual blueprint that names the functions, responsibilities and information packages a digital archive needs to preserve content and keep it usable for a defined audience over the long term. To apply it, you map your existing workflow onto its six functional entities, define your designated community, and ensure every object travels from a SIP through an AIP to a DIP with the preservation metadata attached. OAIS does not tell you which software to buy; it tells you what must be true regardless of the tools.
What does OAIS actually require of me?
OAIS sets six mandatory responsibilities. You must negotiate and accept information from producers, gain sufficient control to preserve it, determine a designated community, ensure the content is independently understandable to that community, follow documented preservation policies, and make the content available. None of these mention a specific product. A county record office meeting them with spreadsheets and a written ingest procedure is more OAIS-conformant than an institution running expensive software with no defined community.
Mapping your workflow to the six functional entities
Walk an object through your current process and label each step with an OAIS function:
| OAIS function | What it covers | Your real-world equivalent |
|---|---|---|
| Ingest | Receiving and validating submissions | Accession email, virus scan, checksum on receipt |
| Archival Storage | Storing AIPs, refreshing media | Your NAS plus offsite copy |
| Data Management | Descriptive and admin databases | Catalogue, accession register |
| Administration | Policy, agreements, audits | Deposit agreements, preservation policy |
| Preservation Planning | Monitoring formats and tech | Format risk reviews, migration plans |
| Access | Generating and delivering DIPs | Reading-room export, web delivery |
Gaps usually appear in Preservation Planning, which small archives skip entirely.
How do I define my designated community?
Be specific. "Researchers" is too vague to act on. Instead write something like: "Social historians familiar with 19th-century English parish administration but not assumed to read TIFF tags or SQL." That sentence decides your obligations. If your community cannot read a format unaided, you owe them representation information — a data dictionary, a format specification, software notes — bundled with the object.
Building OAIS information packages
The model revolves around three packages. Practically, a BagIt bag with a bag-info.txt, a checksum manifest and a PREMIS event log makes a defensible AIP.
text
aip-2024-0142/
bagit.txt
bag-info.txt
manifest-sha256.txt
data/
content/parish-register-1841.tif
metadata/premis.xml
metadata/dublin-core.xml
metadata/representation-info.pdfThe SIP is what arrived; the AIP adds fixity, provenance and representation information; the DIP is whatever you generate for a user (often a watermarked JPEG plus a citation).
Common pitfalls when applying OAIS
The most frequent mistake is treating OAIS as a compliance checkbox rather than a thinking tool. Other traps: leaving the designated community undefined, storing AIPs with no preservation metadata (so you cannot prove provenance later), and conflating backups with preservation — a backup restores yesterday's bits, but it does not monitor format obsolescence or record events.
A practical first-week plan
Spend day one writing your designated community statement. Day two, draw the six-box diagram and annotate it with your real steps. Day three, run a checksum tool across one collection and stand up a manifest. Day four, draft a one-page preservation policy citing OAIS responsibilities. Day five, list your three biggest gaps and assign owners. You now have a defensible OAIS alignment without buying anything.
Key Takeaways
- OAIS is a reference model, not software; it defines what must hold, not how.
- The six mandatory responsibilities are achievable with documented manual procedures.
- A clear designated community statement drives every downstream decision.
- Objects must flow SIP → AIP → DIP, with the AIP carrying fixity and provenance.
- Preservation Planning is the function small archives most often omit.
- A BagIt bag plus PREMIS and representation information is a defensible AIP.
- Do not mistake backups for preservation — they are necessary but not sufficient.
Frequently Asked Questions
What is the OAIS reference model in one sentence?
OAIS (ISO 14721) is a conceptual framework describing the functions and information packages an archive needs to preserve digital objects and make them usable by a designated community over the long term.
Do I have to implement every OAIS function to be compliant?
No. OAIS defines mandatory responsibilities but not a software architecture; a small archive can meet them with documented manual procedures rather than a full repository system.
What is the difference between a SIP, an AIP and a DIP?
A SIP is the submission package you receive, an AIP is the preserved package you store with full preservation metadata, and a DIP is the dissemination package you generate for users on request.
Is OAIS a piece of software I can download?
No, OAIS is a reference model, not software. Tools such as Archivematica, Preservica and RODA are built to align with it, but OAIS itself is a written standard.
Who is the designated community and why does it matter?
The designated community is the specific audience you commit to keeping content understandable for; defining it sets the bar for what representation information and formats you must preserve.
How long does it take to map an existing archive to OAIS?
A focused gap analysis for a small collection takes a few days; the value is in the documented gaps, not in achieving perfection immediately.