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

TED Mapping - Additional Addresses #275

Closed
timgdavies opened this issue Dec 14, 2015 · 0 comments
Closed

TED Mapping - Additional Addresses #275

timgdavies opened this issue Dec 14, 2015 · 0 comments

Comments

@timgdavies
Copy link
Contributor

In the EU TED standard there are a number of spaces for organisation details beyond the 'buyer', 'procuringEntity' and 'supplier' addresses captured in OCDS.

These appear to take two forms:

(1) Some are contact_contracting_body objects;
(2) Others are `contact_review`` objects

Addresses

The addresses include:

  • Multiple possible addresses for CONTRACTING_BODY - in the ADDRESS_CONTRACTING_BODY_ADDITIONAL fields (1..49).
    • contact_contracting_body
    • These appear to be used when there is Joint Procurement
    • Question: Are there additional contracting bodies in cases without joint procurement?
  • ADDRESS_PARTICIPATION
    • contact_contracting_body
    • Question: What is the exact semantics of this field?
  • ADDRESS_FURTHER_INFO
    • contact_contracting_body
    • Address to request further info on the tender
  • ADDRESS_REVIEW_BODY
    • Simpler address type contact_review
  • ADDRESS_REVIEW_INFO
    • Simpler address type contact_review
  • ADDRESS_MEDIATION_BODY
    • Simpler address type contact_review

Handling in OCDS

To handle these in OCDS we need to consider whether:

  • (a) To create some sort of abstract 'additional organisations' array, which can contain a range of organisations each with a type;
  • (b) To create explicit properties for each type of organisation;

My preference is towards (b).

In OCDS, address further info should probably also be serialised into the submissionMethodDetails field with some explanatory text.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants