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

mod-oai-pmh customizations need to be migrated into poppy #11

Open
jeremythuff opened this issue Dec 2, 2024 · 0 comments
Open

mod-oai-pmh customizations need to be migrated into poppy #11

jeremythuff opened this issue Dec 2, 2024 · 0 comments

Comments

@jeremythuff
Copy link
Member

jeremythuff commented Dec 2, 2024

TAMU has customized Mod OAI-PMH so that exported records contain the 998 field. These customizations need to be moved into the Poppy Release of this module.

As best I can tell this is the release of the mod-oai-pmh that is included with poppy: 13.12.8 but this needs to be confirmed.

Here is an example of the the customizations ported for nolana. It will be useful to identify the source code for our current deployment of mod-oai-pmh.

To confirm that the work has been done successfully, the module will need to be built and deployed by operations on an environment that is running both Poppy and VUFind. Once deployed Ricky Lee and Trent Spears will need to confirm that the module is behaving as expected.

@jeremythuff jeremythuff added this to FOLIO Dec 2, 2024
@jeremythuff jeremythuff converted this from a draft issue Dec 2, 2024
@kaladay kaladay moved this from 👷 In Planning to 🏃 On Sprint in FOLIO Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🏃 On Sprint
Development

No branches or pull requests

1 participant