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

Make sure one can OAI harvest repositories without sets #253

Open
jan356 opened this issue Jan 13, 2022 · 0 comments
Open

Make sure one can OAI harvest repositories without sets #253

jan356 opened this issue Jan 13, 2022 · 0 comments

Comments

@jan356
Copy link

jan356 commented Jan 13, 2022

Some OAI harvestable sources do not have sets. It appears, that when you leave the field "OAI specific set id" empty in the "content source" tab of a collection you want to harvest from an external source, this is translated in the harvesting backend as "...&set=all&..." (see backend log file). This does not work for repositories not having sets.

Feature request 1: Can you please change this behavior so that when the field "OAI specific set id" is empty, it does not translate in the harvesting backend as "...&set=all&...", but translates as nothing/empty.

Feature request 2: The same holds for the "./dspace harvest" command: "-i" for OAI set id is a required parameter, please make it optional. Make sure it does not translate in the harvesting backend as "...&set=all&...", but translates as nothing/empty.

Example:
https://public.yoda.uu.nl/oai/oai?verb=ListRecords&set=all&metadataPrefix=oai_dc
is generated by the backend, with this repository it does not result in any records.

However, the same but without "...&set=all&..." does generate records:
https://public.yoda.uu.nl/oai/oai?verb=ListRecords&metadataPrefix=oai_dc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant