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

91 Open 483 Closed
91 Open 483 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

Notice refersToProcedure to be removed
#715 opened Nov 18, 2024 by muricna
1
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
@andreea-pasare @AchillesDougalis
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
@andreea-pasare @AchillesDougalis
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
@AchillesDougalis
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
@andreea-pasare @AchillesDougalis
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
@andreea-pasare
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
@AchillesDougalis
1
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
@AchillesDougalis
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
@AchillesDougalis
1
Remove Predicates from ePO 4.2.0 that were not forseen for 4.2.0 release act: for implementation it can be implemented and closed, all is clear type: bug something implemented incorrectly in a release
#705 opened Oct 9, 2024 by AchillesDougalis 4.2.0
@AchillesDougalis
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
@AchillesDougalis
Revert predicate epo-ful:refersToOrderLine cardinality to [0..1] act: for implementation it can be implemented and closed, all is clear type: bug something implemented incorrectly in a release
#703 opened Oct 9, 2024 by AchillesDougalis 4.2.0
@AchillesDougalis
Catalogue Response module: eCatalogue eCatalogue type: use case Use Case (User story)
#702 opened Oct 7, 2024 by AchillesDougalis
@andreea-pasare @AchillesDougalis
1
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
@andreea-pasare @AchillesDougalis
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
@andreea-pasare @AchillesDougalis
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
@andreea-pasare @AchillesDougalis
To expand epo-ful:TransportMeans class act: for WG discussion it needs to be discussed within the Working Group module: eFulfilment eFulfilment type: feature request something requested to be implemented in a future release
#698 opened Oct 3, 2024 by AchillesDougalis 5.0.0
@AchillesDougalis
Add attributes to epo-ord:OrderLine act: for WG discussion it needs to be discussed within the Working Group module: eOrdering eOrdering type: feature request something requested to be implemented in a future release
#697 opened Oct 3, 2024 by AchillesDougalis 4.3.0
@AchillesDougalis
Suggestion to add epo-ord:hasOrderVATTotalAmount predicate on epo-ord:Order. act: for WG discussion it needs to be discussed within the Working Group module: eOrdering eOrdering type: feature request something requested to be implemented in a future release
#696 opened Oct 3, 2024 by AchillesDougalis 4.3.0
@AchillesDougalis
Document reference from Order Line act: for WG discussion it needs to be discussed within the Working Group module: eOrdering eOrdering type: feature request something requested to be implemented in a future release
#695 opened Oct 2, 2024 by AchillesDougalis 4.3.0
@AchillesDougalis
create new codelist at the level of class epo-ord:DeliveryInformation act: for WG discussion it needs to be discussed within the Working Group module: eOrdering eOrdering type: feature request something requested to be implemented in a future release
#694 opened Oct 2, 2024 by AchillesDougalis 4.3.0
@AchillesDougalis
To expand epo-ord:DeliveryAgreement class act: for WG discussion it needs to be discussed within the Working Group module: eOrdering eOrdering type: feature request something requested to be implemented in a future release
#693 opened Oct 2, 2024 by AchillesDougalis 4.3.0
@andreea-pasare
Map the new BTs described on Regulation 2023/2884 to ePO concepts. act: for implementation it can be implemented and closed, all is clear aux: alignment alignment between ESPD, eForms and ePO aux: mapping it is related to the TED-SWS mappings project 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
#691 opened Oct 2, 2024 by AchillesDougalis 5.0.0
@AchillesDougalis
Approval notes as metadata
#690 opened Sep 25, 2024 by cristianvasquez
2
Remove epo-con:ContractModificationInformation from core module diagram in ePO 4.2.0 module: eContract eContract module: ePO core ePO core type: bug something implemented incorrectly in a release
#689 opened Sep 24, 2024 by andreea-pasare 4.2.0
@andreea-pasare
2
ProTip! Add no:assignee to see everything that’s not assigned.