-
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
to be removed: Predicates and Attributes of eFulfilment
act: for implementation
it can be implemented and closed, all is clear
module: eFulfilment
eFulfilment
Remodel epo:PlannedProcurementPart
aux: mapping
it is related to the TED-SWS mappings project
module: ePO core
ePO core
Linking roles to PlannedProcurementParts (Mapping of fields it is related to the TED-SWS mappings project
OPT-301-Part-FiscalLegis
, OPT-301-Part-EnvironLegis
, OPT-301-Part-EmployLegis
, OPT-301-Part-TenderReceipt
, OPT-301-Part-TenderEval
, OPT-301-Part-AddInfo
and OPT-301-Part-DocProvider
)
aux: mapping
epo:SubmissionTerm
inheritance is wrong
aux: mapping
Is the property it is related to the TED-SWS mappings project
epo:hasReceivedSubmissionType
still needed? (Re: mapping of eForms field BT-760-LotResult
"Received Submissions Type")
aux: mapping
Mapping of eForms fields alignment between ESPD, eForms and ePO
aux: mapping
it is related to the TED-SWS mappings project
BT-509-Organization-Company
, BT-500-Organization-TouchPoint
and BT-509-Organization-TouchPoint
aux: alignment
epo:ContractLotCompletionInformation
should have relation to epo:LotGroup
also
aux: alignment
Mapping of eForms fields alignment between ESPD, eForms and ePO
aux: mapping
it is related to the TED-SWS mappings project
module: ePO core
ePO core
BT-808-Review
(Review Applicant Identifier) and BT-807-Review
(Review Body Identifier)
aux: alignment
Mapping of eForms field alignment between ESPD, eForms and ePO
aux: mapping
it is related to the TED-SWS mappings project
module: ePO core
ePO core
BT-786-Review
(Review Notice Section Identifier)
aux: alignment
Mapping of eForms field it is related to the TED-SWS mappings project
OPT-050-Part
(Document Status)
aux: mapping
Alignment between eForms and ePO representation of contract modifications
aux: alignment
alignment between ESPD, eForms and ePO
aux: mapping
it is related to the TED-SWS mappings project
module: eContract
eContract
Review the names of all the Classes of the Ontology that have a composite naming.
module: none
no module in particular because the issue is of technical or documentation nature
Add properties on class epo-cat:ItemProperty related to Dimension
act: for implementation
it can be implemented and closed, all is clear
module: eCatalogue
eCatalogue
Add additional properties on class epo-cat:ItemProperty or epo-cat:AbstractItem related to Range Dimension
act: for implementation
it can be implemented and closed, all is clear
module: eCatalogue
eCatalogue
Add properties on class epo-cat:ItemProperty
act: for implementation
it can be implemented and closed, all is clear
module: eCatalogue
eCatalogue
Add predicate epo-cat:hasExtendedSellerItemID
act: for implementation
it can be implemented and closed, all is clear
module: eCatalogue
eCatalogue
Multiple ePO documentation sites
act: for internal discussion
it needs to be discussed within the team
Documentation
module: none
no module in particular because the issue is of technical or documentation nature
at-voc-new:ResponseStatus should be renamed
act: for internal discussion
it needs to be discussed within the team
module: eFulfilment
eFulfilment
Previous Next
ProTip!
Updated in the last three days: updated:>2025-03-22.