-
Notifications
You must be signed in to change notification settings - Fork 9
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
Implement JSTOR-compliant ONIX 3.0 XML output #283
Conversation
…t MUSE ONIX output" This reverts commit 9dc527f.
I guess that even if MUSE accepts this specification we should keep them separate, but link them under platform, e.g. |
Good point. Since MUSE said they could only accept titles with at least one BIC/BISAC and didn't want Keywords included, I'm about to make that change to the MUSE specification, which would make it diverge from the JSTOR specification anyway. |
JSTOR have now confirmed that this format meets their specifications. As mentioned above, MUSE have stricter requirements for subject codes, so would not be able to ingest this format. However, they didn't mention any objections to the changes JSTOR initially requested (listed under #44 (comment)). |
Fixes #44 by creating a new, separate ONIX output, based on the Project MUSE output, which fixes the minor issues noted in #44 (comment).
We are still awaiting feedback from a) JSTOR, to confirm that the changed format does now meet their requirements, and b) Project MUSE, to comment on whether the changed format would be acceptable to them.
If Project MUSE have no issues with the minor changes, we should ideally merge the separate MUSE and JSTOR outputs back into a single "flavour". This PR allows users to create JSTOR-compliant output in the meantime.