Object Management Reporting (CPP-013)
| CPP-Identifier | CPP-013 |
| CPP-Label | Object Management Reporting |
| Author | Johan Kylander |
| Contributors | Matthew Addis |
| Evaluators | Franziska Schwab, Felix Burger, Maria Benauer |
| Change history | Comments |
|---|---|
| Version 1.0.0 - 2025-08-29 | Milestone version |
| Version 1.1.0 - 2026-03-26 | Migration to XML |
| Version 1.2.0 - 2026-05-18 | Reassigned step numbers based on new numbering rules. |
1. Description of the CPP
The TDA delivers reporting to enable the effective management of Objects. This must include a wide range of functional, operational, and statistical reports and analytics.
Inputs and outputs
| Input(s) | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| Metadata |
| ||||||||
| Output(s) | |||||||||
| Metadata |
| ||||||||
| Documentation/guidance |
| ||||||||
Definition and scope
Object management reporting is a process in which the TDA creates reports; outputs Provenance metadata; and produces statistical data on the content it preserves. The reporting is needed to enable effective management of Objects. Reporting is done for both the TDA itself, helping it in its preservation planning and as input for Risk Mitigation (CPP-012), and for the designated communities and stakeholders that produce and consume the data. Effective reporting enables a TDA to conduct digital preservation and to select the Information packages or Objects when performing preservation actions.
Reporting on the content includes reports and Provenance metadata from other CPPs that perform actions on digital content. For example, this includes processes that periodically check the quality of the data in Data Quality Assessment (CPP-019) or during triggered events such as Ingest (CPP-029) and Enabling Access (CPP-025):
- Reports from periodic Integrity Checking (CPP-003);
- Preservation actions taken and documented in Data Corruption Management (CPP-004);
- Virus Scanning reports (CPP-007);
- File Format Identification (CPP-008) reports;
- File Format Validation (CPP-010) reports;
- File Migration (CPP-014);
- Data on Emulation and Rendering Tools (CPP-015);
- Metadata from Metadata Ingest and Management (CPP-016);
- Metadata from Rights Management (CPP-020);
- Metadata from Significant Properties Definition (CPP-022);
- Preservation actions taken and documented in File Repair (CPP-027);
- Data from the Creation of Derivatives (CPP-028) process;
- Metadata from the access and use of Objects in TDA by the designated community;
- Metadata on the data volumes and growth rates of the Objects held by the TDA.
As the purpose of reporting is to enable the preservation and the management of digital Objects, the reports usually cover the main types of data that a TDA operates with. This may include data on:
- File formats;
- Technical metadata and significant properties of Objects;
- Tools and software needed to manage the content;
- The health of Objects and actions taken to remedy errors;
- The hardware infrastructure;
- Metadata and metadata standards;
- The provenance of the Objects;
- The licenses and rights to retain, preserve and provide access to Objects;
- The level of usage of Objects in the TDA;
The report types produced in the reporting process can be categorised as follows:
- Statistical data (e.g. number of Objects, file sizes etc.): Used for helping a TDA or stakeholder assess the scope of preservation actions;
- Provenance metadata (i.e. documented preservation actions by the TDA): Used for assessing the state of Objects, the so called "health" of the Files, and to add authenticity by documenting the life-cycle of all digital content in a TDA;
- In depth machine-actionable reports (usually produced by tools): These are used as input in other processes conducted by the TDA;
- Links to knowledge base resources (e.g. file format registries): These are used to help a TDA in preservation planning.
Reporting activities as well as the report types listed above feed into a wide range of management processes and decision making. Some examples include:
- Risk assessment and preservation planning (e.g. using reports on file formats);
- Reporting to funders and stakeholders (e.g. by providing usage statistics);
- Capacity planning and purchasing decisions (e.g. purchasing and refreshment of storage infrastructure based on statistics on data volumes and growth rates);
- Compliance assessments (e.g. using reports on rights and participant consent to check that personal data is retained in compliance with GDPR);
- Optimisation and cost management (e.g. identification of expensive or inefficient processes based on execution time and steps required, or optimising the use of different storage classes for frequently or infrequently accessed data based on usage statistics);
- Identification of anomalies in error rates or failures (e.g. unusually problematic content from specific depositors);
- Deaccessioning of Objects (e.g. reports on Objects that no longer need to be retained because their retention schedules are about to expire, or reports on quality assessment that mean Objects no longer meet the needs of a designated community);
- Environmental sustainability (e.g. use of storage, processing and access statistics as an input to calculating carbon footprint).
When the process description uses the term report, it can be any of the above.
Process description
Trigger event(s)
| Trigger Event | CPP-identifier |
|---|---|
| Ingest | CPP-029 (Ingest) |
| Enabling Access | CPP-025 (Enabling Access) |
| Risk Mitigation | CPP-012 (Risk Mitigation) |
| Data Quality Assessment | CPP-019 (Data Quality Assessment) |
| Reporting needs from the stakeholders or designated communities |
Step-by-step description
| No | Supplier | Input | Steps | Output | Customer | ||
|---|---|---|---|---|---|---|---|
| sequence | |||||||
| 1 | sequence - Determination and collection of required data | ||||||
| 1.1 | sequence - Evaluation of Reporting requests | ||||||
| 1.1.1 | CPP-029 (Ingest) CPP-025 (Enabling Access) CPP-012 (Risk Mitigation) CPP-019 (Data Quality Assessment) | Reporting request (from CPPs, stakeholders or the consumers) in the form of a Report Specification | The TDA receives the request and determines what data is required to provide the requested report | Specification of the data required for the report | |||
| 1.1.2 | Specification of the data required for the report | Determine if reporting data is available (e.g. is it already an output of other CPPs) | Availability of data required for the report | ||||
| 1.1.3 | Availability of data required for the report. | Optional: Determine if changes are needed to data aggregation.If the reporting data is not available:
| Updated Report Specification | ||||
| Updated Specification of data required for the report | |||||||
| 1.2 | sequence - Revising report specification | ||||||
| 1.2.1 | Updated Specification of data required for the report (from 1.1.3) | Optional: In case of changes to data requirements, the CPPs that produce the required data are revised so that the necessary data is produced and compiles the report (as provided by other CPPs) | |||||
| 1.2.2 | Updated Specification of data required for the report (from 1.1.3) | Optional: The TDA gathers and aggregates the data needed for the test report. | Data required for report | ||||
| 1.2.3 | Data required for report | Optional: The test report is compiled and reviewed with the requestor.If further modifications are needed to the data and data collection, then go back to step 1.2.1. | Finalised Specification of Report | ||||
| Report Specification | |||||||
| 2 | sequence - Handling recurring reports | ||||||
| 2.1 | Reporting schedule | Optional: If the report is required on a regular basis, e.g. monthly, then a reporting schedule is set for collecting data on a regular basis | Scheduled report data aggregation | ||||
| 3 | sequence - Data aggregation and report creation | ||||||
| 3.1 | Specification of data required for the report (from 1.1.1 or 1.1.3) | Gather and aggregate data for report | Data required for report. | CPP-029 (Ingest) CPP-025 (Enabling Access) CPP-012 (Risk Mitigation) CPP-019 (Data Quality Assessment) | |||
| Scheduled report data aggregation (from 2.1) | |||||||
| 3.2 | Data required for report (from 3.1) | Produce Report and deliver to Requestor.If a report is produced regularly, then loop to Step 3.1. | Report | ||||
| Report Specification (from 1.1.1 or 1.2.3) | |||||||
Rationale(s) and worst case(s)
| Rationale | Impact of inaction or failure of the process |
|---|---|
| The TDA knows what Information packages it preserves and what they contain | Without being able to locate and report the data it holds, the TDA cannot perform any preservation actions or provide (e.g. searching by Rights, Provenance and Descriptive metadata within the Information packages). |
| The TDA knows which file formats it holds and can locate these Objects within Information packages | Without knowing in what format the Objects it holds are, the TDA cannot plan preservation actions or inform the designated communities about preservation strategies. |
| The TDA knows what metadata standards it holds and which standards apply to which Objects | Without being able to analyse the Objects and their significant properties, the TDA cannot plan preservation actions, provide discovery or access. |
| The TDA maintains and generates Provenance metadata during preservation | Processes that produce reports and provenance data must have their output stored. This information is needed to analyse the Objects in a TDA, create quality reports, provide designated communities with assurance of a high quality digital preservation |
| The TDA knows its hardware infrastructure and has a plan for its management | Without knowledge on the hardware infrastructure, the TDA cannot maintain high-quality bit-level preservation and report to the stakeholders. |
| The TDA knows the rights it has to preserve and provide access to its holdings. | Without knowledge of rights and retention schedules, the TDA cannot know with confidence that it has the permission to preserve its holdings or whether it is holding content that should be deaccessioned. |
2. Dependencies and relationships with other CPPs
Dependencies
| CPP-ID | CPP-Title | Relationship description |
|---|---|---|
| CPP-003 | Integrity Checking | Periodic integrity checking provides reports on the integrity of data and reports corrupted AIPs. |
| CPP-004 | Data Corruption Management | Fixing corrupted AIPs produces Provenance metadata and data for quality reporting to the stakeholders. |
| CPP-007 | Virus Scanning | Reports on virus scanning activities, frequency of threats, and outcomes of the actions provide essential input for operational management and risk assessment. |
| CPP-008 | File Format Identification | File format identification reports are required for a TDA to enable it to manage its content. |
| CPP-010 | File Format Validation | File format validation provide essential information on the well-formedness and validity of the Objects; validation errors; and data on the tools used in the process. |
| CPP-014 | File Migration | File migration provides information on the outcome of the process as well as tools used. |
| CPP-015 | Emulation and Rendering Tools | The process of selecting tools for emulation and rendering provides data to the TDA for reporting to the designated communities. |
| CPP-016 | Metadata Ingest and Management | Metadata ingest provides new Provenance metadata. |
| CPP-022 | Significant Properties Definition | To report on the characteristics of Objects for deeper analysis, the significant properties must have been defined. |
| CPP-027 | File Repair | Fixing invalid Files produces Provenance metadata and data for quality reporting to the stakeholders. |
| CPP-028 | Creation of Derivatives | Creation of new Objects provides data for statistical reporting. |
Other relations
| Relation | CPP-ID | CPP-Title | Relationship description |
|---|---|---|---|
| May require | CPP-005 | Identifier Management | The management and reporting should require that the data is identified with PIDs. |
| Affinity with | CPP-029 | Ingest | Ingest is both an important provider of reporting data to the TDA (via other CPPs) as well as a customer, as the ingest checks and outcomes must be reported to the producer. |
| Affinity with | CPP-025 | Enabling Access | Enabling Access of contents include providing Provenance metadata, statistical data and quality reports to the consumer. |
| Affinity with | CPP-012 | Risk Mitigation | To plan and mitigate risks in preservation, a TDA needs to provide input on the preservation system, the quality of the data, significant properties in Objects, storage management Metadata etc. |
| Affinity with | CPP-019 | Data Quality Assessment | To evaluate the quality of the data, the process needs input in the form of various Metadata. |
3. Links to frameworks
Certification
| Certification framework | Term used in framework to refer to the CPP | Section |
|---|---|---|
| CTS Link | Reporting is not defined directly as a
requirement, but as the category “Digital
Object Management”, which contains the
following requirements:
| |
| Nestor Seal Link | Reporting is not defined directly as a
requirement, but there are specific
requirements for various metadata
categories, which are specified with
reporting in mind:
| |
| ISO 16363 Link | Reporting as such is not described, but referenced multiple times as a way for the TDA to demonstrate that it is meeting a requirement. See 3.2.1.3, 3.3.4, 3.5.1, 4.1.7, 4.6.2.1, 5.1.1.1, 5.1.1.3 and 5.1.1.3.1 |
Other frameworks and reference documents
| Reference Document | Term used in framework to refer to the process | Section |
|---|---|---|
| OAIS Link | Generate Report | 4.2.3.5 |
| PREMIS Link | PREMIS does not dedicate any documentation to reporting, but it mentions reporting when highlighting the importance of storing events and metadata. |