Home / FAQ / Data. What kind of data is available in keep.eu?

Data. What kind of data is available in keep.eu?

Keep.eu focuses on a specific group of programmes, projects and partners. All of these programmes and projects share the fact that they are fully or partially funded by the European Union and/or its Member States, and all of them involve participants (partners) from at least two different countries. These countries can either be part of the European Union, or they can be States or territories outside of the Union (such as pre-accession countries, countries neighbouring the European Union, among others). Keep.eu also contains data on projects developed within the scope of the European Union macro-regional strategies.

For ease of search, keep.eu divides the programmes it features (and, consequently, their projects) into the types described in the FAQ entry on the types of programmes.

The keep.eu database contains four tables:

  • Programmes of the types described in the FAQ entry on the types of programmes (starting in the 2000-2006 period), with fields covering each of the programmes’ name, strand, programming period, number of projects, and web address (URL) (2000-2006 and 2007-2013 periods), plus, in the case with 2014-2020 programmes, many more fields in connection with the programmes goals, achivements and indicators. Specific programme data is in Search for programmes (one page per programme).
  • Projects (approved and contracted projects within the scope of the above programmes), which fields are the projects’ acronym, name (original language and English), description, results (full text), start and end dates, budget, co-financing by European fund and web address (URL).
  • Partners (rolling out the above-mentioned projects), with the following fields: Project partners’ name, address, NUTS3 code, contact details. Partners in any project are further split into lead partners and regular project partners (the field in the database is called project type)
  • Calls (which led to the approval and signature of the above-mentioned projects), with the following fields: Serial number of call or direct award, start date of call, end date of call, budget of call

The tables below shows the data contained in each of the keep.eu database tables Projects, Partners and Calls considering 2014-2020 (data from previous periods contains less fields per project and partner and no information regarding calls).

2014-2020 project fields

Below each field are its explanations, including references to the HIT (Harmonised Implementation Tools).

Period

‘2000-2006’ OR ‘2007-2013’ OR ‘2014-2020’.

Programme

Name of the programme.

Project acronym

Given by the programme. Each acronym needs to be unique per programme / period but can be repeated across different programmes.

Call serial number

This field links each project to its call.

Project name in English

If English is the original name, repeat here.

Project name in language 2 to n

Name of the project in languages other than English.

Description in English

Short (1000-1500 characters) overview of the project (in the style of a press release), description and objectives, including:

  • The common challenge of the programme area you are jointly tackling in your project;
  • The overall objective of the project and the expected change your project will make to the current situation;
  • The main outputs you will produce and who will benefit from them;
  • The approach you plan to take and why is cross-border approach needed;
  • What is new/original about it.

If using HIT, refer to INTERACT_Harmonised_Tool_Project_Selection_ Application_Form_CBC, field ‘A.2 Project summary’, and INTERACT_Harmonised_Tool_Project_Selection_ Application_Form_TN, field ‘A.2 Project summary’. One specific ‘Project description’ field per language, this being the English field.

What are the project results and how do they link to the programme result indicator? Specify one or more project result and describe their contribution to the programme result indicator. If using HIT, refer to INTERACT_Harmonised_Tool_Project_ Selection_Application_Form_CBC and / or INTERACT_Harmonised_Tool_Project_Selection_ Application_Form_TN (sections ‘C.2.1 Project objectives, expected results and main outputs’). One specific ‘Project expected results’ field per language, this being the English field.

Description in language 2 to n

Short (1000-1500 characters) overview of the project (in the style of a press release), description and objectives, including:

  • The common challenge of the programme area you are jointly tackling in your project;
  • The overall objective of the project and the expected change your project will make to the current situation;
  • The main outputs you will produce and who will benefit from them;
  • The approach you plan to take and why is cross-border approach needed;
  • What is new/original about it.

If using HIT, refer to INTERACT_Harmonised_Tool_Project_Selection_ Application_Form_CBC, field ‘A.2 Project summary’, and INTERACT_Harmonised_Tool_Project_Selection_ Application_Form_TN, field ‘A.2 Project summary’. One specific ‘Project description’ field per language.

Expected results in English

What are the project results and how do they link to the programme result indicator? Specify one or more project result and describe their contribution to the programme result indicator. If using HIT, refer to INTERACT_Harmonised_Tool_Project_ Selection_Application_Form_CBC and / or INTERACT_Harmonised_Tool_Project_Selection_ Application_Form_TN (sections ‘C.2.1 Project objectives, expected results and main outputs’). One specific ‘Project expected results’ field per language , this being the English field.

