Internet Activation Proposed Developmental

9 of samples collected by external parties not trained by MAL personnel can be marked with considerable variation.

4.1.1.2 Component details

Data: Sample metadata Comments: Highly variable and disparate. Many external projects have had questionable sample labelling policies, and ineffective structures. A system must be devised which is both efficient and can cater for these problem samples. The effectiveness of the SEAD must not however, be sacrificed in order to cater for badly designed legacy data. Much of this data could be in paper form in structured files, but some is entered into MS Excel files during logging and processing. Status: Current level of digitalisation: 2? Volume of data: 5 Uniformity of data: 1? Complexity of task: 5

4.1.2 Laboratory data

4.1.2.1 Summary

The majority of laboratory data is subject to routines which ensure the creation of appropriate metadata and data elements. There are, however inconsistencies in the storage location and quality of this data, particularly where plant macrofossil analyses are concerned. An ‘Incoming folder’ holds a master list of the information necessary for identifying sample batches. All samples handled in the laboratory at MAL are given a unique identification number, referred to as its “MALnummer”, constructed by the concatenation of a sample batch number followed by a sample number. This minimizes the possibility of mixing up samples from different investigations. These unique identifiers follow the samples through every step of the process, from pre-processing to reporting and are used for all types of samples processed in the laboratory.

4.1.2.2 Component details

Data related to arrival of samples in lab Data: Sample batch information: type, size, date received, external contact and project information. Incoming folder Comments: System was implemented in 1999 and is used as a temporary store for project meta data. This is digitised for 1999-2003. Can be used as central node for project information if used consistently, and may be useful when creating project structure in SEAD. Status: Current level of digitalisation: 2 Volume of data: 2 Uniformity of data: pre-1999: 2?; post-1999: 4 Complexity of task: 3