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

Implement ONIX 2.1 output compliant with EBSCO Host requirements (#49, #43) #290

Merged
merged 11 commits into from
Oct 1, 2021

Conversation

rhigman
Copy link
Member

@rhigman rhigman commented Oct 1, 2021

Fixes #43 and part-fixes #49 (EBSCO Host require ONIX 2.1, EBSCO KnowledgeBase require KBART - and are provisionally happy with the format created under #277).

@rhigman rhigman requested a review from ja573 October 1, 2021 09:08
This was linked to issues Oct 1, 2021
Copy link
Member

@ja573 ja573 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It'll make sense to differentiate the various EBSCO arms in the specifications, too (not just in platforms). Could you rename all instances of "ebsco" with "ebsco_host"? e.g. "onix_2.1::ebsco_host". Not just in data.rs but throughout the export API, e.g. methods, file names, etc.

@rhigman rhigman requested a review from ja573 October 1, 2021 10:49
@rhigman rhigman merged commit 80cc131 into develop Oct 1, 2021
@rhigman rhigman deleted the feature/49_ebsco_onix2.1 branch October 1, 2021 16:11
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

Successfully merging this pull request may close these issues.

Output to EBSCO Generate ONIX 2.1
2 participants