1. Robin Dale RLG Robin.Dale@notes.rlg.org
OAIS Functionality
Robin Dale
RLG

2. Questions to be Answered (1 of 2)
What is OAIS functionality?
What are the functional entities of the OAIS reference model?
What does the reference model mean by ingest, archival storage, data management, administration, access, and preservation planning?
What are the characteristics of these functional entities

3. Questions to be Answered (2 of 2)
What role does each entity play in an archival information system?
What relationships are inherent in the model?
How is OAIS functionality similar to the functionality of a digital library or electronic records system?
Functionality caveats

4. OAIS Functional Model

5. Ingest Functionality
Receive/accept submission information packages (SIPs)
On media, via FTP
Perform quality assurance on SIPs
Checksums, system log files to catch read/write errors
Generate Archival Information Packages (AIPs)
To archive’s data formatting and documentation stds.
Extract descriptive information for data management
To support search and retrieval of AIPs
Coordinates updates to Archival Storage and Data Management
Transfers the AIPs and metadata to appropriate places

6. Ingest, continued

7. Archival Storage Functionality
Receives Archival Information Packages (AIPs) from Ingest
Adds to permanent storage
Manages storage hierarchy
Refreshes/replaces media
Performs error checking
Provides disaster recovery capabilities
Duplication of contents for off-site storage
Provides AIPs to Access

8. Archival Storage, continued

9. Data Management Functionality
Administers archive database functions
Maintaining schema, view definitions, referential integrity
Receives/performs database updates
New descriptive information or archive administration data
Performs queries
Produces reports
Ex.: summary of holdings, usage reports, etc.

10. Data Management, continued

11. Administration Functionality
Solicits/negotiates submission agreements
Audits SIPs to ensure they meet standards
Manages systems configurations (hardware and software)
Monitors systems operations
Inventories, reports, updates
Establishes and maintains archive standards and policies
Provides customer support
Activates requests

12. Administration, continued

13. Preservation Planning Functionality
Evaluates contents of archive; periodically recommends updates to migrate current holdings
Develops recommendations for archive standards and policies
Monitors changes in technology environment, users’ service requests, and knowledge base
Designs information package templates
Develops detailed migration plans, software prototypes and test plans to assist Administration

14. Preservation Planning, continued

15. Access Functionality Receives requests from users (consumers)
Applies controls to limit access as needed
Coordinates requests and execution of requests
Generates dissemination information packages (DIPs)
Delivers DIPs to users (consumers)

16. Access, continued

17. Common Services Operating system services Network services
File access, reliable transmission, support
Security services
Identification/authentication, data integrity, access control, data confidentiality

18. Relationships, data flow

19. OAIS & Digital Library Systems
OAIS functionality - bundled in entities such as Ingest, Data Management, and Access – overlaps the general functionality of a digital library system
Submission (acquisition)
Descriptive information (cataloging)
Authorization/authentication and access control (of users), and
Access provisions (as that possible through library/institutional web site)
Had examples, but will let Deborah Woodyard and David Giaretta discuss this in depth in their section. Don’t want to spoil their talks by giving too many examples.

20. Functionality Reminders. . .
It is a conceptual reference model and not a system design model
Functions as set forth in OAIS Reference Model may not necessarily correspond with functional modules of a system that would implement the model. (Your mileage may vary!)
Functionality of an actual digital repository (or within modules of the repository) may be much more limited than in the OAIS Reference Model