Search results

ResultNotice announcesNoticeAwardInformation however ContractModificationNotice refersToNoticeAwardInformation

module: eNoticeeNoticeeNotice

type: questionsomething needs clarified, refined or decidedsomething needs clarified, refined or decided

Status: Open.

#799 In OP-TED/ePO;

· muricna opened on Jun 20, 2025

·  

6.0.0

Consider moving Tender concept to eSubmission module

Status: Open.

Feature

#798 In OP-TED/ePO;

· andreea-pasare opened on Jun 19, 2025

·  

6.0.0

The ESPD should become independent of the ESPD request.

module: eSubmissioneSubmissioneSubmission

Status: Open.

Task

#783 In OP-TED/ePO;

· AchillesDougalis opened on Apr 16, 2025

·  

6.0.0

Moving properties epo:isWithdrawn, epo:hasWithdrawalDate, epo:hasWithdrawalReason and epo:hasReviewRequestFee from epo:ReviewRequest toepo:ReviewDecision

aux: alignmentalignment between ESPD, eForms and ePOalignment between ESPD, eForms and ePO

aux: mappingit is related to the TED-SWS mappings projectit is related to the TED-SWS mappings project

Status: Open.

Bug

#782 In OP-TED/ePO;

· csnyulas opened on Apr 16, 2025

·  

5.0.0

Add concepts related to epo:Certificate.

module: eFulfilmenteFulfilmenteFulfilment

Status: Open.

Feature

#780 In OP-TED/ePO;

· AchillesDougalis opened on Apr 15, 2025

·  

5.3.0

Add a link to a document describing the damage of the package

module: eFulfilmenteFulfilmenteFulfilment

Status: Open.

Feature

#774 In OP-TED/ePO;

· andreea-pasare opened on Apr 9, 2025

·  

5.3.0

Remodel epo-not:CallForExpressionOfInterest to ParticipationNotice

module: eNoticeeNoticeeNotice

Status: Open.

Feature

#772 In OP-TED/ePO;

· AchillesDougalis opened on Apr 7, 2025

·  

6.0.0

Property overriding investigation and proposal for modeling approach

Status: Open.

#737 In OP-TED/ePO;

· gkostkowski opened on Jan 25, 2025

·  

6.0.0

Aligning ePO Metadata with CDM and Redefining epo:Document Class hierarchy

module: ePO coreePO coreePO core

type: feature requestsomething requested to be implemented in a future releasesomething requested to be implemented in a future release

type: use caseUse Case (User story)Use Case (User story)

Status: Open.

#735 In OP-TED/ePO;

· costezki opened on Jan 21, 2025

·  

6.0.0

Investigate if predicates for specific roles are needed.

act: for implementationit can be implemented and closed, all is clearit can be implemented and closed, all is clear

module: noneno module in particular because the issue is of technical or documentation natureno module in particular because the issue is of technical or documentation nature

type: feature requestsomething requested to be implemented in a future releasesomething requested to be implemented in a future release

Status: Open.

#733 In OP-TED/ePO;

· AchillesDougalis opened on Jan 7, 2025

·  

6.0.0

Should the different prefixes of the Ontology be kept or not?

act: for internal discussionit needs to be discussed within the teamit needs to be discussed within the team

module: noneno module in particular because the issue is of technical or documentation natureno module in particular because the issue is of technical or documentation nature

type: feature requestsomething requested to be implemented in a future releasesomething requested to be implemented in a future release

Status: Open.

#728 In OP-TED/ePO;

· AchillesDougalis opened on Dec 11, 2024

·  

6.0.0

Review all the roles of the Ontology to see if they belong to the correct module

act: for internal discussionit needs to be discussed within the teamit needs to be discussed within the team

module: noneno module in particular because the issue is of technical or documentation natureno module in particular because the issue is of technical or documentation nature

type: feature requestsomething requested to be implemented in a future releasesomething requested to be implemented in a future release

Status: Open.

#727 In OP-TED/ePO;

· AchillesDougalis opened on Dec 11, 2024

·  

6.0.0