Expected results in language 2 to n

What are the project results and how do they link to the programme result indicator? Specify one or more project result and describe their contribution to the programme result indicator. If using HIT, refer to INTERACT_Harmonised_Tool_Project_ Selection_Application_Form_CBC and / or INTERACT_Harmonised_Tool_Project_Selection_ Application_Form_TN (sections ‘C.2.1 Project objectives, expected results and main outputs’). One specific ‘Project expected results’ field per language.

Achievements in English

After the end of the project, highlight of the main achievements in a press release style, interesting and understandable for non-specialists (around 1500 words). Even though this is meant to be filled out only after the end of the project, at the time this table was produced (2014.11.10), the tools of the HIT ‘Project Final Report’ were still in development but the tools ‘INTERACT_Harmonised_Tool_Project_Implementation_Project _Progress_Report_CBC’ and ‘INTERACT_Harmonised_Tool_Project_Implementation_Project _Progress_Report_TN’ were already in place. The corresponding field therein is ‘A.2 Highlights of main achievements’. One specific ‘Project achievements’ field per language, this being the English field.

Achievements in language 2 to n

After the end of the project, highlight of the main achievements in a press release style, interesting and understandable for non-specialists (around 1500 words). Even though this is meant to be filled out only after the end of the project, at the time this table was produced (2014.11.10), the tools of the HIT ‘Project Final Report’ were still in development but the tools ‘INTERACT_Harmonised_Tool_Project_Implementation_Project _Progress_Report_CBC’ and ‘INTERACT_Harmonised_Tool_Project_Implementation_Project _Progress_Report_TN’ were already in place. The corresponding field therein is ‘A.2 Highlights of main achievements’. One specific ‘Project achievements’ field per language.

Expected outputs in English

Description of the project main outputs (around 500 words). In the INTERACT_Harmonised_Tool_Project_Selection_ Application_Form_CBC and INTERACT_Harmonised_Tool_Project_Selection_Application_ Form_TN, refer to section C.5 Work plan per work packages, field of table WP 3 – 7, field ‘Describe your project main output’. One specific ‘Expected outputs’ field per language, this being the English field.

Expected outputs in language 2 to n

Description of the project main outputs (around 500 words). In the INTERACT_Harmonised_Tool_Project_Selection_ Application_Form_CBC and INTERACT_Harmonised_Tool_Project_Selection_Application_ Form_TN, refer to section C.5 Work plan per work packages, field of table WP 3 – 7, field ‘Describe your project main output’. One specific ‘Expected outputs’ field per language.

Delivered outputs in English

Description of the project main output (around 500 words) as in the last progress report form. One specific ‘Delivered outputs’ field per language, this being the English field.

Delivered outputs in language 2 to n

Description of the project main output (around 500 words) as in the last progress report form. One specific ‘Delivered outputs’ field per language.

Project’s total budget / expenditure

Total eligible budget indicates the total budget of the project to be co-financed from the programme, based on the approved Application Form. In the INTERACT_Harmonised_Tool_Project_Selection_Budget_ Application_Form_TN_and_CBC.xlsx, refer to spreadsheet ‘A.3 Summary”, cell I12 (‘TOTAL ELIGIBLE BUDGET’). At the end of the project, total eligible expenditure actually incurred during the project implmentation, based on accumulated data provided in the last Progress Report. In the INTERACT_Harmonised_Tool_Project_Implementation_ Finance_Progress_Reports.xlsx, refer to spreadsheet ‘PART B. Project Finance Report’, cell E21 (TOTAL ELIGIBLE EXPENDITURE reported so far).

Project’s EU funding

European Union funding means all EU funds committed by the programme to the project, based on the last approved Application Form. In the INTERACT_Harmonised_Tool_Project_Selection_Budget_ Application_Form_TN_and_CBC.xlsx, refer to spreadsheet ‘A.3 Summary’, cell B10 (Amount of total EU Funds’). At the end of the project, the amount of EU funds allocated to the project, based on accumulated data provided in the last Progress Report. In the INTERACT_Harmonised_Tool_Project_Implementation_ Finance_Progress_Reports.xlsx, refer to spreadsheet ‘PART B. Project Finance Report’, calculate E11 minus E16.

ERDF contribution

In the INTERACT_Harmonised_Tool_Project_Selection_ Budget_Application_Form_TN_and_CBC.xlsx, refer to spreadsheet ‘A.3 Summary’, cell B7 (‘ERDF’). At the end of the project, the amount of EU funds allocated to the project, based on accumulated data provided in the last Progress Report. In the INTERACT_Harmonised_Tool_Project_Implementation_ Finance_Progress_Reports.xls, refer to spreadsheet ‘PART B. Partner Finance Report’, tables ‘B.3 Project expenditure per co-financing source (fund) – breakdown per partner’, tables ‘Programme co-financing – ERDF (if applicable)’, cell E43.

ENPI/ENI contribution

In the INTERACT_Harmonised_Tool_Project_Selection_ Budget_Application_Form_TN_and_CBC.xlsx, refer to spreadsheet ‘A.3 Summary’, cell B9 (‘ENI’). At the end of the project, the amount of EU funds allocated to the project, based on accumulated data provided in the last Progress Report. In the INTERACT_Harmonised_Tool_Project_Implementation_ Finance_Progress_Reports.xls, refer to spreadsheet ‘PART B. Partner Finance Report’, tables ‘B.3 Project expenditure per co-financing source (fund) – breakdown per partner’, tables ‘Programme co-financing – ENI (if applicable)’, cell E68.

IPA II contribution

In the INTERACT_Harmonised_Tool_Project_Selection_ Budget_Application_Form_TN_and_CBC.xlsx, refer to spreadsheet ‘A.3 Summary’, cell B8 (‘IPA II’). At the end of the project, the amount of EU funds allocated to the project, based on accumulated data provided in the last Progress Report. In the INTERACT_Harmonised_Tool_Project_Implementation_ Finance_Progress_Reports.xls, refer to spreadsheet ‘PART B. Partner Finance Report’, tables ‘B.3 Project expenditure per co-financing source (fund) – breakdown per partner’, tables ‘Programme co-financing – IPA II (if applicable)’, cell E56.

Third country contribution

Any contribution, ERDF-equivalent or not, from countries other than the Member States of the European Union.

Co-financing sources

And EU fund (either ERDF, ENI, IPA or Other).

Website

URL of the project website.

Themes 1, 2 and 3

Please refer to the FAQ entry Themes. What are they? How are they assigned to projects?

Specific objective (2014-2020 Interreg and Interreg-IPA CBC only)

As required by the programmes at the time of the application. In the INTERACT_Harmonised_Tool_Project_Selection_ Application_Form_CBC and INTERACT_Harmonised_Tool_Project_Selection_Application_ Form_TN, refer to section C.2.1 Project objectives, expected results and main outputs, table column ‘Programme priority specific objective’.

Thematic Objective (2014-2020 Interreg only)

Self filled-out field, from field ‘Contribution to the Programme’s specific objective.

Investment Priority (2014-2020 Interreg only)

Self filled-out field, from field ‘Contribution to the Programme’s specific objective’.

Thematic Priority (2014-2020 Interreg-IPA CBC only)

Self filled-out field, from field ‘Contribution to the Programme’s specific objective’.

Thematic Objective (ENI CBC only)

As required by the programmes at the time of the application.

Project start

Start date as in the application form and updated in the programme’s monitoring system.

Project end

End date as in the application form and updated in the programme’s monitoring system.

Priority Area (EU macro-regional strategy)

Priority area of the European Union macro-regional strategy enclosing the project.

Degree of compliance (EU macro-regional strategy)

Degree of compliance of the European Union macro-regional strategy enclosing the project.

Enclosed by EU macro-regional strategy

Name of the strategy or no name. In the INTERACT_Harmonised_Tool_Project_Selection_ Application_Form_CBC and INTERACT_Harmonised_Tool_Project_Selection_Application _Form_TN, refer to ‘C.3.1 How does the project contribute to the wider strategies and policies?’ (only the strategy title).

2014-2020 partner fields

Below each field are its explanations, including references to the HIT (Harmonised Implementation Tools).

Programme

Name of the programme.

Project acronym

This field links each partner to its project.

Organisation in English

Official translation, if existing.

Organisation in language 2 to n

In case the original language is English, repeat name above.

Lead partner

Lead Partner’ OR ‘Standard partner’. (Keep.eu does not contain associated partners, unless the programmes at hand consider that they should feature among a project’s partner set.)

Department

Name of the department /unit / division in English if possible.

Street

Name of town in English or other language (organisation’s main address, as per cell B34).

Postal code

Postal code, no pre-format.

Town

Name of town in English or other language (organisation’s main address, as per cell B34).

Country

Countries’ English short names, not the formal ones, as defined in the United Nations Terminology Bulletin ‘Country Names’, or Country and Region Codes for Statistical Use of the UN Statistics Division (ISO uses them and is for us the source, in https://www.iso.org/obp/ui/#search). For example, the notation that keep.eu uses is ‘Portugal’, not ‘Portuguese Republic’.

Country code

Self filled-out field, from Country.

NUTS 1 (or equivalent)

Self filled-out field, from Town and Country.

NUTS 2 (or equivalent)

Self filled-out field, from Town and Country.

NUTS 3 (or equivalent)

Self filled-out field, from Town and Country.

Latitude

Self filled-out field, from Town and Country.

Longitude

Self filled-out field, from Town and Country.

Website

URL of the organisation.

Legal status

Public entity OR Private entity. In the INTERACT_Harmonised_Tool_Project_ Selection_Application_Form_CBC and INTERACT_Harmonised_Tool_Project_Selection_Application _Form_TN, refer to section B.1 ‘Project Partners’, field ‘Legal status’.

Partner’s eligible budget / expenditure

Partner eligible budget indicates the budget of an individual partner to be co-financed from the programme, based on the last approved Application Form. Partner eligible expenditure indicates the expenditure of an individual partner actually incurred during the project implementation, based on accumulated data provided in the last Progress Report. In the INTERACT_Harmonised_Tool_Project_Selection_ Budget_Application_Form_TN_and_CBC.xlsx, refer to spreadsheet ‘PART D. Project budget’, table ‘D.2 Project budget – overview per partner/ per budget line’, column K (TOTAL ELIGIBLE BUDGET per Partner)’. In the INTERACT_Harmonised_Tool_Project_ Implementation_Finance_Progress_Reports.xls, refer to spreadsheet ‘PART B. Partner Finance Report’, cell E21 (PARTNER TOTAL ELIGIBLE EXPENDITURE reported so far).

ERDF contribution

In the INTERACT_Harmonised_Tool_Project_Selection_ Budget_Application_Form_TN_and_CBC.xlsx, refer to spreadsheet ‘PART D. Project budget’, table ‘D.1 Project budget per co-financing source (fund) – breakdown per partner / Programme co-financing – ERDF (if applicable)’, column C (ERDF). In the INTERACT_Harmonised_Tool_Project_ Implementation_Finance_Progress_Reports.xls, refer to spreadsheet ‘PART B. Partner Finance Report’, tables ‘B.3 Project expenditure per co-financing source (fund) – breakdown per partner’, tables ‘Programme co-financing – ERDF (if applicable)’, column E.

ENPI / ENI contribution

In the INTERACT_Harmonised_Tool_Project_Selection_ Budget_Application_Form_TN_and_CBC.xlsx, refer to spreadsheet ‘PART D. Project budget’, table ‘D.1 Project budget per co-financing source (fund) – breakdown per partner / Programme co-financing – ENI (if applicable)’, column C (ERDF). In the INTERACT_Harmonised_Tool_Project_ Implementation_Finance_Progress_Reports.xls, refer to spreadsheet ‘PART B. Partner Finance Report’, tables ‘B.3 Project expenditure per co-financing source (fund) – breakdown per partner’, tables ‘Programme co-financing – ENI (if applicable)’, column E.

IPA II contribution

In the INTERACT_Harmonised_Tool_Project_Selection_ Budget_Application_Form_TN_and_CBC.xlsx, refer to spreadsheet ‘PART D. Project budget’, table ‘D.1 Project budget per co-financing source (fund) – breakdown per partner / Programme co-financing – IPA II (if applicable)’, column C (ERDF). In the INTERACT_Harmonised_Tool_Project_ Implementation_Finance_Progress_Reports.xls, refer to spreadsheet ‘PART B. Partner Finance Report’, tables ‘B.3 Project expenditure per co-financing source (fund) – breakdown per partner’, tables ‘Programme co-financing – IPA II (if applicable)’, column E.

Third country contribution

The part, from the partner’s budget, covered by third-country funds.

2014-2020 call fields

Programme

Name of the programme.

Call serial number

Number.

Call start date

Date field.

Call end date

Date field.

Budget of call

Budget in EUR.