This page (revision-25) was last changed on 28-May-2014 14:53 by Test

This page was created on 13-Nov-2013 09:05 by Test

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
25 28-May-2014 14:53 978 bytes Test to previous
24 15-May-2014 16:34 733 bytes Test to previous | to last
23 15-May-2014 16:33 794 bytes Test to previous | to last
22 15-May-2014 16:18 11 KB Test to previous | to last
21 15-May-2014 16:15 19 KB Test to previous | to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 6 added one line
\\
At line 7 changed 2 lines
!!1. Planning
During this stage, project documentation will be produced which will set out the aims and objectives of the project, and the personnel, strategies, timetable, tasks and resources necessary for the work to take place. This is the stage at which the archiving requirements of the project should be determined, as follows.
[{Image src='Guidance1.JPG' width='227,2' height='170,4' align='right' }]
At line 10 changed one line
!1.1. The structure and character of the future archive
[{Image src='Guidance2.JPG' width='228' height='171' align='right' }]
At line 12 changed one line
The structure and character of the future archive should be agreed on and understood by all concerned, including the expected final content of the archive and how it will be managed, see [Standards - 3. Principles]
[1. Planning]
At line 14 changed 3 lines
*Standards should be set for project records (e.g. context records, object records, site plans) including their creation in both digital and analogue formats; what media will be used and procedures followed to ensure a consistent record, including digital file formats, file naming and classification schemes, metadata protocols and storage media. Where they exist, standards or conventions set in international, national, regional, local or specialist guidelines should be followed.
*The anticipated material (finds) assemblage and the archiving procedures to be followed during identification, recording, and management should be defined. This should detail the manuals to be used and any packaging, temporary storage, curation or movement requirements.
*Wherever they exist, international, national, regional, local and/or repository standards for archaeological archives and collections management should be followed.
[2. Data Gathering]
At line 18 changed one line
!1.2. Selection for archive
[3. Analysis, Reporting and Archive Transfer]
At line 20 changed one line
A selection strategy should be agreed at the project planning stage. This should set out the criteria for selecting records, documents, data files and materials (finds) for inclusion in the project archive. It should also set out how things that have not been selected for archive will be dispersed or discarded. This strategy should be devised in accordance with the project research aims or management questions (the Standard 4.5). Account should be taken of any national, regional or local research frameworks and also of the collecting policies of the recipient repository.
[4. Care and Curation of the Archive]
At line 22 changed 64 lines
*All components of the documentary record and the material assemblage should be subject to selection for retention in the archive at any time during the project lifecycle. Documents should be subject to version control and a clear digital management policy should be in place which enables the deletion of duplicate or superfluous digital files.
*A selection strategy should be drawn up with input from all the relevant members of the project team, including specialists and the curator of the repository or repositories into which the final archive will be received.
!1.3. The security of the archive and disaster management planning
It is vital that security or disaster management plans are devised and implemented that safeguard the archive, and also potential archive components, from damage and loss (the Standard 5.1, 5.3). Such plans, which could be a part of the disaster management plan for the project itself, should be included in the planning documentation.
*Ensure the disaster management strategy includes the means of safeguarding the information that is contained in the archive, including the implementation of security copying or back up systems for both analogue and digital data. It should detail the standards which will be adhered to in order that the documentary and material archive will be created, collected and stored to ensure against damage, cross contamination, loss or theft.
*Ensure the disaster management strategy covers the security of the archive whilst on site/in the field, during transportation or movement of material objects (finds) and information, during analysis in the office or laboratory and in store during temporary care. Disaster plans should also be in place at archive repositories.
!1.4. Tasks and resources
At the planning stage the tasks and resources required for the project will be identified and allocated and it is important that the needs of the archiving process are included in these plans (the Standard 4.4).
*During the creation of the project plan, archiving activities and tasks should be programmed and timetabled. Important archiving milestones, for example obtaining landowner agreements, copyright and transfer of title agreements, or fulfilling deposition conditions, should be programmed in, and any scheduling issues which may affect these milestones should be noted.
*Qualified and experienced specialists, including conservators, should be consulted to ensure sufficient resource is identified and allocated to make the project archive ordered, internally consistent, accessible, stable, secure and properly cared for from the beginning of the project until the archive is safely deposited in an approved repository.
!1.5. Identification and involvement of the repository
Unless national, regional or local laws or regulations dictate where the archive must go, the recipient repository, or repositories, should be identified and involved at the project outset so that the future of the final archive can be guaranteed, and the archive compiled in accordance with the repository’s specifications. It is important to ensure that any national, regional or local legal regulations which apply to the project archive are followed and are described in the project planning documentation.
*Ensure that both the analogue documentary archive and the material (finds) archive are transferred to a repository, or repositories, approved in accordance with national, regional or local accreditation schemes (the Standard 4.3.6) and that the digital archive is deposited with a Trusted Digital Repository (the Standard 4.5.18). Any repository must provide nationally, regionally or locally recognised standards of curatorial care and good access to the archive for all future users.
*Ensure that the repository curators participate in the project planning process from the outset.
!1.6. Transfer of title and copyright
The rights of title to the archive and issues over copyright are complex and it is not possible in the Guide to go into any specific detail, as this would involve discussing varying national laws and procedures for several European countries. However, general principles do hold.
*Copyright and transfer of title, where appropriate, should be clarified and agreed during the project planning stage. If there are any copyright or transfer of title issues affecting the project archive, then it is important to ensure that these are resolved in accordance with national, regional or local legislation.
!!2.DATA GATHERING
During this stage of the project, planning is put into effect and archaeological data and materials are collected, either in the field or elsewhere.
!2.1. Ensuring access to the archaeological archive
Project staff and researchers will need to access the archive contents both during and after the lifetime of the project. It is therefore important to document, organise and index the documentary and material (finds) archive in order to keep it comprehendible and accessible (the Standard 4.3). The following practices should be employed throughout the lifecycle of the project, with the resulting documentation also becoming part of the archive.
*It should be easy to find a way through all parts of the archive. The archive should be fully indexed, beginning with an overall catalogue of contents, which leads on to deeper levels of individual indices for other elements such as context records, finds lists and drawings.
*A project summary should be created that will introduce researchers to the aims and objectives, scope, location, content and results of the project. It should include links to any previous work undertaken on the project/site. The summary should be kept updated and complete until the project is finalised and the archive transferred to a repository
*Project documentation should make clear how and why the archaeological records and materials (finds) were created, collected, selected and analysed. This could include information such as recording methodologies or sampling strategies. This is an essential tool for both the data creator and the researcher. It facilitates data management (for best practice advice on digital data management in archaeology see [http://Guides.archaeologydataservice.ac.uk/]) during the lifecycle of a project and also acts as an aid to understanding and interrogating the archive once the project is complete. (Examples of project documentation include: project designs, written schemes of investigation etc and their revisions, recording systems and techniques, selection and sampling strategies, manuals used, classification systems in use such as numbering systems or identifiers and translations of codes or abbreviations)
*The application of metadata is essential for accessing the digital archive. Metadata provides summary information about a digital file or dataset to enable the user easily to access and use the information, or decide whether it will be useful or not.
*In the case of digital data, it is important to follow international metadata standards to ensure that information can be clearly understood and easily re-used by both people and computers. Choosing the metadata standard best suited for the information can sometimes be difficult. A project should work closely with a Trusted Digital Repository when determining how the digital archive must be described and which metadata standards to choose. (Dublin Core Metadata Initiative: [http://dublincore.org/], see especially [http://dublincore.org/documents/dces/] for the basic element set. CIDOC Conceptual Reference Model: [www.cidoc-crm.org], the Inspire Directive: [http://inspire.jrc.ec.europa.eu]).
*Metadata can be applied on three levels:
**__Project__: this should describe the general context, geographical situation and time span of the project and the files that belong to the project.
**__Content__: this level includes all glossaries, vocabularies and variables that have been used when recording data with a concordance of what the terms mean.
**__File__: this should describe the specific content of the file.
!2.2. Validity and comprehensibility of information
It is essential to ensure that all the elements of an archive form a seamless whole facilitating movement between each part of the archive. For example, it must be possible to make connections between context records, finds records and photographs and one should also be able to trace individual finds back to the context, layer, trench and location. It should also be possible to research parallels in the wider archaeological record (the Standard 4.3). This is a duty not only for the project manager but for the project team as a whole:
*The relationships between the project and the wider archaeological record should be clear. References and links to such things as research frameworks, associated publications and reports, and similar or related projects, will make it possible to interrogate the project archive within international, national, regional and local contexts.
*The relationship between the archive and its origin should be clear, whether that origin is a site or a finds assemblage; and it should be possible to link all parts of the project archive back to their exact point of origin. For example, site plans and sections should be geo-referenced; finds should be marked or labelled with both a site identifier and an appropriate context or individual identifier.
*The relationships within the project archive should be clear. All data and images should be able to be referenced back to associated materials or documentation, and vice versa. For example the drawings should be linked to the context record, photographs to the site plans, and object records link accurately back to the correct objects.
*Wherever standardised and accepted terminology controls exist, such as glossaries or thesauri, they should be used and cited in the project metadata. If they do not exist then at the very least it should be ensured that terminologies are consistently used throughout the project record and that the relevant glossaries are included in the archive. Digital information retrieval and manipulation is reliant on searching and filtering within the data. For example if the term ‘posthole’ is used in one place and ‘post-hole’ in others, effective and efficient searching and filtering becomes impossible.
!2.3. The creation of a stable archive
Archiving is a process that aims to preserve information and material for posterity. The physical products of an archaeological project are unique and irreplaceable; therefore the project team should ensure that adequate care is taken of it from the project outset. Procedures and practices should be followed which promote the lifespan of the archive (the Standard 4.3):
\\
\\
\\
\\
[{Image src='Guidance3.jpg' width='217,88' height='220,12' align='right' }]