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

1333 better guidance map hard cases structure #1338

Merged
merged 14 commits into from
Jul 29, 2021

Conversation

jpmckinney
Copy link
Member

close #1333

(This PR is a bit of a "proof of concept" - I'd do another top to bottom proof read to make sure the old content fits well with the new structure before moving it from draft. On the other hand, since there will be quite a few changes (discussed in the first paragraph of #1333), it might make sense to not spend too much time on the current version.)

@jpmckinney
Copy link
Member Author

@JachymHercher Is this PR in progress or ready for review?

@JachymHercher
Copy link
Contributor

Ready for review.

@jpmckinney
Copy link
Member Author

jpmckinney commented Jul 29, 2021

The Map page is edited to reduce the levels of hierarchy and improve the flow. The only more substantive change is the removal of the organization identifiers section, which mostly linked to and repeated the worked example. See #1300

Some pages were merged. I'll describe the changes here.

  • awards_contracts_buyers_suppliers is split between awards_contracts and buyers_suppliers
    • The first paragraph is moved to awards_contracts, verbatim
    • The second paragraph is moved to awards_contracts, edited for the new structure
    • "Definitions" is moved to both pages, verbatim
    • "Award" loses the UNCITRAL definition, which describes the stage, whereas we are trying to describe award decisions, of which many can occur in the award stage
    • "Contract" is moved to awards_contracts, verbatim
    • "Buyer" and "Suppliers" are moved to buyers_suppliers, verbatim
    • "Electronic catalog" is moved to a separate page, verbatim, because it is unrelated to either page
    • "Purchase order" is omitted (see below).
    • "The OCDS model" is moved to the top of awards_contracts, where it makes sense after an initial paragraph that discusses different procedures. It's not included in buyers_suppliers, where it would just be a repetition of what OCDS is.
    • "Awards and contracts" is moved to awards_contracts, verbatim
    • "Buyers" and "Suppliers" are merged into the earlier "Buyer" and "Suppliers" sections
  • consortia is merged to buyers_suppliers, verbatim
  • award_notices_decisions is merged into awards_contracts, with a change in heading text
  • mapping_awards_contracts is merged to awards_contracts, verbatim (i.e. only heading level changes)
  • purchase_orders is merged to awards_contracts, but loses two paragraphs (below)

Purchase orders loses these paragraphs, and is otherwise identical:

A purchase order is [a specific type of contract,] an official document issued by a buyer committing to pay a supplier for the supply of specific goods, works or services to be delivered in the future.

Purchase orders can be issued against an existing contract, or if no prior contract exists then acceptance of a purchase order by a supplier forms a contract between buyer and supplier.

The purpose of the worked example is to demonstrate a specific scenario in which disclosing purchase orders in contracts leads to double-counting - with the instruction to such use of the contracts array.

The additional paragraphs above might create more confusion than they resolve; the first paragraph, for example, is true of most contracts. For the purpose of the worked example, they are not needed.

(See also a long discussion about purchase orders in #896. )

@jpmckinney jpmckinney merged commit 15c7ca1 into 1.1-dev Jul 29, 2021
@jpmckinney jpmckinney deleted the 1333-better-guidance-map-hard-cases-structure branch July 29, 2021 23:56
@jpmckinney
Copy link
Member Author

This is much better, thank you! https://standard.open-contracting.org/staging/1333-better-guidance-map-hard-cases-structure/en/guidance/map/

@jpmckinney jpmckinney added this to the Iterative improvements milestone Jul 30, 2021
jpmckinney added a commit that referenced this pull request Jul 30, 2021
jpmckinney added a commit that referenced this pull request Jul 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

Better Guidance/Map/*/Mapping the hard cases structure
2 participants