Mapping CORDIS projects to SDGs
Participants will analyse how EU-funded research contributes to the Sustainable Development Goals (SDGs).
Map CORDIS project data to the SDGs taxonomy available in EU Vocabularies. The aim is not only to assign one or more SDGs to each project, but also to explain the reasoning behind and present the results in a clear and reusable way.
CORDIS – mapping EU-funded research projects to the Sustainable Development Goals
CORDIS provides information on EU-funded research and innovation projects, including project objectives, descriptions, keywords, EuroSciVoc categories, deliverables and other project-related content.
The United Nations Sustainable Development Goals provide a widely used framework for understanding societal, environmental and economic impact. EU Vocabularies provides access to a structured SDG taxonomy, including more specific narrower concepts. The challenge is to use this taxonomy to identify which SDGs are addressed by CORDIS projects and, where possible, to map them to the most precise relevant concepts.
Participants are invited to design a method for linking CORDIS projects to SDG concepts. A project may contribute to more than one SDG. The mapping must therefore support multiple labels and must include an explanation of why each label was assigned.
The solution may use any relevant CORDIS project fields, such as:
- EuroSciVoc categories;
- project keywords;
- objective (coming from the eGrant agreement);
- project description (editorial content);
- project deliverables;
- other available project-related content.
Participants should not only produce a mapping table. They should also analyse and present the results, for example by showing which SDGs are most frequently linked to CORDIS projects, which are less represented, how SDG relevance varies by programme, topic, country, organisation type, project duration or scientific field, or where the mapping is uncertain.
As an optional extension, participants may also compare the SDG mapping with the current European Commission Strategic priorities authority table, where relevant.
Objective
Create a transparent and explainable method to map CORDIS projects to SDG concepts, using the EU Vocabularies SDG taxonomy as the reference framework.
The best submissions will combine sound data analysis, good use of controlled vocabularies, clear reasoning and effective presentation.
Expected output
Participants should submit:
- A notebook explaining the methodology, data preparation, mapping logic and results.
- A project-to-SDG mapping table, including:
- CORDIS project identifier;
- project title;
- assigned SDG concept(s);
- narrower SDG concept(s), where applicable;
- confidence score or confidence level;
- short explanation or evidence for each assignment;
- source field(s) used for the assignment.
- Visualisations showing the main findings.
- A short discussion of limitations, uncertain cases and possible improvements.
- A working web-based prototype.
- A description document on what you did and why your solution is the best.
Data
Participants are encouraged to use the datasets made available through data.europa.eu, although equivalent information may also be obtained directly from CORDIS.
Relevant fields may include, but are not limited to:
- project acronym;
- project title;
- objective;
- project description;
- EuroSciVoc category;
- keywords;
- programme;
- topic;
- start and end dates;
- participating organisations;
- countries;
- deliverables and other project outputs, where available.
The reference taxonomy is the Sustainable Development Goals taxonomy in EU Vocabularies:
Participants should use the taxonomy structure and prefer the most precise relevant concept. Where a narrower concept is available and applicable, it should be used instead of assigning only the top-level SDG.
Optional reference authority table:
Task
For each selected CORDIS project, identify one or more relevant SDG concepts.
A good solution should:
- support multiple SDG assignments per project;
- use narrower SDG concepts where possible;
- explain the reasoning behind each assignment;
- distinguish strong, weak and uncertain matches;
- avoid assigning SDGs only on the basis of isolated keywords;
- show how the method deals with ambiguous or cross-cutting projects;
- provide reusable outputs.
Methodological guidance
- Participants are free to choose their own approach for linking CORDIS projects to SDG concepts.
- The proposed method should be transparent, explainable and reproducible. Participants should clearly describe how SDG assignments were generated, how confidence was assessed and how uncertain or ambiguous cases were handled.
- If artificial intelligence, machine learning or other automated methods are used, the solution must explain how the method works and how the results were validated. Black-box mappings without explanation will not be considered sufficient.
- Participants must not process personal data.
- Participants should document any external datasets, tools or models used.
Visualisation
Participants are encouraged to present their findings through appropriate visualisations that help explain the mapping results, highlight patterns in the data and communicate uncertainties where relevant.
Evaluation criteria, submission format and indicative timeline: please see under Rules.
Awards
The best submissions will receive gold, silver and bronze certificate recognition on the competition platform.
Key terms
| Term | Definition |
| CORDIS | The Community Research and Development Information Service (CORDIS) is the European Commission’s primary source of information on EU-funded research and innovation projects and their results. |
| EDP | The European Data Portal is a service that provides access to open data published by public administrations across Europe. |
| EuroSciVoc | The multilingual taxonomy of scientific fields used by the Publications Office of the European Union to classify research topics. |
| EU Vocabularies | A collection of controlled vocabularies and authority tables maintained by the Publications Office of the European Union. |
| Multi-label classification | A classification approach where a project may be assigned to multiple concepts simultaneously. |
| Narrower concept | A more specific concept within a hierarchical taxonomy. Participants should prefer the most precise applicable concept whenever possible. |
| Project deliverable | A project output submitted during the lifetime of a project. Deliverables may provide additional evidence for classification. |
| Project description | Editorial content prepared for CORDIS, providing a more accessible description of the project and its context. |
| Project objective | The project summary extracted from the eGrant agreement and published in CORDIS. It describes the aims and expected outcomes of the project. |
| SDG | Sustainable Development Goal. One of the goals and targets defined by the United Nations 2030 Agenda for Sustainable Development. |
| SDG taxonomy | The EU Vocabularies concept scheme representing the Sustainable Development Goals and their more specific concepts. This is the reference taxonomy for the challenge. |
| Strategic priority | Controlled vocabulary describing the strategic priorities of the European Commission. Participants may optionally use it for comparison with SDG mappings. |
Evaluation criteria, submission format and indicative timeline
Evaluation criteria
Submissions will be evaluated according to the following criteria:
1. Correct use of the SDG taxonomy
The solution uses the EU Vocabularies SDG taxonomy correctly and assigns the most precise relevant concepts where possible.
2. Quality of the mapping
The assigned SDGs are relevant, well justified and not based on superficial keyword matching only.
3. Explainability
The notebook clearly explains why a project was linked to a given SDG. The reasoning is understandable for non-technical users.
4. Reusability
The method and output can be reused or adapted by CORDIS or EDP after the challenge.
5. Data handling
The solution uses CORDIS data appropriately, documents preprocessing steps and handles missing or inconsistent data transparently.
6. Visualisation and communication
The results are presented clearly through tables, charts or other visualisations.
7. Awareness of limitations
The submission identifies uncertain cases, possible biases and limitations of the method.
8. A working web-based prototype
This prototype helps the work of the evaluators.
9. A description document on what you did and why your solution is the best
A short summary of why you think your solution should be awarded.
Submission format
Each submission should include:
- a notebook;
- a mapping table in CSV or Excel format;
- any supporting files needed to reproduce the results;
- a short summary of the approach and main findings;
- a working web-based prototype;
- a description document explaining why your solution is the best.
Indicative timeline
- Launch of the challenge: 1 August 2026
- Q&A period (extended): until 21 September 2026
- Submission deadline: 30 September 2026, 23:59 CEST (UTC+2)
- Evaluation period: 1–30 October 2026
- Results announced: 4 November 2026
Q&A
For more information check Overview and Rules pages.
We use this place to display questions and answers (Q&A) arrived from different users. We would like to share the same understanding.
Q1: Eligibility: Is participation open to anyone, or is it restricted to a particular group, e.g current or former CORDIS-funded researchers.
A1: Participation is open to anyone. It is not restricted to current or former participants in CORDIS-funded projects.
Q2: Dataset scope: The brief references CORDIS data generally without specifying a particular framework programme. Is there a preferred or expected dataset to use — for example, Horizon Europe (2021–2027) only — or is any CORDIS programme/dataset acceptable, including earlier ones such as H2020 or FP7?
A2: The challenge is not restricted to a particular framework programme. Participants may use CORDIS data from Horizon Europe, Horizon 2020, FP7 or other framework programmes covered by CORDIS. They may focus on one programme or use data from several programmes, depending on their chosen approach.
Q3: Submission: Could you clarify how and where the final submission should be delivered (e.g. an upload portal, email, a GitHub repository), and whether there are any strict format or file-size limits?
A3: The final submission should be uploaded via the competition platform by 30 September 2026, 23:59 CEST (UTC+2). It should include the items listed under ‘Submission format’ in the Rules. Format limited only for the mapping table: CSV or Excel. No size limit.
Q4: AI/LLM tools: The brief notes that participants should document any external datasets, tools or models used. Could you confirm whether the use of commercial LLM APIs (for example, to help generate explanations for SDG assignments) is acceptable, or whether fully open/local models are expected given the emphasis on reproducibility?
A4: The current text allows participants to choose their own approach and explicitly refers to the use of AI, machine learning and other automated methods, provided that the method is transparent, explainable and reproducible. It also requires participants to document any external datasets, tools or models used. It does not explicitly state whether commercial LLM APIs are acceptable – but it would make the reproducibility difficult or even impossible.
Q5: Taxonomy depth. The EU Vocabularies SDG taxonomy (http://data.europa.eu/sdg) includes 17 goals, 169 targets, and several hundred indicator/series concepts. When the brief asks for “the most precise relevant concept” and “narrower SDG concept(s)”, should mappings stop at target level, or are indicator-level concepts also expected?
A5: Participants should use the most precise relevant concept available in the EU Vocabularies SDG taxonomy. The mapping does not have to stop at target level. Indicator-level or other narrower concepts may also be used where they are relevant and can be meaningfully supported by the CORDIS project information. However, participants are not expected to assign a narrower concept simply because one exists: the level of precision should be justified by the available evidence.
Q6: Corpus cut-off. CORDIS dumps are updated monthly. Is there a preferred snapshot (for example a stated dump date) so that mappings remain comparable across participants?
A6: There is no mandatory CORDIS snapshot or cut-off date for the challenge. As CORDIS data are updated regularly, participants should clearly document the dataset(s) used, including the date of retrieval or snapshot where applicable, so that their results can be understood and reproduced. Participants are not expected to use exactly the same snapshot.
Q7: Licence for reuse. The evaluation criteria mention reusability by CORDIS or the European Data Portal. Is a specific open licence preferred for the mapping table, notebook and prototype (for example CC-BY or EUPL)?
A7: No specific open licence is required for submissions. However, as reusability is one of the evaluation criteria, participants are encouraged to use an appropriate open licence and to state clearly the licence applying to their submitted code, data and documentation. Any third-party data, tools, libraries or other resources used must, of course, be used in accordance with their applicable licences and conditions.
Q8: Prototype hosting. The Rules require a working web-based prototype. Should it be publicly hosted at submission time (URL), or is it sufficient to provide code that the evaluators can run locally?
A8: The working web-based prototype should be accessible to the evaluators at submission time, preferably through a URL included in the submission. Providing source code alone that requires the evaluators to install dependencies and run the prototype locally would not fulfil the purpose of the requested working web-based prototype. Supporting source code and instructions may additionally be included to facilitate reproducibility.
Q9: Can teams participate in the competition, or are submissions limited to individuals?
A9: Teams are welcome to participate in the competition. However, due to the format of the certificates, only one name can appear on a certificate. Teams should therefore indicate whether, in the event of ranking among the top three submissions, they would like the certificate to be issued in the name of one team member or under their shared team name.
Q10: Terms, intellectual property and publication. Beyond the evaluation criteria published on the challenge page, is there a full terms & conditions document for the competition? Specifically: who holds the rights to submitted materials, under what licence may CORDIS or the European Data Portal reuse the method and mapping, and will submissions (or winning submissions) be published publicly after the challenge?
A10: Participants retain full ownership of their submissions and all associated rights. The winning submissions themself will not be published. Only the individual participants or teams behind the winning applications will be featured on the European Data Portal in order to promote the winners.
Q11: Use of large language models. The challenge page notes that commercial LLM APIs may make reproducibility difficult. Could you clarify whether: (a) a method built on a commercial LLM API is acceptable if fully documented (model, version, prompts, parameters), and (b) whether a method using an open-weight model (publicly downloadable weights, version-pinned, reproducible on any infrastructure) accessed through a hosted inference provider satisfies your reproducibility expectations?
A11: All LLMs, whether open or closed, may be used for the challenge. The key requirement is not the type of LLM used, but that the methodology is sufficiently transparent and reproducible.
For a commercial LLM API, participants should document the model, version, prompts and parameters used. However, it should be noted that full reproducibility may have inherent limitations, as the provider may update or modify the model or service, and the same model/version may no longer be available later. Even with identical prompts and parameters, the results may therefore not always be reliably reproducible.
An open-weight model accessed through a hosted inference provider is equally acceptable. Participants should specify the exact model and version used and document the methodology and relevant settings in sufficient detail to allow the approach to be reproduced.