Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Example: Publishing historical data, when history can't be reconstructed #1031

Open
jpmckinney opened this issue Jun 9, 2020 · 0 comments
Open
Labels
Focus - Examples Relating to examples in the guidance

Comments

@jpmckinney
Copy link
Member

The OCDS model works best when publishers create releases to update a contracting process over its lifetime.

However, when publishing historical data (e.g. information about contracting processes that were completed a decade ago), the publisher might only know the final state; they might not be able to reconstruct the timeline.

In this case, the publisher can publish a single release in the releases array within a record (within a record package), along with a compiled release that is identical except for the value of the tag field.

cc @yolile from Skype discussion on 2019-09-09, in case anything else to add.

@jpmckinney jpmckinney added the Focus - Documentation Includes corrections, clarifications, new guidance, and UI/UX issues label Jun 9, 2020
@jpmckinney jpmckinney added this to the Worked examples milestone Jun 9, 2020
@jpmckinney jpmckinney changed the title Worked example: Publishing historical data, when history can't be reconstructed Example: Publishing historical data, when history can't be reconstructed Jun 7, 2023
@jpmckinney jpmckinney added Focus - Examples Relating to examples in the guidance and removed Focus - Documentation Includes corrections, clarifications, new guidance, and UI/UX issues labels Jun 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Focus - Examples Relating to examples in the guidance
Projects
Status: Backlog: Examples
Development

No branches or pull requests

1 participant