-
Notifications
You must be signed in to change notification settings - Fork 18
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
Label
Projects
Milestones
Assignee
Sort
Issues list
Problems mapping "Documents Official Language" and "Documents Unofficial Language" fields (it is related to the TED-SWS mappings project
type: feature request
something requested to be implemented in a future release
BT-708-Part
, BT-737-Part
, BT-708-Lot
, BT-737-Lot
)
aux: mapping
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
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
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
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
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
Unmappable eForms fields in PIN, CEI and T02 notice subtypes
aux: mapping
it is related to the TED-SWS mappings project
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
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
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
Inconistencies with concepts related to taxes, allowances and charges
module: eCatalogue
eCatalogue
module: eOrdering
eOrdering
type: bug
something implemented incorrectly in a release
Notice refersToProcedure to be removed
aux: mapping
it is related to the TED-SWS mappings project
module: ePO core
ePO core
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
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
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
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
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
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
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
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
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
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
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
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
Previous Next
ProTip!
Exclude everything labeled
bug
with -label:bug.