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

How should we map fields I.3.3.1 (ADDRESS_FURTHER_INFO_IDEM) and I.3.4.2 (CONTRACTING_BODY/ADDRESS_PARTICIPATION_IDEM) when there are multiple Buyers #333

Open
csnyulas opened this issue Jan 30, 2023 · 0 comments
Assignees
Labels
type: feature request something requested to be implemented in a future release type: implementation question something needs clarified, refined or decided before the implementation can continue

Comments

@csnyulas
Copy link
Contributor

This is question raised by @muricna, which was added as a comment to a related issue: #258 (comment)

1.3.3.1 When there is more than one buyer and therefore more than one address above should there not both addresses be foreseen.

The question is applicable for the mapping of either of the fields called "The above mentioned address" which can appear in F21, F22 and F23:

  • field I.3.3.1 with XPath: CONTRACTING_BODY/ADDRESS_FURTHER_INFO_IDEM, and
  • field I.3.4.2 with XPath: CONTRACTING_BODY/ADDRESS_PARTICIPATION_IDEM

Currently, if the XML element ADDRESS_FURTHER_INFO_IDEM, resp. ADDRESS_PARTICIPATION_IDEM, is present in the XML notice, we will create an epo:ProcurementProcedureInformationProvider, resp. epo:TenderReceiver, instance by using the information that is available on the Buyer, at XPATH CONTRACTING_BODY/ADDRESS_CONTRACTING_BODY. In case there are multiple buyers, which are expressed by the existence of (possibly multiple) CONTRACTING_BODY/ADDRESS_CONTRACTING_BODY_ADDITIONAL XML element(s), we do not map any of those additional addresses into the epo:ProcurementProcedureInformationProvider and/or the epo:TenderReceiver class.

The current solution has a clear interpretation: The "main" buyer, or the buyer mentioned first, is the one where further information can be obtained, resp. tenders/requests can be submitted. It is worth noting that the question does not imply in any form that there might be multiple such addresses. It is "The above mentioned address", not "The above mentioned address(es)"

If the current solution is not enough/appropriate, we will need to discuss:

  • What does it meansto have multiple epo:ProcurementProcedureInformationProvider and/or the epo:TenderReceiver instances?
  • If there are epo:ProcurementProcedureInformationProvider and/or the epo:TenderReceiver instances, is there any order of preference where the additional information can be obtained from, or tenders/request submitted to? How can we encode such order of preference?
  • Do we need to create epo:ProcurementProcedureInformationProvider and/or the epo:TenderReceiver instances for all additional buyers (besides the "main" buyer), or just some of them? How would we know for which ones?
@csnyulas csnyulas added question type: implementation question something needs clarified, refined or decided before the implementation can continue labels Jan 30, 2023
@costezki costezki added type: feature request something requested to be implemented in a future release and removed question labels Jan 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature request something requested to be implemented in a future release type: implementation question something needs clarified, refined or decided before the implementation can continue
Projects
None yet
Development

No branches or pull requests

3 participants