Skip to main content

Collection or Study Level Metadata


Collection or study level metadata provides an overarching layer of context, provenance and inherent relationships to the individual files you may have.


This level of descriptive metadata is important as it helps researchers reach an informed understanding of the collection or research study.


Corporate and Personal Records

  • Describe the collection using metadata elements such as:
    • title
    • description - a description of the content of the collection. The greater the detail the better
    • creator(s) - i.e. the creating body or individual
    • extent - the amount of content within the collection
    • relevant dates
    • keyword(s) - that quickly describe any subject areas, classifications, locations or individuals of interest
    • copyright - who owns the collection?
    • access conditions - is some of the data reserved, restricted or protected, meaning there are conditions over access to the materials within the collection? If so, what are they?
  • Provide the provenance history of the collection - i.e. who has held responsibility for the collection over time?

Research Study

  • Provide an overview of the study:
    • title
    • description
    • author(s)
    • commissioning and funding bodies
    • the overall aims and objectives for the study
    • relevant dates
    • relevant locations
    • key findings
  • Describe the data collection methods used:
    • data collection protocols
    • sampling design
    • data sources used and the provenance of that data
    • technology used (instruments, hardware and software)
  • Describe the data validation, cleaning and refinement methods used.
  • Describe any prediction modelling developed.
  • Describe any modifications made to your data over time and the processes used in order to perform these modifications.
  • If specialist software has been developed in order to achieve any of the above then you should endeavour to offer the source code under an open license with descriptions on how to compile and run the code, and what dependencies (hardware or software) exist.
  • Provide details of any sensitive or confidential data and any conditions around access.