-
Notifications
You must be signed in to change notification settings - Fork 11
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
Comments
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. |
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. |
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. |
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. |
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? |
@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. |
Hi,
Maybe this and the other plugin connected to this one could be sitewide?
The text was updated successfully, but these errors were encountered: