Update OpenAIRE plugin

[mtub]

A few years ago, the OpenAIRE plug-in has been added to OJS (see http://pkp.sfu.ca/support/forum/viewtopic.php?t=7085&f=28). OpenAIRE is an important European Union-funded project (https://www.openaire.eu/project-factsheets). One of its goals is to increase literature repository interoperability through common guidelines and some standards for OAI use. Those guidelines help implement means to track output of EU-funded projects. The plug-in added necessary metadata fields (i.e. grant number) and made OJS OpenAIRE-compliant.

But the guidelines have evolved since 2011, they now exist in version 3. The plug-in should be reviewed and updated according to the latest guidelines (e.g. the mandatory OAI set should be renamed from 'EC_fundedresources' to 'open_aire') (see https://guidelines.readthedocs.org/)

Code is in generic plugins: https://github.com/pkp/ojs/tree/master/plugins/generic/openAIRE

Porting this to OMP should be a good thing, too.

Will be happy to assist with review and update if someone picks this up. @bozana? At least you were the original author...

[bozana]

@mtub, wouldn't it be again a project we could work together on? On a weekend... :-)

[lilients]

Hi @mtub , @bozana and everybody else,

at the project OJS-de.net we want to implement the necessary changes for the OpenAIRE plugin (german description, code).

I just started having a look at the guidelines and the plugins. There is also the DRIVER plugin (german description, code) which will not be needed anymore, because they have the same guideline now. I would propose to adapt the OpenAIRE plugin and remove the DRIVER plugin.

These are my TODOs based on the OpenAIREs content acquisition policy:

Obligatory features:

• check for OA
• follow guidelines (datacite format, rename set to openaire)
• make project id optional

Optional features:

• add version number to metadata (https://guidelines.openaire.eu/en/latest/data/field_version.html)
• add alternative identifiers (dc:relation)
• add relations to other publications (dc:relation)
• add option to enter persistent identifiers to research datasets (dc:relation)
• add option to enter funding info (project identifier)

Nice to have:

• register journal with OpenAIRE (automatically || semi automatically)

Thats it for now. Always happy to get feedback or ideas, if you think I missed something. 🌞

[bozana]

@lilients, maybe you would like to take a look also at this changes: pkp/ojs#1383. They are for 2.4.x, but maybe there are some of them interesting for your project and for 3.x as well? I haven't taken a look yet, but hopefully soon, then I can tell more... -- just for information...

[lilients]

thanks for the info @bozana . I would wait for your review of these changes, so I can include them to the migration.

[ajnyga]

Hi all,

A general question concerning funding information. Is there any point to handle funder infomation both in the OpenAIRE plugin and in the forthcoming integration with CrossRef funder registry (formerly fundref)?

Should there instead be a OJS native way of handling (saving, fetching) funder information (funder name, funder id, project id, grant id) and use that information for both OpenAIRE and CrossRef? This would in my opinion mean removing the current Sponsoring Agencies metadata field and replacing it with a more sophisticated way of handling funder information.

All the other things mentioned in @lilients post I give a big thumbs up!

[bozana]

@lilients, what exactly do these items mean (in/for OJS):

• add alternative identifiers (dc:relation)
• add relations to other publications (dc:relation)
• add option to enter persistent identifiers to research datasets (dc:relation)

@ajnyga, I will take a look at those funder registries and information OpenAIRE needs -- in case that each institution (e.g. Crossref and OpenAIRE) has different requirements, a different list and internal IDs, it would mean that each plugin would have to implement it on its own...

[ajnyga]

I am just worried about a situation where a user has to enter similar kind of funder data to several fields.

[bozana]

Yes...

[joschirr]

Hi, please be patient and hold on.
We are in preparation of a new release of the OpenAIRE Literature Guidelines which will (among other things) recommend the reuse of certain fields from the datacite metadata standard v4, such as FundingReference. As a consequence this will allow to make use of the FundRef-IDs also for OpenAIRE compatible metadata.

[ajnyga]

Just for reference, this is a funder registry (fundRef) plugin for OJS3 I have made. I know that PKP is planning to work on a similar integration, but this was among the things I promised to work on in my project last fall: https://github.com/ajnyga/fundRef

[ajnyga]

Hi @joschirr

What is the planned schedule for the release of the new OpenAIRE literature guidelines? We would like to handle OpenAIRE data as well in the Funding plugin: https://github.com/ajnyga/funding

Comparison of CrossRef funder data, datacite funder data and OpenAIRE project data based on the current guidelines.

CrossRef		Datacite		OpenAIRE
funder_identifier	=	funderIdentifier	=	missing
funder_name	=	funderName	=	Funder*
award_number	=	awardNumber	=	projectID**
missing	=	awardTitle	=	ProjectName
missing	=	awardURI	=	missing
missing	=	missing	=	ProjectAcronym
missing	=	missing	=	FundingProgramme***

* Only two options: European Commission (EC) or Wellcome Trust (WT)? For OAI the acronyms are used.
** Not sure if the projectID is/can be the exact same thing?
*** only two options: FP7 and H2020?

Sources:
https://support.crossref.org/hc/en-us/articles/214360746-Funding-data-overview
https://guidelines.openaire.eu/en/latest/literature/field_projectid.html
https://schema.datacite.org/meta/kernel-4.0/

[ajnyga]

https://blogs.openaire.eu/?p=2397

[joschirr]

Sorry for my late reply.
OpenAIRE Guidelines v4 will support the DataCite fundingReference element node incl. the CrossRef funding data.
I'm not sure if it makes sense for e-journal platforms like OJS to follow these new guidelines (application profile based on DC and DataCite) or better should expose JATS by default.

[joschirr]

Note that OpenAIRE already interprets funding and project grantIds / awardURIs also from other funders and funding programmes than FP7 and H2020. These two are of course most important for us but are not limited on them.

[ajnyga]

fyi: currently in contact with OpenAIRE and started to work on this...

edit: I have great plans (tm)

[asmecher]

@ajnyga's great plans came to fruition! https://github.com/ajnyga/openaire