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

Link to guidance for creating a release #166

Closed
duncandewhurst opened this issue Feb 9, 2023 · 2 comments
Closed

Link to guidance for creating a release #166

duncandewhurst opened this issue Feb 9, 2023 · 2 comments
Labels
2019-reg Relating to the 2019 regulation (eForms) documentation

Comments

@duncandewhurst
Copy link
Contributor

duncandewhurst commented Feb 9, 2023

I'm creating a separate issue for this task from #54 (comment):

* [ ]  Review the guidance for creating a release and decide where it will be linked from

Currently, the instructions for creating a release are linked from two places: Release withheld information and the mapping for BT-701-notice (notice identifier).

I think it would be helpful to add a sub-heading to how to use this profile before 'post-processing steps' with a link to the instructions for creating a release so that implementers know to do that before mapping other fields. The heading could be either 'Convert a notice to OCDS format' or 'Publish a notice in OCDS format', e.g.

Convert a notice to OCDS format

Create a release and map each field on the notice according to the field mappings.

@jpmckinney does that sound good?

@duncandewhurst duncandewhurst added 2019-reg Relating to the 2019 regulation (eForms) documentation labels Feb 9, 2023
@jpmckinney
Copy link
Member

Yes, sounds good!

@duncandewhurst
Copy link
Contributor Author

Done in bd2f108

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2019-reg Relating to the 2019 regulation (eForms) documentation
Projects
None yet
Development

No branches or pull requests

2 participants