Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider adding support for sitewide plugin operation #6

Open
ajnyga opened this issue Nov 23, 2018 · 6 comments
Open

Consider adding support for sitewide plugin operation #6

ajnyga opened this issue Nov 23, 2018 · 6 comments

Comments

@ajnyga
Copy link

ajnyga commented Nov 23, 2018

Hi,

Maybe this and the other plugin connected to this one could be sitewide?

@asmecher
Copy link
Member

Perhaps as an override; one of the use cases it's being developed for requires it to be selectively enabled (for large installations, one or two of whose journals need to be indexed via JATS/OAI.

@ajnyga
Copy link
Author

ajnyga commented Nov 23, 2018

where do you index using JATS?

My interest concerns OpenAIRE. They now prefer JATS instead of the old DC extensions they used.

I have been in contact with them and will have a skype call next Tuesday concerning the OpenAIRE plugin. My aim is to combine the Funding plugin and the OpenAIRE so that the Funding plugin handles the projectID stuff and the OpenAIRE plugin just reads that data if it is available. Basically the whole OpenAIRE plugin will be revised, or at least the version I will make.

One option would be to use your Jats plugin, but the problem is that if a Jats galley exists, it will use that and most likely that Jats document will not include the details OpenAIRE wishes to see (I still think that the front section of any JATS galley should be always dynamically created based on the OJS metadata). So I will probably make my own flavor of oai_jats that is always dynamically created so that OpenAIRE can use that for indexing.

@asmecher
Copy link
Member

This is for Coalition Publi.ca -- most of the journals included there will use a combination of the OAIJats plugin and the JATS Template plugin (although some may generate the JATS through another means).

The OAIJats plugin already overrides the front content with what's built into OJS; I think that might be a useful starting point? I envision custom JATS requirements as some kind of filter process, so it might be worth adding a hook or two here so that aspects of the document can be overridden before output.

@ajnyga
Copy link
Author

ajnyga commented Nov 23, 2018

Ah, ok great!

I think they are mainly interested in the article access status, possible embargo dates and funding data. It could also be that they need a metadataformat with a specific name, I will ask about that next week.

@odolany
Copy link

odolany commented Apr 11, 2019

Do I understand correctly from the above that accessing multi-journal contents through /index.php/index/oai?verb=ListRecords&metadataPrefix=jats is not to be expected by design?

@asmecher
Copy link
Member

@odolany, yes for the moment -- though we're open to proposals/contributions. It would still need to be able to operate on a journal-by-journal basis but it may be possible to support both.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants