Over the last few weeks as part of the HERALD project the ADS has been making some progress on the part of the new OASIS which records the archive.

As an archival body themselves, they were keen that that the new system improves on:

  • Recording what has been found/produced for archive
  • Allowing an archival body to produce in-form guidance on what it expects from a deposition
  • Making the archival body aware of events happening within their area/remit
  • Allowing the archival body and data producer to correspond at an early stage
  • Recording the deposition stage
  • Reflecting the differences in archive workflows in England + Scotland.
  • Signposting between physical and digital archives

One of the problems with the old OASIS was that records were often completed whilst the archive was still in flux. Looking over many records you can see cases where archive location is “TBC” or “Intending to send to…”. There’s also a  inconsistency in naming the organisation, and a great deal of uncertainty in what people are recording is in the archive. It’s not all doom and gloom, there are some really good examples (everything neatly recorded, archive named, museum accession code in place) that show that the willingness to record the archive properly is in place among many archive users.

The first thing is to have an OASIS form permanently open. So if the allocation and deposition of archive is on a separate timeline to the rest of the record (as often seems to be the case), then it’s a simple matter to have a user return and complete when things are sorted. That’s especially true in Scotland where (at the time of writing) the allocation of archives is decided via the Scottish Finds Allocation Panel as Treasure Trove – although people may have an idea of where things may be deposited based on past examples, the archive part of OASIS needs to stay live so that it can be updated where needed….

Read the full article here>  https://archaeologydataservice.ac.uk/blog/2019/01/oasis-and-archives/
Source: ADS

Comments

comments
http://www.bajrfed.co.uk/bajrpress/oasis-and-archives/
www.bajrfed.co.uk
crawl=CC-MAIN-2019-09
199870
application/http; msgtype=response
sha1:CJDGUH2WAKGM4IIUXMNLXFYETBWUJU26
<urn:uuid:00e9dd75-7a20-41aa-89bc-b3bbe11fa039>
2019-02-18T00:40:20Z
88.208.252.212
text/html
sha1:TJPUZESOBSQNJDFZRLRQSHNXJKTDHHEA
<urn:uuid:95973984-5508-48d7-8b8f-5c9139cecd7b>
http://www.bajrfed.co.uk/bajrpress/oasis-and-archives/
response
<urn:uuid:2e79673e-deda-43f1-a33e-be24ca1c5570>
isPartOf: CC-MAIN-2019-09
publisher: Common Crawl
description: Wide crawl of the web for February 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-148-30-93.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 0.11-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/