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

BT-133 Public Opening Place is too vague. #714

Open
AchillesDougalis opened this issue Nov 18, 2024 Discussed in #570 · 0 comments
Open

BT-133 Public Opening Place is too vague. #714

AchillesDougalis opened this issue Nov 18, 2024 Discussed in #570 · 0 comments
Assignees
Labels
aux: alignment alignment between ESPD, eForms and ePO aux: mapping it is related to the TED-SWS mappings project module: ePO core ePO core
Milestone

Comments

@AchillesDougalis
Copy link
Contributor

Discussed in #570

Originally posted by AchillesDougalis February 26, 2024
the "BT-133 Public Opening"field used in eforms has a "text" datatype, and has the following description: "The place (e.g. physical address, URL) where the tenders will be publicly opened."
So, BT-133 is a description, but it could also be an address, a url, a building etc. How should the ePO team allign with the eForms team in order to create a usefull representation of this in ePO?

@AchillesDougalis AchillesDougalis added aux: mapping it is related to the TED-SWS mappings project module: ePO core ePO core aux: alignment alignment between ESPD, eForms and ePO labels Nov 18, 2024
@AchillesDougalis AchillesDougalis added this to the 5.0.0 milestone Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
aux: alignment alignment between ESPD, eForms and ePO aux: mapping it is related to the TED-SWS mappings project module: ePO core ePO core
Projects
None yet
Development

No branches or pull requests

2 participants