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

Add Source/Server name to OAI-PMH Harvesting clients #10217

Open
DS-INRAE opened this issue Jan 9, 2024 · 6 comments · May be fixed by #11217
Open

Add Source/Server name to OAI-PMH Harvesting clients #10217

DS-INRAE opened this issue Jan 9, 2024 · 6 comments · May be fixed by #11217
Labels
Type: Feature a feature request

Comments

@DS-INRAE
Copy link
Member

DS-INRAE commented Jan 9, 2024

Overview of the Feature Request
As a superuser, I can use a new field to document the source repository in OAI-PMH harvesting clients :
image

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?

@DS-INRAE
Copy link
Member Author

DS-INRAE commented Oct 8, 2024

Hi @jp-tosca, are you still up for a PR to address this issue ? :)

@jp-tosca
Copy link
Contributor

jp-tosca commented Oct 8, 2024

Hi @DS-INRAE thanks for reaching out, it has been a while since we looked at this issue but we can bring it up to the team. This was mentioned on #10464 and reading through the comment I wonder if this last comment from @landreev is where we can pick up from this.

@DS-INRAE
Copy link
Member Author

DS-INRAE commented Oct 8, 2024

Yes,

What would happen if someone has multiple clients harvested into the same collection? 🤔

To be sure to understand is it the case where we have something akin to this ?

  • Harvesting client "A" with Server name "Source_1" in collection Z
  • Harvesting client "B" with Server name "Source_1" in collection Z
  • Harvesting client "C" with Server name "Source_2" in collection Z

In this case (hopefully it's the right one), it should be
Metadata Sources :

  • Source_1 : datasets harvested from A+B
  • Source_2 : datasets harvested from C

Do you want me to also copy this in the comment so it stays in the thread ?

@DS-INRAE
Copy link
Member Author

DS-INRAE commented Oct 8, 2024

We discussed this issue again recently with @stevenferey @jeromeroucou and @luddaniel they will also be able to help answer these and further the discussion 😃

@luddaniel
Copy link
Contributor

Hi @jp-tosca, are you still on the subject or can we develop it ? (not much code normally)

@jp-tosca jp-tosca removed their assignment Dec 5, 2024
@jp-tosca
Copy link
Contributor

jp-tosca commented Dec 5, 2024

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.

@luddaniel luddaniel moved this from 💯 Top priority (5 max) to 🕒 Planned Development in Recherche Data Gouv Jan 29, 2025
luddaniel added a commit to Recherche-Data-Gouv/dataverse that referenced this issue Feb 5, 2025
@luddaniel luddaniel linked a pull request Feb 5, 2025 that will close this issue
@luddaniel luddaniel moved this from 🕒 Planned Development to 🚧 Dev by Recherche Data Gouv in Recherche Data Gouv Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Feature a feature request
Projects
Status: 🚧 Dev by Recherche Data Gouv
Development

Successfully merging a pull request may close this issue.

3 participants