You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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
EC-OBPSS
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:
For these reasons, the initial recommendation is not to introduce this field into OBPS.
Questions for the community
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.