Digitisation of Tell el-Daba resources

(Edeltraud Aspöck, Gerald Hiebel, Martina Simon)

    Model of metadata creation. Figure 1: Model of metadata creation. Scanning over-sized plans. Figure 2: Scanning over-sized plans. List of analogue and digitised analogue resources with estimated numbers (project midterm). Many digital copies/scans were made before 4DP project and have no metadata records (‘scans/digital objects’). Table 1: List of analogue and digitised analogue resources with estimated numbers (project midterm). Many digital copies/scans were made before 4DP project and have no metadata records (‘scans/digital objects’). 4DP scanning standards. Table 2: 4DP scanning standards.

‘Digitisation’ of Tell el-Daba resources for digital archiving includes:

  1. Digitisation of analogue resources and metadata creation for long-term preservation.
  2. Processing of digital objects and metadata creation for long-term preservation.

The first 2,5 years of the project were dedicated to analogue resources. We have developed and tested metadata forms for each analogue resource type and processed a large number of resources (Table 1). This process included a series of corrections and adaptions of forms and data as part of feedback cycles and quality assurance.

For the creation of the metadata record for analogue resources we have developed a workflow based on several spreadsheets (MS Excel, Figure 1). There is a separate excel file for each resource type with information about the resources and the scanning process – if an analogue resource was digitised. A metadata master file contains metadata of physical objects such as excavation objects, archaeological objects, finds, bulk finds (convolutes, animal bones, stone registry), locus, stratum/phase. These metadata were collected from the resources describing physical objects. 4DPuzzle identifiers (for archaeological objects and finds without TD inventory numbers) and a list of terms to specify types of archaeological objects (for data entry) are included in the metadata master file and it defines the most important attributes and relationships of physical objects (like “part of” relations of excavation objects or “falls within” relations between archaeological objects and excavation objects). Identifiers for physical objects relate the resource files to the metadata master file.

The file names for the digitised resources are created from the unique identifier of a resource and, additionally, a short description of its content (e.g. TD_FZ_1234__TD_F-I_j21_Planum1 tells us that the unique identifier of the resource is TD_FZ_1234 (first part of file name) and that this field drawing (FZ) shows Tell el-Daba area F/I, square j21, Planum 1). It allows information about the contents of the file to be understood by a human being without opening it.

Digitisation workflow

  • Scanning of the resource: there are different requirements for different resource types. For example, field drawings of ‘Plana’ (levels) are standardized A3 drawings, which can be digitized quickly by creating a digital copy with the scanner. Field drawings of sections often consist of many different A3 drawings, which have to be stitched together, which is more time consuming.
  • Create metadata record for the resources: includes creation of the unique identifier for the resource (see description in WP3) and the scan title (a short description of its content) which automatically creates the filename (see above); entering identifiers of archaeological- and excavation objects, loci and stratum to link the record to them; enter additional metadata for the respective resource and the digitization process (like scale, ppi rate and used hardware);
  • If necessary, create the relevant identifiers in the master metadata table.
  • The analogue resource is marked with a pencil to show that it has been scanned (name of person who created the scan and date).
  • The same workflow applies to digital copies of resources. In this case, the last step is to change the filename according to our standards (see above).
  • If necessary (some irregularities were encountered during metadata creation and a decision was made), data logs have to be updated.
  • At the end of each workday, all metadata files are committed to the git-repository (Fig. 1). Additionally, we create backups of all updated files by copying them into a backup folder on our netdrives.

Scanning standards

Based on guides of good practice we have developed parameters for scanning analogue resources (ADS, Archaeological Data Service/Digital Antiquity 2017, IANUS, Forschungsdatenzentrum Archäologie und Altertumswissenschaften 2014, table 2.1).

There are differences in how the resources are getting digitised. For example, convolutes (sheets of cardboard with pencil drawings of profiles from several pieces of pottery) usually consist of several, up to eight, items, which have to be scanned and then combined to one image. For each image there is only one metadata record. In this case, the scanning is more time-consuming, while creation of metadata is quick. In other cases, it may be the other way round. For example, the recording of metadata of the field drawings is more complicated, as it contains a higher level of detail, in particular if different types of archaeological objects have been documented additionally to the drawing of the archaeological evidence of the respective level. In other cases, analogue resources have already been scanned in Egypt, and we only need to assemble the scans and enter metadata.

Oversized drawings and maps were scanned using the Wide Tek 25 A2-scanner at the ÖAW ACDH (Fig. 2) and merged using stitching software and additionally Photoshop (stitching software was too inaccurate).

Data management

All project data are currently stored on our ÖAW network drive. The digital copies of TD resources will be transferred to the ACDH repository for long-term archiving once available. The ÖAW network drives are maintained with daily backups. After each workday, the current versions of the metadata files are committed to the git repository and, additionally, copies are made in a backup folder on our project network drive. After that, files are converted to RDF and transferred to a triple store provided by the ACDH (Data integration, storage, archiving and open access) and can be queried over the web user interface.

Data logs are kept for each type of resource. They contain descriptions of the metadata fields and documentation of all the decisions we have made when encountering irregularities of documentation.

The main aims until the end of the project are to:

  1. Develop digitisation workflows for all types of digital and analogue resources and document these workflows, so they can be applied in future digitization work.
  2. Complete digitisation of endangered analogue and digital resources (photos from the earlier campaigns, ink-drawn plans on tracing paper, digital objects with outdated file formats).