Skip to content

Issues: OP-TED/ePO

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

109 Open 491 Closed
109 Open 491 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Electronic delivery of an item module: eCatalogue eCatalogue
#746 opened Feb 21, 2025 by idolum 5.0.0
@andreea-pasare
New eForms subtype required aux: mapping it is related to the TED-SWS mappings project
#745 opened Feb 20, 2025 by csnyulas 5.0.0
1
Environmental-related information in the catalogue module: eCatalogue eCatalogue
#744 opened Feb 16, 2025 by idolum 5.0.0
@andreea-pasare
at-voc-new:RespoonseStatus should be renamed act: for internal discussion it needs to be discussed within the team module: eFulfilment eFulfilment
#743 opened Feb 12, 2025 by AchillesDougalis 5.0.0
@andreea-pasare
Remove attribute epo:hasReviewURL module: ePO core ePO core
#742 opened Feb 12, 2025 by andreea-pasare 5.0.0
@andreea-pasare
Add action-code and reject-reasons Codelists to epo-ful:ReceiptAdvice module: eFulfilment eFulfilment type: feature request something requested to be implemented in a future release
#741 opened Feb 12, 2025 by AchillesDougalis 5.0.0
@andreea-pasare
Harmonize PostAwardDocument and Line classes links to epo:Document act: for implementation it can be implemented and closed, all is clear
#740 opened Feb 12, 2025 by AchillesDougalis 5.0.0
@andreea-pasare @AchillesDougalis
Mapping of BT-684-Lot "IPI Measures are Applicable" aux: mapping it is related to the TED-SWS mappings project
#738 opened Feb 7, 2025 by andreea-pasare 5.0.0
@andreea-pasare
Property overriding investigation and proposal for modeling approach
#737 opened Jan 25, 2025 by gkostkowski
Unify epo:procedureSpecificTerm and epo:LotSpecificTerm . Keep them only as profiles
#736 opened Jan 21, 2025 by cristianvasquez
Aligning ePO Metadata with CDM and Redefining epo:Document Class hierarchy module: ePO core ePO core type: feature request something requested to be implemented in a future release type: use case Use Case (User story)
#735 opened Jan 21, 2025 by costezki
6 tasks
@muricna
epo-acc:ESPDRequest the definition is wrong
#734 opened Jan 20, 2025 by muricna 5.0.0
@andreea-pasare
2
Investigate if predicates for specific roles are needed. act: for implementation it can be implemented and closed, all is clear module: none no module in particular because the issue is of technical or documentation nature type: feature request something requested to be implemented in a future release
#733 opened Jan 7, 2025 by AchillesDougalis 5.0.0
@AchillesDougalis
Problems mapping "Documents Official Language" and "Documents Unofficial Language" fields (BT-708-Part, BT-737-Part, BT-708-Lot, BT-737-Lot) aux: mapping it is related to the TED-SWS mappings project type: feature request something requested to be implemented in a future release
#732 opened Dec 18, 2024 by csnyulas 5.0.0
@andreea-pasare
2
Relax the cardinality of predicate epo-cat:hasAmount to [0..1] act: for implementation it can be implemented and closed, all is clear module: eCatalogue eCatalogue module: eOrdering eOrdering type: feature request something requested to be implemented in a future release
#731 opened Dec 17, 2024 by AchillesDougalis 5.0.0
@andreea-pasare
Change definition of epo-ord:hasResponseDescription so it can be reused in other modules module: eCatalogue eCatalogue module: eOrdering eOrdering type: feature request something requested to be implemented in a future release
#730 opened Dec 13, 2024 by andreea-pasare 5.0.0
@andreea-pasare
Fix definitions for epo:hasItemStandardID and epo:hasConstraint act: for internal discussion it needs to be discussed within the team module: ePO core ePO core type: bug something implemented incorrectly in a release
#729 opened Dec 11, 2024 by AchillesDougalis 5.0.0
@AchillesDougalis
Should the different prefixes of the Ontology be kept or not? act: for internal discussion it needs to be discussed within the team module: none no module in particular because the issue is of technical or documentation nature type: feature request something requested to be implemented in a future release
#728 opened Dec 11, 2024 by AchillesDougalis miscellaneous
@victoriobentivogli
1
Review all the roles of the Ontology to see if they belong to the correct module act: for internal discussion it needs to be discussed within the team module: none no module in particular because the issue is of technical or documentation nature type: feature request something requested to be implemented in a future release
#727 opened Dec 11, 2024 by AchillesDougalis 5.0.0
@AchillesDougalis
Unmappable eForms fields in PIN, CEI and T02 notice subtypes aux: mapping it is related to the TED-SWS mappings project
#726 opened Dec 11, 2024 by csnyulas 5.0.0
@andreea-pasare
1
epo-ord:hasResponseDescription, change definition request act: for WG discussion it needs to be discussed within the Working Group module: eCatalogue eCatalogue type: feature request something requested to be implemented in a future release
#725 opened Dec 6, 2024 by AchillesDougalis 5.0.0
@andreea-pasare
Versioning of the CM Enterprise Architect files module: none no module in particular because the issue is of technical or documentation nature type: feature request something requested to be implemented in a future release
#724 opened Dec 6, 2024 by AchillesDougalis miscellaneous
@AchillesDougalis
Automatization of the first steps of the Workflow of a new ePO release. module: none no module in particular because the issue is of technical or documentation nature type: feature request something requested to be implemented in a future release
#723 opened Dec 6, 2024 by AchillesDougalis miscellaneous
@AchillesDougalis
Inconistencies with concepts related to taxes, allowances and charges module: eCatalogue eCatalogue module: eOrdering eOrdering type: bug something implemented incorrectly in a release
#722 opened Nov 28, 2024 by idolum 5.0.0
@andreea-pasare
Decide on what prefixes should be used for NUTS and CPV module: ePO core ePO core
#717 opened Nov 25, 2024 by andreea-pasare 5.0.0
@andreea-pasare
ProTip! Mix and match filters to narrow down what you’re looking for.