3. Project Identifier (MA)¶
3.1. DC Field¶
dc:relation
3.2. Usage¶
Mandatory when applicable
3.3. Usage Instruction¶
An authoritative list of projects is exposed by the OpenAIRE API, and available for all repository managers. Values include the project name and project ID. The projectID equals the Grant Agreement identifier, and is defined by the info:eu-repo namespace term grantAgreement.
The syntax is:
info:eu-repo/grantAgreement/Funder/FundingProgram/ProjectID/
[Jurisdiction]/[ProjectName]/[ProjectAcronym]
where:
Funderrefers to the funding organization (e.g.,ECfor European Commission,WTfor Wellcome Trust)FundingProgrammerefers to a specific programme (e.g.,FP7for Framework Programme Seven,H2020for Horizon 2020,HEfor Horizon Europe )ProjectIDrefers to a unique identifier in the scope of the funder (and maybe the programme), e.g. a grant agreement number.Jurisdictionrefers to the authority granted to a formally constituted legal body (e.g.EUfor European Union)ProjectNamecontains the full name of the projectProjectAcronymcontains the project’s acronym.
For OpenAIRE compatibility, the elements in square brackets are optional. The three-part namespace is mandatory when applicable (info:eu-repo/grantAgreement/Funder/FundingProgram/ProjectID), while the six-parts namespace is recommended.
When omitting fields in the extended version, the number of fields must be preserved by using /. A correct example for omitting the the ProjectName field would therefore look like this: EC/FP7/12345/EU//OpenAIREplus
If any of the field values contains a forward slash (/), it needs to be escaped using URL encoding (%2F). For instance, My/Project would be represented as My%2FProject.
3.4. Since¶
OpenAIRE Guidelines v1
3.5. Example¶
An example that uses all six areas and covers an example of the funding programme ‘’Horizon Europe’‘, as label-term HE:
1 2 3 | <dc:relation>
info:eu-repo/grantAgreement/EC/HE/123456789/EU/Making Capabilities Work/WorkAble
</dc:relation>
|
Note
ProjectId, Jurisdiction, ProjectName, and ProjectAcronym are only examples and doesn’t exists.
An example utilizing all six fields:
1 2 3 | <dc:relation>
info:eu-repo/grantAgreement/EC/FP7/244909/EU/Making Capabilities Work/WorkAble
</dc:relation>
|
An example for omitting the the ProjectName field (note that the number of slashes is correctly preserved):
1 2 3 | <dc:relation>
info:eu-repo/grantAgreement/EC/FP7/283595/EU//OpenAIREplus
</dc:relation>
|
A correct example using the old three-part form (discouraged):
1 2 3 | <dc:relation>
info:eu-repo/grantAgreement/EC/FP7/244909
</dc:relation>
|