Skip to content

Inclusion of metadata field "Data Life Cycle Steps" #3

Open

Description

@PatricaCabrera

Background

EC-OBPSS proposes to use a metadata field for Data Life Cycle Steps. This field does not exist in IOC-OBPS.

Before introducing a new metadata field, we would like to assess whether it provides additional value or duplicates information already captured elsewhere in the OBPS metadata model.

Current situation

IOC-OBPS

  • Data management-related activities are already described using the Data Management Processes vocabulary.

EC-OBPSS

  • The controlled vocabulary or authoritative reference for this field has not yet been identified.

Preliminary assessment

The current view is that Data Life Cycle Steps substantially overlaps with the existing Data Management Processes field used in OBPS.

Adding both fields may:

  • duplicate information,
  • create inconsistencies between records,
  • increase the effort required for metadata curation, and
  • make it less clear which field contributors should use.

For these reasons, the initial recommendation is not to introduce this field into OBPS.

Questions for the community

  • Does this field provide information that cannot already be captured by Data Management Processes? See issue Review of "Methodology Type" vocabulary #1
  • Is there an authoritative vocabulary or standard defining Data Life Cycle Steps?
  • Are there use cases where both fields are needed?

Proposed outcome

Current recommendation: Do not include Data Life Cycle Steps as a separate metadata field unless a clear use case and non-overlapping scope can be demonstrated.

Activity

  1. changed the title [-]Inclusion of metadata field **Data Life Cycle Steps**[/-] [+]Inclusion of metadata field "Data Life Cycle Steps"[/+] on Jul 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions