Project Information Dissemination Service (PIDS) CORDIS
INTRODUCTION Main objective of PIDS: Collect FP6 Result! 2004 2005 2006 2007 2008 FP4 179 73 0 0 0 FP5 1408 1471 3568 1387 301 FP6 0 0 0 23 8 FP Results per year 4000 3500 3000 2500 FP4 2000 FP5 FP6 1500 1000 500 0 2004 2005 2006 2007 2008
SERVICE OVERVIEW A service that enables Project Coordinators (COs) and Project Officers (POs) to Find information on their projects Store their projects public outputs (news, events, results, documents ) Disseminate these outputs through CORDIS services (CORDIS Wire, results database, CORDIS Library ) and in a longer run, through projects mini sites. Originally: also meant to Update information on projects but this was abandoned
ADVANTAGES OF THE PIDS For collecting deliverables: all public outputs linked to a project (results, news, events, documents for dissemination, publishable summaries) will be stored in a common repository outputs can be added at any time during the life of the project when a CO enters a new output for a project, the PO will immediately receive a notification e-mail to check the deliverable (if needed). For disseminating the deliverables to relevant CORDIS services such as results database, Technology Marketplace CORDIS Wire, CORDIS Library
PIDS LOG IN PAGE From here the Project Coordinator (CO) and the Project Officer (PO) log in to the PIDS with their CORDIS account
PROJECT REGISTRATION (by the Coordinator) The CO must register the project 1. The Project Coordinator browses CORDIS projects DB to find the project 2. Once the project is found it can be registered in the service
PROJECT OVERVIEW preliminary check Once the project is registered the CO gets an overview with pre-populated fields; others should be completed. Once the CO submits to PO, the PO receives an e-mail notification
PROJECT OFFICER S HOMEPAGE 1. The PO logs in and gets an overview of the projects already submitted in PIDS that (s)he is concerned with. 2. The PO clicks on the reference of a newly registered project to view it.
PO PROJECT VALIDATION The PO gets an overview of the information preliminary validated by the CO. (S)he can edit his/her contact details and validate. Once validated by the PO, the CO receives an e-mail notification
PROJECT COORDINATOR S HOMEPAGE The project coordinator's homepage shows the projects already submitted to the PO (validated or not) From that table, new results can be added; or the current ones edited
PROJECT COORDINATOR S PROJECT PAGE In this screen, the CO: -can add new Results 4 types: results, news, events and documents - can see in the table the results that have already been validated or are to be validated
ADDING A RESULT When adding a new Result, the CO completes a form with different parts: 1- the heading: project reference, acronym, title, status of PO approval 2- a part common to all types of Results («output type») 3- a part specific to each type of Result 4- a part common to all types of Reults («contact persons for information») When all steps are completed, the result can be submitted. A notification e-mail is sent to the PO for validation (if requested).
PROJECT OFFICER S PROJECT PAGE The PO can download/ view/ approve the project Result (if required). When the Result has been approved (if required), the dissemination phase starts.
DISSEMINATION PHASE During the collection phase, COs have entered in the PIDS different types of outputs (news, events, results, documents ), that were submitted for the approval of their PO. Once the approval is given, the outputs can be disseminated.
DISSEMINATION PHASE News Events Exploitable results Documents Multimedia After quality control by the CORDIS team, each output is sent from PIDS to its relevant repository (database). Once the outputs have been disseminated to the repositories, they are searchable individually through the traditional CORDIS search interfaces.
FUTURE CONTENT AGGREGATION: Project Mini Site Mini-site concept: Each project registered in the PIDS will have its own public project mini-site on CORDIS. On each project mini-site, information on the project itself (project overview) and all its public deliverables (news, events, results, documents ) will be available. Prerequisite: The project s outputs must have been successfully disseminated to the relevant CORDIS databases before the aggregation process can start. Aggregation: The content aggregation is fully automated by means of FEPs (Filtered Entry Points): The mini-site is composed of dynamic content retrieved from the CORDIS databases. The project mini-site does not require any direct human interaction for executing content updates. Owing to this automation, all projects mini sites will have a standardized lay out. In the future, when CMS 2 is implemented, direct interaction of POs and COs will be possible if requested.
CONTENT AGGREGATION: the Project Mini Site Standard header Standard footer Restricted area
Project Mini Site
CONCLUSION PIDS makes it easier and faster, for COs and POs, to collect FP6 project results and disseminate them.