Archived copy.
This page was recovered from the Internet Archive snapshot of
/display/REQ/Archaeology Data Service taken on 2017-11-11.
The original wiki at wiki.opf-labs.org is being decommissioned.
Archaeology Data Service
| Storage and access |
|
| Collection storage / preservation of masters | 1 copy of masters stored on our file server (Sun OS) and backed up by University of York. Another copy stored in our deep storage facility at the UK Data Archive. Original media (CD/DVD) stored in filing cabinet where appropriate. |
| Collection access | From our website |
| Access protocol | What technical protocol is used to access files? Local file systems? Windows shares? (SMB/CIFS) http for web users. Internally by ADS staff we use a variety of methods including Webdrive and WinSCP |
| Workflow |
|
| Workflow overview | Describe your existing content workflow See ADS Preservation Policy/Ingest Manual/Repository Operations document on our website: http://archaeologydataservice.ac.uk/advice/preservation  In summary, we accession files into the archive and then migrated them (if necessary) to a suitable dissemination and preservation format (based on individual data procedure manuals available internally on our staff wiki). Future file migrations will be necessary as time goes on in order to ensure that we do not have any obsolesence. |
| Tools used in workflow | What tools are part of the existing workflow? DROID (and PRONOM) Our home-grown Collections Management System (CMS) - programmed in Java with an underlying ORACLE database Various bits of software to carry out the file migrations themselves Our website is the way we disseminate the files - This used to be built using ColdFusion with Oracle database sitting behind it. Now it is in Java and we use the open source BlueDragon to read the legacy ColdFusion scripts |
| Workflow technologies | What technologies underly the existing workflow? Java, ORACLE, BlueDragon |
| Workflow challenges | What challenges are present in the existing workflow? (technology, organisational, staffing) Not enough of what we do is automated. Too much human interaction needed particularly at the accessioing stage)! Especially for things such as checking we have all the files we are meant to have and adequate metadata in order to make sense of the collection |
| Automation | Does the workflow include manual steps? Lots of manual steps. There are some things that we do that should be automated, but others we will never solve with automation because nothing would be able to do the job. |
| Location of Solution in workflow | Where in this workflow would the Solution be deployed? Ingest process - migrating files for preservation and dissemination |
| Workflow change process | What is the process for changing or enhancing the workflow? What obstacles to change are present? Curatorial and technical staff make decisions in our team meetings (monthly) and these changes are agreed with managers in follow up executive meetings |
| Actors |
|
| Workflow execution actor | Who executes the existing workflow? Curatorial and technical staff |
| Workflow administration actor | Who adminsters the existing workflow? All curatorial and technical staff |
| Workflow executor rights | What system rights do the workflow executors have? Can they install software? Can they use the web? Yes they can install software and use web |
| Collection owner/curator | Who is the collection owner or curator? (section/department/team) Curatorial and Technical staff (including systems manager) |
| Workflow champions | Is there a workflow champion, who is it? Jenny Mitcham |
| Dataset/Issue/Solution links | ADS Grey Literature Library |