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.

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

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

Issues list

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
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
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
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
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
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
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
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
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
Notice refersToProcedure to be removed aux: mapping it is related to the TED-SWS mappings project module: ePO core ePO core
#715 opened Nov 18, 2024 by muricna 5.0.0
BT-133 Public Opening Place is too vague. aux: alignment alignment between ESPD, eForms and ePO aux: mapping it is related to the TED-SWS mappings project module: ePO core ePO core
#714 opened Nov 18, 2024 by AchillesDougalis 5.0.0
Problem with BT-748 act: for WG discussion it needs to be discussed within the Working Group aux: alignment alignment between ESPD, eForms and ePO aux: mapping it is related to the TED-SWS mappings project module: ePO core ePO core
#713 opened Nov 18, 2024 by AchillesDougalis 5.0.0
how to deal with Unpublished fields act: for WG discussion it needs to be discussed within the Working Group aux: alignment alignment between ESPD, eForms and ePO aux: mapping it is related to the TED-SWS mappings project module: eNotice eNotice module: ePO core ePO core
#712 opened Nov 18, 2024 by AchillesDougalis 5.0.0
eforms BT-133 It might be a good idea to look into whether there are two options full address and url aux: alignment alignment between ESPD, eForms and ePO aux: mapping it is related to the TED-SWS mappings project
#711 opened Nov 18, 2024 by AchillesDougalis 5.0.0
Unable to specify or represent an organisation part/department since ePO 4.0-rc.2 aux: mapping it is related to the TED-SWS mappings project module: ePO core ePO core type: feature request something requested to be implemented in a future release
#710 opened Nov 14, 2024 by andreea-pasare 5.0.0
Should the Ontology Include an eforms SDK version concept act: for WG discussion it needs to be discussed within the Working Group aux: alignment alignment between ESPD, eForms and ePO aux: mapping it is related to the TED-SWS mappings project type: question something needs clarified, refined or decided
#708 opened Oct 17, 2024 by AchillesDougalis 5.0.0
Redo Predicates removed from ePO 4.2.0 act: for implementation it can be implemented and closed, all is clear module: ePO core ePO core type: feature request something requested to be implemented in a future release
#707 opened Oct 16, 2024 by AchillesDougalis 5.0.0
Remodelling of class epo:MiniCompetitionAwardOutcome act: for WG discussion it needs to be discussed within the Working Group aux: mapping it is related to the TED-SWS mappings project module: ePO core ePO core
#706 opened Oct 16, 2024 by AchillesDougalis 5.0.0
Set predicate epo-ful:refersToOrderLine cardinality to [1] act: for implementation it can be implemented and closed, all is clear type: feature request something requested to be implemented in a future release
#704 opened Oct 9, 2024 by AchillesDougalis 5.0.0
Remove Predicate epo-sub:relatesToESPDRequest act: for implementation it can be implemented and closed, all is clear module: eAwarding Pre-awarding type: feature request something requested to be implemented in a future release
#701 opened Oct 7, 2024 by AchillesDougalis 5.0.0
epo-acc:ESPDRequest should be a specialization of epo:TendererQualificationSubmission act: for implementation it can be implemented and closed, all is clear module: eAwarding Pre-awarding type: feature request something requested to be implemented in a future release
#700 opened Oct 7, 2024 by AchillesDougalis 5.0.0
epo-sub:ESPD should be a specialization of epo:QualificationResponse act: for implementation it can be implemented and closed, all is clear module: eAwarding Pre-awarding type: feature request something requested to be implemented in a future release
#699 opened Oct 7, 2024 by AchillesDougalis 5.0.0
ProTip! Exclude everything labeled bug with -label:bug.