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.

Sign up for GitHub

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

Jump to bottom

epo:refersToLot relation should be used only on epo-not:ResultNotice instances #430

Open
csnyulas opened this issue Jul 12, 2023 · 1 comment
Open

epo:refersToLot relation should be used only on epo-not:ResultNotice instances #430

csnyulas opened this issue Jul 12, 2023 · 1 comment
Assignees
@csnyulas
Labels
type: bug Something implemented incorrectly in a release. type: feature request something requested to be implemented in a future release
Milestone
2023-05-future

Comments

@csnyulas
Copy link
Contributor

from the EPO 3.1.0 Glossary:
image
@csnyulas csnyulas added type: bug Something implemented incorrectly in a release. type: feature request something requested to be implemented in a future release labels Jul 12, 2023
@csnyulas csnyulas added this to the 2023-05-future milestone Jul 12, 2023
@csnyulas csnyulas self-assigned this Jul 12, 2023
@csnyulas csnyulas mentioned this issue Jul 12, 2023
Open
@csnyulas
Copy link
Contributor Author

The fix in the TM would be to change the child component of the joinCondition in the predicateObjectMap of the epo:refersToLot property

from:
rr:child "if(not(exists(/TED_EXPORT/FORM_SECTION/F20_2014))) then 'true' else 'false'";
to:
rr:child "if(../NOTICE/@TYPE='AWARD_CONTRACT' or ../NOTICE/@TYPE='CONCESSION_AWARD_CONTRACT') then 'true' else 'false'";

The CM for all forms (but especially for those that can generate multiple notice types) should also updated to include this condition.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@csnyulas csnyulas

Labels
type: bug Something implemented incorrectly in a release. type: feature request something requested to be implemented in a future release
Projects
None yet
Milestone
2023-05-future
Development

No branches or pull requests
1 participant
@csnyulas