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

tx1-2: fileds that may appear in multiple notice type (e.g. estimated date of publication) #249

Closed
costezki opened this issue Nov 23, 2022 · 2 comments
Assignees
Labels
act: for closing it can be closed but an additional confirmation is needed type: bug Something implemented incorrectly in a release.
Milestone

Comments

@costezki
Copy link
Collaborator

costezki commented Nov 23, 2022

[N Muric] F21 context

II.3 This field is only used for Prior information Notice to show the estimated date of Publication of the Contract Notice and not the date of publication of the Result notice as shown in the mapping.

Answer: A simple solution is to map this field to epo:Notice because only contract notices and PINs may have such field, and thus only on those cases the mapping will be activated.

IV2.1 This field can also be used for calls for competition so going through the ResultNotice does not always work. See 459484-2021

Anser: idem

@costezki costezki added the type: bug Something implemented incorrectly in a release. label Nov 23, 2022
@costezki costezki added this to the 2022-12 milestone Nov 23, 2022
@costezki costezki changed the title tx1-2: estimated date of publication on ResultNotice tx1-2: fileds that may appear in multiple notice type (e.g. estimated date of publication) Nov 23, 2022
@csnyulas
Copy link
Contributor

This should be handled when we fix #238

@csnyulas
Copy link
Contributor

csnyulas commented Dec 7, 2022

The conceptual mapping aspects of this issue is handled in version 5.0.1 of the CM, and the technical mapping is also done (see the commits referencing this issue), however there is an outstanding question for the first problem mentioned in this issue for which we created a separate issue (#262). So, we will mark this issue fixed and will close it.

@csnyulas csnyulas closed this as completed Dec 7, 2022
@csnyulas csnyulas added the act: for closing it can be closed but an additional confirmation is needed label Dec 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
act: for closing it can be closed but an additional confirmation is needed type: bug Something implemented incorrectly in a release.
Projects
None yet
Development

No branches or pull requests

2 participants