View Source

| *Title* \\ | New Operating System&nbsp; \\ |
| *Detailed description* | The Council are due to upgrade their Operating System and issues arise over the access and authenticity of original files with the new operating system. The implementation of a new operating system could affect the files and we need to ensure that the files we have are ready for this change. \\ |
| *Issue champion* | _﻿﻿__[~neildickson]_ \\ |
| *Other interested parties* \\ | _Any other parties who are also interested in applying Issue Solutions to their Datasets_ |
| *Possible Solution approaches* | _To ensure we are ready for the upgrade to the new system:_
* _Extract information from our current catalogue. If the catalogue does not work with the new operating system then we will at least have our information t{_}{_}o ensure we know our files have not been&nbsp;corrupted:_
* _Implementation of a Checksum system.&nbsp;_
* _User friendly BagIt system.&nbsp;_ |
| *Context* | _The majority of the digital files we hold have been created with the intention of being digital surrogates and being used as part of our PastPerfect Cataloguing system with the relevant metadata attached.&nbsp;Additionally, we have various digital artworks in our digital collection. At Inverclyde Council, the Operating System used is Windows XP. Within the next 12 to 24 months, the Operating system used by the Council will be updated. We want to ensure that when the upgrade takes place we are aware of any corruption to our files that may occur and that &nbsp;_ |
| *Lessons Learned* | _The need to get a strict best practice&nbsp;guideline&nbsp;for how we manage our digital collection. We are not currently ready for the changes that will affect our collections in the near future. We must run a consistent preservation programme and possibly change the current cataloguing system. PastPerfect is unclear on its ability to run with new Windows Operating Systems. It may best to implement a cataloguing system which has safety in numbers, although there is no guarantee it will survive longer than the current cataloguing system.&nbsp;_{_}Additionally, the implementation of the bagIt systems reinforces our need to have greater control of our digital collection. Simplicity is often key with digital preservation and the need to create disaster plans, risk assessments and creating a strong knowledge base on the issues surrounding digital preservation._ |
| *Datasets* | [SPR:McLean Museum]\\ |
| *Solutions* | [SPR:Checking the Authenticity and Integrity of Digital Content]\\ |
https://wiki.opf-labs.org/pages/viewpagesrc.action?pageId=13762729
wiki.opf-labs.org
crawl=CC-MAIN-2021-49
7513
application/http; msgtype=response
sha1:O2CV5QSXAWY46IVVYYNEVXROIKRJEBKB
<urn:uuid:d7c57e75-dcad-4834-80fc-b14fdf8545f2>
2021-11-29T18:02:07Z
172.67.179.60
text/html
sha1:YXELJ3NLPUVNNH3RX2CMY6BXN5JHAJXH
<urn:uuid:60fbb110-ed73-49c3-8688-db3f9f85df09>
https://wiki.opf-labs.org/pages/viewpagesrc.action?pageId=13762729
response
<urn:uuid:f4648cbd-384f-4643-9ef5-f2f8f83d422f>
isPartOf: CC-MAIN-2021-49
publisher: Common Crawl
description: Wide crawl of the web for November/December 2021
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-102
software: Apache Nutch 1.18 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.3-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/