-
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 guidance on linking releases from different publications #1646
Conversation
duncandewhurst
commented
Oct 10, 2023
- Closes Add guidance on linking releases from different publications #1430
I suggest reviewing the HTML version of the new page as the examples are easier to parse that way. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly all good just the one comment on when to use the link with a 'prev' relationship
@jpmckinney let me know if you'd prefer to review in a Google Doc. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I reviewed at a mid-level. That said, I don't expect I'll have much more when I read more slowly.
I haven't reviewed the Colombia case from the issue. Which example to they fall into?
The CRM issue was closed before we learned whether ANI and Colombia Compra use consistent mappings, but that seems very unlikely so I think they fall under "how to connect releases from different publications without reusing ocids". |
@jpmckinney I think this PR is awaiting your review per your comment in #1646 (comment). I'll re-request a review so that it is marked as such. |
…f 'prev' code for non-OCDS publications.