790 likes | 993 Views
Issued document 1.0. OAIS. Rathachai Chawuthai rathachai.chawuthai@live.com . Information Management CSIM / AIT. Agenda. Preface Overview Data Model Function Model Architecture Model OAIS in use. Preface. Starter. I want to build own restaurant . What should I do?. Starter.
E N D
Issued document 1.0 OAIS RathachaiChawuthai rathachai.chawuthai@live.com Information Management CSIM / AIT
Agenda • Preface • Overview • Data Model • Function Model • Architecture Model • OAIS in use
Starter I want to build own restaurant. What should I do?
Starter What you should know
Starter What you should plan
Starter How you should run
Starter I don’t tell you a blueprint or concrete model for running a restaurant. But I guideyou WHAT and HOW that you have to considerwhen plan to run a restaurant business.
Introduction I want to build an archival information system. What should I do?
Introduction Understand OAIS reference 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 resposibilites • 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
Overview • Preserved data in the system needs to be formed in a package. • Owing to the 3 important functions of OAIS (Ingest, Store, and Access), package of preserved data are transformed into 3 types – SIP, AIP, and DIP • SIP - to enter to the system • AIP - to preserved in the system • DIP - to distribute from the system • Each package type is based on the same concept that is described hereafter
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.
Big picture Big picture OCLC.org Of Information Model Of a package
Package model • 4 Simple information concepts PDI Preservation Description Information Content Information Archive Packaging Information Package 1 Descriptive Information about Package 1
Package model • 4 Simple information concepts • Content Information • A digital resource that need to preservee.g. text, image, video, sound, … • Preservation Description Info (PDI) • Contain preservation metadata that informs humans or machines to know what they should concern when they want to access, render or other actions to the digital resource. • Archive Packaging Information • A package that enwraps both Content Information (1) and PDI (2) to store as one object • Descriptive Information (Information of Archive Package) • Itperforms as a metadata of Archive Packaging Information (3). • It helps search engine that does not need to costly extract Archive Package Info to query Content Info or PDI directly
1) Content Information Content Information PDI Preservation Description Information Content Information • Content Information: • Original targeted for preservation. • Physical/Digitalobject and it RepresentationInformation. Archive Packaging Information Package 1 Descriptive Information about Package 1 OCLC.org
1) Content Information • Content Information • A basic concept of information that contain data and its representation information. • For example, it can be “Thailand Map” Content Information OCLC.org
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.
1) 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
2) PDI PDI Preservation Description Information Content Information • Preservation Description Information (PDI): • What is needed to preserve the Content Information • Provenance • For reliability • Source of content • histories • Context • Environment to render • Reference • Refer to thing outside e.g. ISBN • Fixity • Check sum, MD5, … Archive Packaging Information Package 1 Descriptive Information about Package 1 OCLC.org
2) PDI • PDI contains • Reference Info • Identifier that link to thing outside system or real world resource; such as ISBN • Provenance Info • To record why the digital resource born, where it born, why, and how. • Including software and environment that created it. • Context Info • To inform how reliable of the digital resource • To inform original or source of content • To inform history of change • To inform migration process OCLC.org • Fixity Info • To provide necessary information to access and verify digital resource • E.g. keyword, Checksum, MD5, and etc
2) PDI Example of PDI components OCLC.org
2) PDI Example of PDI components OCLC.org
2) PDI Example of PDI components OCLC.org
3) Archive Package Information PDI Preservation Description Information Content Information • Archive Package Information: • CollectContent Informationand PDI together to store in the system • The package has a name for example “Package 1” Archive Packaging Information Package 1 Descriptive Information about Package 1 OCLC.org
4) Descriptive Information PDI Preservation Description Information Content Information • Descriptive Information: • Because searching in the package directly take time, it needs metadata of package in order to search. • Information which is used to discover which package has the Content Information of interest. • Full set of attributes that are searchable in catalog service. • To perform indexing to this information may improve performance of searching. Archive Packaging Information Package 1 Descriptive Information about Package 1 OCLC.org
Package Model as Information Model Descriptive Information about Package 1 Package 1 OCLC.org
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
Ingest OCLC.org
Ingest Description • Receive Submission • Upload SIP package from producer by electronic transfer such as FTP • Quality Assurance • Validate transmission (e.g. checksum) error SIP package and log a result • Generate AIP • Transform SIP to AIP and report result • Generate Descriptive Info • Produce metadata support searching, retrieving AIPs (to answer who, what, when, where, why) , and browsing such a thumbnail • Coordinate Update • Provide a single point to access (add, modify, remove, get) storage area
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
Archival Storage OCLC.org
Archival Storage Description • Receive Data • Receive AIP from Ingest to permanent storage • Manage Storage Hierarchy • Provide administration functions for storage media • Replace Media • Support functions of migration from a media to another media • Error Checking • Check and notification error from data in storage area • Disaster Recovery • Provide mechanism for replicating digital content to safe place • Provide data • Copy data from storage area to Access in order to serve consumer query
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
Data Management OCLC.org
Data Management Description • Administer Database • Mainly, focus on database administration functions e.g. define schema, configure database, define integrity constrains, and etc. • Perform Queries • Point that request query from consumer, then query to database, and finally generate result set • Generate Report • Receive reports from Ingest and Access to summary • Receive Database Updates • Point that perform database operations such a insert, update, and delete
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