What do you mean I need digital preservation? I've got DAM!
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

What do you mean I need digital preservation? I've got DAM!

on

  • 906 views

Introduction to the panel of the same name at Createasphere Digital Asset Management 2012 Conference (2012-09-28). Intended to provide DAM practitioners an introduction to the standards and concerns ...

Introduction to the panel of the same name at Createasphere Digital Asset Management 2012 Conference (2012-09-28). Intended to provide DAM practitioners an introduction to the standards and concerns of the digital preservation community. A very quick, high-level talk.

Statistics

Views

Total Views
906
Views on SlideShare
873
Embed Views
33

Actions

Likes
0
Downloads
7
Comments
0

6 Embeds 33

http://www.scoop.it 15
https://twitter.com 7
http://www.linkedin.com 4
https://www.linkedin.com 4
http://twitter.com 2
https://si0.twimg.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution-ShareAlike LicenseCC Attribution-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n

What do you mean I need digital preservation? I've got DAM! Presentation Transcript

  • 1. What do you mean I need Digital Preservation? I’ve Got DAM! Kara Van MalssenAUDIOVISUAL PRESERVATION SOLUTIONS Slide inspiration: http://www.slideshare.net/slidesthatrock/slides-that-rock-9659045
  • 2. What are the businesscases for DAM?
  • 3. ORganization
  • 4. Re-use
  • 5. Distribution
  • 6. Monetization
  • 7. Preservation
  • 8. Preservation ?
  • 9. Preservation begins at the point of creation
  • 10. THE OAIS REFERENCE MODEL ISO 14721:2003 PRESERVATION PLANNING DESCRIPTIVE DESCRIPTIVE INFO INFOP DATA CR MANAGEMENT queries OO ND result sets SU SIP INGEST ACCESS orders UC ARCHIVAL ME E STORAGE DIPR R AIP AIP ADMINISTRATION MANAGEMENT
  • 11. THE OAIS REFERENCE MODEL ISO 14721:2012 PRESERVATION PLANNING DESCRIPTIVE DESCRIPTIVE INFO INFOP DATA CR MANAGEMENT queries OO ND result sets SU SIP INGEST ACCESS orders UC ARCHIVAL ME E STORAGE DIPR R AIP AIP ADMINISTRATION MANAGEMENT
  • 12. Audit & Certification of TrustworthyRepositories ISO 16363http://public.ccsds.org/publications/archive/652x0m1.pdf
  • 13. Audit & Certification of TrustworthyRepositories ISO 16363http://public.ccsds.org/publications/archive/652x0m1.pdf Compliance Areas 1. INFRASTRUCTURE AND SECURITY 2. DIGITAL OBJECT MANAGEMENT 3. ORGANIZATIONAL INFRASTRUCTURE
  • 14. 1. INFRASTRUCTURE AND SECURITY
  • 15. 1. INFRASTRUCTURE AND SECURITY
  • 16. 5.1.1.1 The repository shall employ technology watches or other technology monitoring notification systems. 1. INFRASTRUCTURE AND SECURITY5.1.1.1.1 The repository shall have hardware technologies appropriate to the services it provides to its designatedcommunities.5.1.1.1.2 The repository shall have procedures in place to monitor and receive notifications when hardwaretechnology changes are needed.5.1.1.1.3 The repository shall have procedures in place to evaluate when changes are needed to current hardware.5.1.1.1.4 The repository shall have procedures, commitment and funding to replace hardware when evaluationindicates the need to do so.5.1.1.1.5 The repository shall have software technologies appropriate to the services it provides to its designatedcommunities.5.1.1.1.6 The repository shall have procedures in place to monitor and receive notifications when software changesare needed.5.1.1.1.7 The repository shall have procedures in place to evaluate when changes are needed to current software5.1.1.1.8 The repository shall have procedures, commitment, and funding to replace software when evaluationindicates the need to do so.5.1.1.2 The repository shall have adequate hardware and software support for backup functionality sufficient forpreserving the repository content and tracking repository functions.5.1.1.3 The repository shall have effective mechanisms to detect bit corruption or loss.5.1.1.3.1 The repository shall record and report to its administration all incidents of data corruption or loss, andsteps shall be taken to repair/replace corrupt or lost data.5.1.1.4 The repository shall have a process to record and react to the availability of new security updates based ona risk-benefit assessment.5.1.1.5 The repository shall have defined processes for storage media and/or hardware change (e.g., refreshing,migration).5.1.2 The repository shall manage the number and location of copies of all digital objects.5.1.2.1 The repository shall have mechanisms in place to ensure any/multiple copies of digital objects aresynchronized.5.2.1 The repository shall maintain a systematic analysis of security risk factors associated with data, systems,personnel, and physical plant.5.2.4 The repository shall have suitable written disaster preparedness and recovery plan(s), including at least oneoff-site backup of all preserved information together with an offsite copy of the recovery plan(s).
  • 17. 5.1.1.1 The repository shall employ technology watches or other technology monitoring notification systems. 1. INFRASTRUCTURE AND SECURITY5.1.1.1.1 The repository shall have hardware technologies appropriate to the services it provides to its designatedcommunities.5.1.1.1.2 The repository shall have procedures in place to monitor and receive notifications when hardwaretechnology changes are needed.5.1.1.1.3 The repository shall have procedures in place to evaluate when changes are needed to current hardware.5.1.1.1.4 The repository shall have procedures, commitment and funding to replace hardware when evaluationindicates the need to do so.5.1.1.1.5 The repository shall have software technologies appropriate to the services it provides to its designated5.1.1.3 The repository shall have effective mechanisms to detect bit corruption or loss.communities.5.1.1.1.6 The repository shall have procedures in place to monitor and receive notifications when software changesare needed.5.1.1.1.7 The repository shall have procedures in place to evaluateits administration all incidents of5.1.1.3.1 The repository shall record and report to when changes are needed to current software5.1.1.1.8 The repository shall have procedures, commitment, and funding to replace software when evaluationdata corruption or so. and steps shall be taken to repair/replace corrupt or lost data.indicates the need to do loss,5.1.1.2 The repository shall have adequate hardware and software support for backup functionality sufficient forpreserving the repository content and tracking repository functions.5.1.1.3 The repository shall have effective mechanisms to detect bit corruption or loss.5.2.4 The repository shall have suitable written disaster preparedness and recovery5.1.1.3.1 The repository shall record and report to its administration all incidents of data corruption or loss, andplan(s), including repair/replace corrupt or lost data. of all preserved information together withsteps shall be taken to at least one off-site backupan offsiterepository shall have a process to record and react to the availability of new security updates based on5.1.1.4 The copy of the recovery plan(s).a risk-benefit assessment.5.1.1.5 The repository shall have defined processes for storage media and/or hardware change (e.g., refreshing,migration).5.1.2 The repository shall manage the number and location of copies of all digital objects.5.1.2.1 The repository shall have mechanisms in place to ensure any/multiple copies of digital objects aresynchronized.5.2.1 The repository shall maintain a systematic analysis of security risk factors associated with data, systems,personnel, and physical plant.5.2.4 The repository shall have suitable written disaster preparedness and recovery plan(s), including at least oneoff-site backup of all preserved information together with an offsite copy of the recovery plan(s).
  • 18. 2. DIGITAL OBJECT MANAGEMENT
  • 19. 4.1.2 The repository shall clearly specify the information that needs to be associated with specific Content 2. DIGITAL OBJECT MANAGEMENTInformation at the time of its deposit.4.1.4 The repository shall have mechanisms to appropriately verify the identity of the Producer of all materials.4.1.5 The repository shall have an ingest process which verifies each SIP for completeness and correctness.4.1.7 The repository shall provide the producer/depositor with appropriate responses at agreed points during theingest processes.4.1.8 The repository shall have contemporaneous records of actions and administration processes that are relevantto content acquisition.4.1.1 The repository shall identify the Content Information and the Information Properties that the repository willpreserve.4.2.1 The repository shall have for each AIP or class of AIPs preserved by the repository an associated definitionthat is adequate for parsing the AIP and fit for longterm preservation needs.4.2.1.2 The repository shall have a definition of each AIP that is adequate for longterm preservation, enabling theidentification and parsing of all the required components within that AIP.4.2.3.1 The repository shall follow documented procedures if a SIP is not incorporated into an AIP or discardedand shall indicate why the SIP was not incorporated or discarded.4.2.4 The repository shall have and use a convention that generates persistent, unique identifiers for all AIPs.4.2.4.1.5 The system of identifiers shall be adequate to fit the repository’s current and foreseeable futurerequirements such as numbers of objects.4.2.4.2 The repository shall have a system of reliable linking/resolution services in order to find the uniquelyidentified object, regardless of its physical location.4.2.5.2 The repository shall have tools or methods to determine what Representation Information is necessary tomake each Data Object understandable to the Designated Community4.2.5.3 The repository shall have access to the requisite Representation Information.4.2.6 The repository shall have documented processes for acquiring Preservation Description Information (PDI) forits associated Content Information and acquire PDI in accordance with the documented processes.4.2.9 The repository shall provide an independent mechanism for verifying the integrity of the repository collection/content.4.3.1 The repository shall have documented preservation strategies relevant to its holdings.4.3.2 The repository shall have mechanisms in place for monitoring its preservation environment.4.3.3.1 The repository shall have mechanisms for creating, identifying or gathering any extra RepresentationInformation required.
  • 20. 4.1.2 The repository shall clearly specify the information that needs to be associated with specific Content 2. DIGITAL OBJECT MANAGEMENTInformation at the time of its deposit.4.1.4 The repository shall have mechanisms to appropriately verify the identity of the Producer of all materials.4.1.5 The repository shall have an ingest process which verifies each SIP for completeness and correctness.4.1.7 The repository shall provide the producer/depositor with appropriate responses at agreed points during theingest processes.4.1.8 The repository shall have contemporaneous records of actions and administration processes that are relevantto content acquisition.4.1.1The repository shall identify the Content Information and the Informationand the Information4.1.1 The repository shall identify the Content Information Properties that the repository willProperties that the repository will preserve.preserve.4.2.1 The repository shall have for each AIP or class of AIPs preserved by the repository an associated definitionthat is adequate for parsing the AIP and fit for longterm preservation needs.4.2.1.2 The repository shall have a definition of each AIP that is adequate for longterm preservation, enabling theidentification and parsing of all the required components within that AIP.4.2.3.1 The repository shall follow documented procedures if a SIP tonot incorporated into an AIP or discarded4.2.5.2 The repository shall have tools or methods is determine what Representationand shall indicate why the SIP was not incorporated Data Object understandable to the DesignatedInformation is necessary to make each or discarded.4.2.4 The repository shall have and use a convention that generates persistent, unique identifiers for all AIPs.Community4.2.4.1.5 The system of identifiers shall be adequate to fit the repository’s current and foreseeable futurerequirements such as numbers of objects.4.2.6 The repository shallshall a system of reliable linking/resolution services in order to find the uniquely4.2.4.2 The repository have have documented processes for acquiring Preservationidentified object, regardless of its physical location.Description Information (PDI) or methods to determineContent Information and acquire to4.2.5.2 The repository shall have tools for its associated what Representation Information is necessaryPDI in accordanceunderstandable to the Designated Communitymake each Data Object with the documented processes.4.2.5.3 The repository shall have access to the requisite Representation Information.4.2.6 The repository shall have documented processes for acquiring Preservation Description Information (PDI) forits associated Content Information and acquire PDI in accordance with the documented processes.4.2.9 The repository shall provide an independent mechanism for verifying the integrity of the repository collection/content.4.3.1 The repository shall have documented preservation to its holdings.4.3.1The repository shall have documented preservation strategies relevant strategies relevant to its4.3.2 The repository shall have mechanisms in place for monitoring its preservation environment.holdings.4.3.3.1 The repository shall have mechanisms for creating, identifying or gathering any extra RepresentationInformation required.
  • 21. 3. ORGANIZATIONAL INFRASTRUCTURE
  • 22. 3.1.1 The repository shall have a mission statement that reflects a commitment to the preservation of, long termretention of, management of, and access to digital information. 3. ORGANIZATIONAL INFRASTRUCTURE3.1.2 The repository shall have a Preservation Strategic Plan that defines the approach the repository will take in thelong-term support of its mission.3.1.2.1 The repository shall have an appropriate succession plan, contingency plans, and/or escrow arrangements inplace in case the repository ceases to operate or the governing or funding institution substantially changes its scope.3.1.2.2 The repository shall monitor its organizational environment to determine when to execute its succession plan,contingency plans, and/or escrow arrangements.3.1.3 The repository shall have a Collection Policy or other document that specifies the type of information it willpreserve, retain, manage, and provide access to.3.2.1 The repository shall have identified and established the duties that it needs to perform and shall have appointedstaff with adequate skills and experience to fulfill these duties.3.2.1.2 The repository shall have the appropriate number of staff to support all functions and services3.3.1 The repository shall have defined its Designated Community and associated knowledge base(s) and shall havethese definitions appropriately accessible.3.3.2 The repository shall have Preservation Policies in place to ensure its Preservation Strategic Plan will be met.3.3.2.1 The repository shall have mechanisms for review, update, and ongoing development of its PreservationPolicies as the repository grows and as technology and community practice evolve.3.3.3 The repository shall have a documented history of the changes to its operations, procedures, software, andhardware.3.3.4 The repository shall commit to transparency and accountability in all actions supporting the operation andmanagement of the repository that affect the preservation of digital content over time3.3.5 The repository shall define, collect, track, and appropriately provide its information integrity measurements.3.3.6 The repository shall commit to a regular schedule of self-assessment and external certification.3.4.1 The repository shall have short- and long-term business planning processes in place to sustain the repositoryover time.3.4.2 The repository shall have financial practices and procedures which are transparent, compliant with relevantaccounting standards and practices, and audited by third parties in accordance with territorial legal requirements.3.5.1.3 The repository shall have written policies that indicate when it accepts preservation responsibility for contentsof each set of submitted data objects3.5.1.4 The repository shall have policies in place to address liability and challenges to ownership/rights.
  • 23. 3.1.1 The repository shall have a mission statement that reflects a commitment to the preservation of, long termretention of, management of, and access to digital information. 3. ORGANIZATIONAL INFRASTRUCTURE3.1.2 The repository shall have a Preservation Strategic Plan that defines the approach the repository will take in thelong-term support of its mission.3.1.2.1 The repository shall have an appropriate succession plan, contingency plans, and/or escrow arrangements inplace in case the repository ceases to operate or the governing or funding institution substantially changes its scope.3.1.2.2The repository shallshall have a missionenvironment to that reflects a commitment to the3.1.1 The repository monitor its organizational statement determine when to execute its succession plan,contingency plans, and/or escrow arrangements. management of, and access to digitalpreservation of, long term retention of,3.1.3 The repository shall have a Collection Policy or other document that specifies the type of information it willinformation. manage, and provide access to.preserve, retain,3.2.1 The repository shall have identified and established the duties that it needs to perform and shall have appointedstaff with adequate skills and experience to fulfill these duties.3.2.1.2 The repository shall have the appropriate number of staff to support all functions and services3.3.1 TheThe repository shall have an appropriate succession plan, contingency plans,3.1.2.1 repository shall have defined its Designated Community and associated knowledge base(s) and shall havethese definitions appropriately accessible.and/or escrow arrangements in place in case the repository ceases to operate or the3.3.2 The repository shall have Preservation Policies in place to ensure its Preservation Strategic Plan will be met.governing or fundinghave mechanisms for review, update, and ongoing development of its Preservation3.3.2.1 The repository shall institution substantially changes its scope.Policies as the repository grows and as technology and community practice evolve.3.3.3 The repository shall have a documented history of the changes to its operations, procedures, software, andhardware.3.3.2The repository shall commit to transparency and accountability in allplace to ensurethe operation and3.3.4 The repository shall have Preservation Policies in actions supporting its PreservationmanagementPlan will be met. affect the preservation of digital content over timeStrategic of the repository that3.3.5 The repository shall define, collect, track, and appropriately provide its information integrity measurements.3.3.6 The repository shall commit to a regular schedule of self-assessment and external certification.3.4.1 The repository shall have short- and long-term business planning processes in place to sustain the repositoryover time.3.4.2 The repository shall have financial practicesa regular schedule oftransparent, compliant with relevant 3.3.6 The repository shall commit to and procedures which are self-assessment and external certificationaccounting standards and practices, and audited by third parties in accordance with territorial legal requirements.3.5.1.3 The repository shall have written policies that indicate when it accepts preservation responsibility for contentsof each set of submitted data objects3.5.1.4 The repository shall have policies in place to address liability and challenges to ownership/rights.
  • 24. PEople Technologies Policies
  • 25. PEople Technologies PoliciesDigital Preservation!
  • 26. DAM!PEople Technologies PoliciesDigital Preservation!
  • 27. DAM!PEople PoliciesDigital Preservation!
  • 28. DAM! PoliciesDigital Preservation!
  • 29. DAM!People Technologies PoliciesDigital Preservation!