PKP Bugzilla – Bug 5735
Expose important data for bibliographic control
Last modified: 2012-09-21 15:55:55 PDT
We are moving to Git Issues for bug tracking in future releases. During transition, content will be in both tools. If you'd like to file a new bug, please create an issue.
Expose important data for bibliographic control in OJS journals, including:
- journal title
- journal issn
- journal doi
- journal URL
- journal OAI URL
- year of first published item
- year of last published item
- volume number of first published item
- volume number of last published item
- issue number of first published item
- issue number of last published item
- publisher name
- publisher URL
- principal contact name
- principal contact email
Kevin, we don't currently have journal DOIs in the system as metadata; it's too late to add new fields to setup and we'd also need to consider where else to expose these. I'd suggest leaving that one out for this release. I would also suggest that we don't expose any information that wouldn't be exposed elsewhere on the site, i.e. if the journal's archives are closed behind a login, then we shouldn't expose first published / last published info.
Suggest using the OAI <description> node, included in the Identify verb, to describe. This would also make the "OAI URL" entry a bit redundant. Would need to consider how to address both site-level and journal-level requests for this info.
Kevin, can you think of a good XML standard that might hit at least a few of these? If we're only doing this for the sake of our own records, it's somewhat self-serving.
(In reply to comment #3)
> Kevin, can you think of a good XML standard that might hit at least a few of
> these? If we're only doing this for the sake of our own records, it's somewhat
An emerging standard that might apply is the KBART standard:
It is still early days, but this looks like it will move ahead. I believe that the SFU Library is starting to get some title lists from vendors in this format. I can try to find an example, if that would help.
Kevin, good spotting -- that's a pretty close match. Unfortunately it's a CSV-based report (not embeddable in an OAI Identify response), typically delivered by FTP (a push-based mechanism), so I'm not sure how we can make the data available via a pull-based mechanism like OAI. Who releases a data exchange standard these days without at least a mention of XML?
Deferring, unfortunately. Need to do some more requirements work on this first.