Data Quality Assessment (CPP-019)

CPP-IdentifierCPP-019
CPP-LabelData Quality Assessment
AuthorMikko Laukkanen, Juha Lehtonen
ContributorsBertrand Caron, Johan Kylander
EvaluatorsFranziska Schwab, Felix Burger, Maria Benauer
Change historyComments
Version 1.0.0 - 2025-08-29Milestone version
Version 1.1.0 - 2026-03-27Migration to XML

1. Description of the CPP

The TDA evaluates and re-evaluates the data quality of Information Objects

Inputs and outputs

Input(s)
Data
Information object
File
Metadata
Descriptive metadata
Technical metadata
Provenance metadata
Rights metadata
Structural metadata
Documentation/guidance
Quality assessment policy
Format policy - preferred formats
Collection development policy
Metadata recording policy
Output(s)
Documentation/guidance
Quality assessment report

Definition and scope

Data Quality Assessment refers to the systematic evaluation of Objects and their associated Metadata against predefined measures to ensure they meet the standards necessary for consumers' needs and continued access. The assessment typically covers several key dimensions, some of these are for example:

  • Authenticity: The Object is what it purports to be (i.e. it has been created, modified and sent by the person purported to have done it at the date and time purported). The designated community must be able to trust that the data is real and credible and is managed by a trustworthy TDA. Sufficient information must exist to understand the Object's creation circumstances, provenance, and relationship to other content. In addition to integrity checks, the authenticity of the data is ensured by controlled changes through preservation actions and the Provenance metadata.
  • Completeness: The Object and the Metadata are complete. They do not have missing parts or links to targets outside the preserved Object which should remain accessible.
  • Consistency: The Object is presented in applicable file formats or Representations with applicable metadata formats. Conflicting values in the Metadata should be avoided.
  • Relevance: The data preservation is based on a predefined collection development policy (i.e. has a purpose of being preserved).
  • Structured: The structure of the Object is described in the Metadata. Complex Objects are organised, including relationships between Files, proper sequencing of multi-part Objects, and the integrity of any embedded Metadata or links.
  • Understandability: The information is understandable and meaningful for the designated community.
  • Validity: The Object and Metadata are valid against the File and metadata format specifications and standards, and comply with all other predefined profiles and rules.

Data quality assessment may include various processes, repeated from time to time. A very common phase to perform an assessment is in the Ingest phase, but the use case described below demonstrates that such a process can also be performed at the access stage. The data may be rejected from digital preservation, if it does not meet the criteria. An assessment typically has the following steps, described on a very high level:

  1. Define the scope of the assessment;
  2. Define data quality dimensions and metrics, including possible thresholds;
  3. Gather and analyse data;
  4. Create a quality report about all the findings;
  5. If needed, update the data and Metadata to improve the quality.

The step-by-step description below mainly concentrates on the technical aspects of the data and Metadata, but the scope of this CPP is indeed covering a broader range of contextual data quality properties.

The assessment process often employs both automated tools and manual review. For example, automated tools can perform file format identification, validate File or Information package structures, check for malware, verify checksums, or check for completeness of a delivery against an inventory. Human reviewers, for example, may evaluate content accuracy, Metadata completeness, and contextual adequacy. The processes should be automated as much as possible for faster processing and to avoid human errors.

Results from Data Quality Assessment affect preservation planning decisions (e.g. what additional Metadata needs to be captured). The assessment also establishes baseline quality metrics that can be monitored over time to detect degradation or other changes that might necessitate intervention.

Process description

Trigger event(s)

Trigger EventCPP-identifier
IngestCPP-029 (Ingest)
Metadata ingestCPP-016 (Metadata Ingest and Management)
Mass export of AIPs from the TDACPP-006 (AIP Batch Export)
Periodic re-appraisal

Step-by-step description

NoSupplierInputStepsOutputCustomer
 sequence
1CPP-018 (Community Watch)Preservation objectives Based on preservation intent as defined by Community Watch, derive quality properties that will be extracted by other CPPs Quality properties
2Quality properties The TDA receives a defined set of quality properties and determines what data is required to create a quality assessment report. This triggers steps 3 to 8 Specification of the data required for the assessment.
3 alternative - Different handling based on nature of quality properties
3.aSpecification of the data required for the assessmentIf quality properties concern file formats:Assess the file format against the preferred formats policyTechnical quality report
File
CPP-008 (File Format Identification)File format identifier
Format policy - preferred formats
3.bSpecification of the data required for the assessmentIf quality properties concern the validity of formats:Assess the validity status.Technical quality report
File
CPP-010 (File Format Validation)Validity status
3.cSpecification of the data required for the assessment If quality properties concern technical qualities or completeness of Files or Representations: Assess the technical quality and completeness against quality properties Technical quality report
File / Representation
Quality properties
CPP-009 (Metadata Extraction)Extracted Metadata
3.dSpecification of the data required for the assessmentIf quality properties concern metadata quality:Assess the metadata quality.Metadata ingest report
Metadata recording policy
Object
CPP-016 (Metadata Ingest and Management) Metadata
3.eSpecification of the data required for the assessmentIf quality properties concern existence of malware:Scan for malwareVirus scanning report
CPP-007 (Virus Scanning) File
3.fSpecification of the data required for the assessment If quality properties concern the legal status and authenticity of the Object: Assess the legal status of the Object Legal status report
CPP-020 (Rights Management) Rights metadata
Object
4Optional: File format identifierCreation of quality assessment report from suppliersQuality assessment report
Optional: Validity status
Optional: Metadata ingest report
Optional: Technical quality report
Optional: Virus scanning report
Optional: Legal status report
5Quality assessment reportAssess the quality of an Object during specific stages (e.g. during ingest)CPP-029 (Ingest)
6Optional: The quality of an Object, AIP or Metadata can be enhanced or modified based on the quality assessment report. It may run for example some of the following CPPs:
  • CPP-014 (File Migration)
  • CPP-016 (Metadata Ingest and Management)
  • CPP-017 (Disposal)
  • CPP-026 (File Normalisation)

Rationale(s) and worst case(s)

RationaleImpact of inaction or failure of the process
Quality assessment identifies vulnerabilities before they result in data loss, allowing the TDA to take preventive action rather than reactive measures. As digital preservation spans decades or centuries during which technological environments will change completely multiple times, the data quality assessment evaluates whether current Objects contain sufficient technical and contextual information to remain interpretable by future systems and users. Uncontrolled file format obsolescence, hardware failure or bit corruption.Loss of content interpretability over time, authenticity and/or significant properties.
Data Quality Assessment helps the TDA to take informed preservation decisions regarding appraisal and re-appraisal based on quality metrics. Identification, automated extraction and correct interpretation of such metrics is fundamental to collection development. No knowledge or no capacity to assess the quality of the Object could lead to appraisal of Representations of poor quality despite Representations of better quality being available.

2. Dependencies and relationships with other CPPs

Dependencies

CPP-IDCPP-TitleRelationship description
CPP-007Virus Scanning Virus Scanning acts as a supplier since scanning for viruses is performed as a step in the overall Data Quality Assessment.
CPP-009Metadata Extraction Metadata extraction returns Metadata that are used to assess the File quality (e.g. for an audiovisual File quality assessment may rely on Metadata such as bit depth, sampling frequency, etc.)
CPP-018Community Watch The signals from the community may affect the Data Quality Assessment. For example, the Data Quality Assessment performed during Ingest may result in extraction of quality properties that are required by the Designated Community.

Other relations

RelationCPP-IDCPP-TitleRelationship description
May requireCPP-020Rights ManagementAssessing the legal status and authenticity of Objects requires Rights metadata.
May requireCPP-005Identifier ManagementData Quality Assessment may include validating the PIDs and their linked resources.
Required byCPP-009Metadata Extraction The selection of an appropriate extractor tool depends on requirements as provided by Data Quality Assessment.
Required byCPP-029Ingest Ingest uses the Quality Assessment report as produced by Data Quality Assessment to accept or reject the Object.
May be required byCPP-029Ingest The TDA may have quality requirements as produced by Data Quality Assessment that may be checked during ingest.
Affinity withCPP-013Object Management ReportingObject management reporting relates to re-evaluating quality dimensions.
Affinity withCPP-022Significant Properties Definition As Data Quality Assessment identifies quality properties whose value will determine whether the Objects are ingested or not, these quality properties will likely be also considered significant by the TDA.
Affinity withCPP-023Risk Properties Definition and Extraction Both CPP-019 and CPP-023 are defining properties that the TDA should consider and interpret against the result of CPP-009 (Metadata extraction).
Affinity withCPP-025Enabling Access DIPs should conform to the quality aspects as specified by the TDA.

4. Reference implementations

Use cases

Access Quality Metrics for Net Art

Institutional background
InstitutionRhizome, US
Hyperlinkhttps://doi.org/10.17605/OSF.IO/6RNK4
Description
Trigger event Rhizome’s ArtBase faces significant challenges in providing high-quality, reliable access to their collections. Over time, the software, hardware, and file formats used to create and view these works become obsolete, leading to a degraded user experience or rendering the art inaccessible.
Problem statement The primary problem is the lack of a standardised method to help users of the ArtBase archive navigate the various versions and access methods of digital artworks. The archive holds multiple "variants" of each piece, which might include live versions from a web server, archived copies, or versions viewed through emulators. Each variant offers a different experience, and without a guide, users might unknowingly choose a version that is incomplete or partially non-functional. The paper notes that visitors need a way to make an informed choice between a version that is integrated into the modern internet landscape but potentially broken, and one that is more historically accurate but requires a special, emulated environment.
Proposed solution The proposed solution is a system that calculates an "access quality score" for each variant of an artwork. This score is a single value, derived from a combination of Technical metadata and curatorial information, which indicates how complete and functional an artwork's performance is likely to be. The system uses a data model to define variants as a combination of archived Files ("artifacts") and the software environment ("machine") used to view them. The score is calculated by determining whether a machine's capabilities support the data formats within the artifact. This system aims to present a simple, three-level "stoplight" indicator (green, yellow, or red) that guides visitors to the best available version, manages their expectations for works with known issues, and ultimately improves the user experience of the ArtBase archive.

Publicly available documentation

InstitutionOrganisation typeLanguageHyperlink
TIB – Leibniz Information Centre for Science and Technology and University Library , DENational library
Non-commercial digital preservation service
Research infrastructure
Research performing organisation
English https://wiki.tib.eu/confluence/spaces/lza/pages/93608984/Specifications
Englishhttps://github.com/TIB-Digital-Preservation/pre-ingest-analyzer
(TIB Pre-Ingest Analyzer (PIA))
CSC – IT Center for Science Ltd., FINon-commercial digital preservation serviceEnglishhttps://digitalpreservation.fi/en/specifications
Achivematica, CADigital preservation systemEnglish https://www.archivematica.org/en/docs/archivematica-1.17/user-manual/appraisal/appraisal/
(Manual assessment can be done using the Appraisal Tab)
English https://www.archivematica.org/en/docs/archivematica-1.17/user-manual/transfer/transfer/#transfer-tab-microservices
(Some of the information needed for quality assessment (e.g. file format validation, characterisation, virus scanning) is produced during the Transfer process)