-
Notifications
You must be signed in to change notification settings - Fork 46
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
Add links field #928
Comments
We should also look into merging in https://github.com/open-contracting-extensions/ocds_pagination_extension. |
Rather than re-using RelatedProcess, we should use JSON Hyper-Schema, e.g.: {
"links": [
{
"rel": "self",
"href": "https//..."
}
]
} |
Hello, We need to use this extension for the issue 1228, an initial version in the repository that can be found at here: https://github.com/portaledcahn/ocds_Links_extension Please feel free to comment. Greetings |
More recently, we've been discussing the use case of one publication's release referring to another publication's release as canonical. This can be achieved with |
Reopening because we forgot to add the Link object to the building block reference |
Ignore me, I was looking at the wrong version of the docs. |
#1326 says
And
If a publisher is publishing releases only and wants to publish an alternate link to the contracting process, how should they publish this? Still with links, with Context: Dominican Republic wants to publish this type of link https://comunidad.comprasdominicana.gob.do//Public/Tendering/OpportunityDetail/Index?noticeUID=DO1.NTC.1031532 that contains the entire contracting process info in HTML format. |
I think that link can be modelled in The use case for |
Do you mean As per #1228 (comment)
But in this case, this link represents indeed an alternative representation (HTML) of the entire procedure. |
I would just link it in The use case is more than just for alternative representations, but for alternative representations in cases where there is no OCDS data to link to (e.g. when the UK was transitioning from TED to OCDS).
|
Issue
A government might only publish OCDS data for new events in a contracting process. However, they would still want to have a link back to any earlier events (in non-OCDS format).
This might occur in cases of jurisdictional changes, like municipal mergers or EU withdrawal, where the cost and complexity of converting old events might be too high.
Proposal
Add a top-level field, similar to
relatedProcesses
, namedlinks
, e.g.:The
relationship
field would have a different codelist thanrelatedProcess.csv
, with codes for:prev
, Previous publication, The linked resource is a previous publication about this contracting process, that is not in OCDS format or is using a different OCID. This code is intended for use when transitioning from an old system without converting its data, which might occur in cases of jurisdictional changes like municipal mergers.We can propose other codes like:
alternate
, Alternate representation, The linked resource is an alternate representation of this contracting process. For example: a local XML format.There probably aren't any others we want to include at first, but we can be inspired by https://developer.mozilla.org/en-US/docs/Web/HTML/Link_types
The codes should all make sense in the context of a contracting process, not in the context of the individual release. If the field were used in the context of an individual release, then we'd have to make the field
"omitWhenMerged": true
. In most cases, adocuments
field can be used to make links to external resources related to an individual release.The text was updated successfully, but these errors were encountered: