Skip to content

Versioning and resource status #1238

@riccardoAlbertoni

Description

@riccardoAlbertoni

Originally posted by @andrea-perego in #93 (comment)
I don't remember if this was already mentioned, but another aspect of versioning may concern the resource "status" - e.g., draft, stable, deprecated, withdrawn.

The EU Publications Office maintains some reference code lists - the two that may be most relevant here are:

E.g., the dataset status code list above includes the following statuses (alphabetically ordered):

Code Label Definition
COMPLETED completed This dataset is considered to be complete, it holds all information that is intended.
DEPRECATED deprecated It is recommended that the contents of this dataset be no longer used.
DEVELOP under development This dataset is currently being assembled. It may be in an incomplete or faulty state.
DISCONT discontinued This dataset is no longer produced or updated.
WITHDRAWN withdrawn This dataset is no longer meant to be published.

The concept status code list includes additional statuses.

This information is clearly useful for administrative purposes, but relevant as well for users.

E.g., in the JRC Data Catalogue, these statuses determine where a dataset can be published (e.g., a dataset in draft status is not supposed to be published in production). On the other hand, deprecated, discontinued, or withdrawn records are not removed from the catalogue (because of the persistence policy we have in place), but they are "marked" as such, so that users are aware they shouldn't be used or are not longer available.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions