-
Notifications
You must be signed in to change notification settings - Fork 500
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
Add Source/Server name to OAI-PMH Harvesting clients #10217
Comments
Hi @jp-tosca, are you still up for a PR to address this issue ? :) |
Yes,
To be sure to understand is it the case where we have something akin to this ?
In this case (hopefully it's the right one), it should be
Do you want me to also copy this in the comment so it stays in the thread ? |
We discussed this issue again recently with @stevenferey @jeromeroucou and @luddaniel they will also be able to help answer these and further the discussion 😃 |
Hi @jp-tosca, are you still on the subject or can we develop it ? (not much code normally) |
Sorry @luddaniel I see that I was still assigned to this but I removed myself. I will bring it up again to the team when I see Leo to see if this can be planned or prioritized. |
…ata source facet quality
Overview of the Feature Request

As a superuser, I can use a new field to document the source repository in OAI-PMH harvesting clients :
In order to (see related issues) filter content from various harvested repositories with a search facet.
One source/server name should be able to be used for several clients (e.g. to dispatch several sets from the same repository in different dataverse collection).
What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
Superuser
What inspired the request?
Needed for our harvested repositories.
Any open or closed issues related to this feature request?
The text was updated successfully, but these errors were encountered: