300 likes | 397 Views
Issued document 1.0. OAIS. Rathachai Chawuthai rathachai.chawuthai@live.com. Information Management CSIM / AIT. Agenda. Overview Data Model Function Model. Overview. Overview. O pen A rchival I nformation S ystem
E N D
Issued document 1.0 OAIS RathachaiChawuthai rathachai.chawuthai@live.com Information Management CSIM / AIT
Agenda • Overview • Data Model • Function Model
Overview • Open Archival Information System • In 2000 the Research Libraries Group (RLG) and Online Computer Library Center (OCLC) discussed how both organizations build an infrastructure for purposes of archiving digital objects. • It guides you to build archival information system OCLC.org
Overview • Purpose • Model a system for archival information, which is represented in digital format, for long-term preservation • Scope • Framework for long-term preservation and access • Terminology • Architectures and Operation • Preservation strategies and techniques • Data model
Overview • Primary functions • To preserve digital resource over an extended period of time • To provide user access to the information in archives
High Level Concept • Roles • Producer - a data provider • Management - an administrator • Consumer - a data retriever • Important functions • Ingest- submit data to system • Store - preserve data in system • Access - retrieve data from system
High Level Concept Person(s), or client systems who interact with the OAIS system and services Roles OAIS (archive) Person(s), or client systems, who provide the information to be preserved Person(s) who set the overall policy of the OAIS. Management is separate from administrative functions OCLC.org
High Level Concept Important functions And workflow Store Ingest Access OCLC.org
High Level Concept Roles and responsibilities • Producer • Ingest digital resource to system • Management • Monitor, verify digital resource, do preservation planning, migrate digital resource, and etc. • Consumer • Search and access digital resource in repository
Data Model
Information Package 3 important functions, 3 package types, and 3 roles Ingest Query SIP DIP Disseminate Consumer Producer Access AIP Store Administrator
Information Package Types • SIP • A form of package that the is suitable to ingest to the system by the producer. • Majorly, SIP contains Content Info and PDI. • Multiple SIPs may associate with the same PDI. OCLC.org DIP AIP SIP • AIP • A form of package that is suitable stored in the system. • One or more SIPs is transformed to AIP that has complete set of PDI associated Content Info. • AIP may be a collection of AIPs. • DIP • A form of package that is suitable to disseminateto consumer. • AIP is transformed to DIP for sharing purpose. • DIP may contains one or more AIP that may not has complete set of PDI.
Package model • 4 Simple information concepts PDI Preservation Description Information Content Information Archive Packaging Information Package 1 Descriptive Information about Package 1
Content Information • Data Object • It is an object that need to preserve. • It can be either physical thing in the real world or digital object content containing bit string. • In this case, it can be file content (1010101010101110101 000101010101001010…..) of image file of Thailand Map • In fact, it is just a string of bit that has no meaning if no one cannot understand.
Information Model • Representation Information • A bit string(100111010…) may be useless if no one knows its meaning. The representation Information inform what structure of “100111010…”is and how to interpret it. • It may has representation of representation if the data object content has complex structure or encode by many level Format in byte form Raw bit string Construct JPEG format structure Interpret to color of pixels to be a picture
Function Model
Functional Models Big picture of all functions and flow of packages OCLC.org
Functional Models Big picture of all functions and flow of packages OCLC.org, CORNELL.edu
Ingest Overview • Accept SIPs from Producers • Verify SIPs that user submits • Generate AIPs for archive storage
Archival Storage Overview • The main task is to store data. • It also maintains data and guarantee that preservation data still be accessible form constrain of media and security • Furthermore, it provides disaster recovery capabilities
Data Management Overview • Mainly, the API works for many functions related to database • Manage DB configuration • Maintain database schema • Define integrity constrains • Perform DB update • Perform query management
Administration Overview • Solicit and negotiate submission agreement • With producer • Audit submission • To ensure that they meet standard • Maintain Configuration Management of • System hardware • Software • Day-to-day governance of the other OAIS functional entities
Administration Description (cont) • Establish Standards and Policies • Manage standards and policies in order to approve migration and replication processes • Audit Submission • Verify that AIP and SIP is following specification and agreement • Ensure that PID is understandable for the digital resource • Activate Requests • To check the request of consumer is correct, then submit the request to Access • Customer Service • Provide functions to manage user’s account
Preservation Planning Overview • Monitor environment of OAIS • Provide recommendations • Still accessible? • Long-term? • If original computing environment becomes obsolete?
Access Overview • Determine • Existence • Description • Location • Availability Of information in OAIS • Allow Consumer • Request • Retrieve Information of Products
Summary OCLC.org
Summary • Producer • Ingest package to system • System store AIP in Archival storage • System store descriptive metadata in Data management • Consumer • Query data via Access • Query from descriptive metadata from Data management • Retrieve data via Access • Get data from Archival storage • Management • Manage and monitor every flow in system