Preservation Watch

Preservation Watch

During the Planets project Paul Wheatley and I created the Planets Functional Model http://www.planets-project.eu/docs/reports/Planets_PP7-D6_EvaluationOfPPWithinOAIS.pdf  . We identified in this model the functions that were related to the (OAIS) Preservation Planning activity, inspired by the experience gathered in the various Planets work packages. Central in the Planets model is the Preservation Watch Function. In this function we combined several areas that an organization should monitor in order to get an overview of risks and constrains that might influence its collection, and, when a risk is identified, require action. In OAIS the monitoring of the Designated Community and the Technical Environment are explicitly mentioned, but in our view there is more to take into account and we also included Organization ( changes in your own organization like budget cuts or changing policies) Producer (content deliverers that will offer you innovative materials) Administration (your stored material might contain a virus) and finally Knowledge Base, used here as an umbrella term for a variety of key information which will inform preservation processes (Pronom, finalization of an ISO standard like PDF-A2). These are all developments that need to be “watched”. Based on the outcomes of this watch activity an organization might decide to tackle the risk and make a plan on how to mitigate this risk.


Although much of the preservation watch activity in organizations is currently done manually (people reading blogs, subscribing to newsletters, attending conferences and browsing the internet), several areas that an organization need to monitor might benefit from an automated watch functionality.


The SCAPE project will develop an Automated Watch model to cope with this, as part of the Planning and Watch Subproject. It will be interesting to see whether the Planets Functional model will be viable, or whether crucial areas are missing. And I’m very curious how your organization is doing the “preservation watch activity”. Will in the end an Automated Watch function do (part of) your job?


 

25
reads

Leave a Reply

Join the conversation
https://openpreservation.org/blogs/preservation-watch/
openpreservation.org
CC-MAIN-2024-18
168656
application/http; msgtype=response
sha1:KFGHU6Z5TTGBSUT2PYVZX66UQKVRX45C
<urn:uuid:8e3fd805-2e50-4d80-9041-e23479f5949d>
2024-04-17T10:04:57Z
172.67.171.109
text/html
sha1:RYVU6NFLY3BL76PY247544ZBUH6UA2VE
<urn:uuid:ece11e13-30b9-4c90-93cc-723e584594b8>
https://openpreservation.org/blogs/preservation-watch/
response
<urn:uuid:f7e4f75b-c3fa-41cc-933d-f6dbd836e698>
isPartOf: CC-MAIN-2024-18
publisher: Common Crawl
description: Wide crawl of the web for April 2024
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-118
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.5-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/