When I create a dataset, I want use an existing DOI #6425
Comments
|
@tcoupin thanks for the explanation, the screenshot, and the offer to make a pull request! Let's let the community discuss here or elsewhere and see how much interest there is! This "use an existing DOI" feature reminds me a bit of harvested datasets because it's a way for DOIs to get into an installation of Dataverse that aren't under the main DOI authority/prefix for that installations. For example, the main DOI authority/prefix for Harvard Dataverse is 10.7910 but in the screenshot below, I'm showing harvested datasets with a DOI authority/prefix of 10.18738 and 10.6141:
The other thing I'm reminded of is how sometimes installations of Dataverse are torn about including licensed data in Dataverse. Dataverse will assign all datasets a DOI. Sometimes there is a desire to not assign a DOI to licensed datasets. This was mentioned in passing in "Best Practices for Research Data Management" at https://www.youtube.com/watch?v=sIm9CZipNYo Finally, there was some good discussion about scope (only one DOI authority/prefix) in the original "DataCite DOI Support Functional Requirements Document" years ago that feels somewhat related: https://docs.google.com/document/d/1DAiQ80-69EUW1so-qY3HVfcjiy4zaObg4RDfz18da_k/edit?usp=sharing |
|
Hi @tcoupin, I don't think we'd want to support this for similar reasons that we didn't want to merge #5105/#5104 and we would not accept a PR. The workflow of data in other systems can currently be supported through OAI-PMH and in the future will be supported by TRSAs (http://cyberimpact.us/dataverse-trusted-remote-storage-agent-update/). We don't want to implement the ability to point to external objects outside of these two methods. |
|
I followed the recommendations of #5105 (comment) |
|
@djbrooke @pdurbin Hi, I hope you're doing fantastic! How I understand TRSA, the PIDs will still be minted in Dataverse. Am I mislead? Can that mechanism really be used to reference external PIDs? @tcoupin Could you please check out #5402 to see if your issue is covered by that one? If this will not find a way to core, I'd be very interested in your branch! |
|
@RightInTwo good question. Can you please leave a comment on #6423 with your thoughts on how a data citation should look? |
I unterstand your use case as "I want to feed a dataverse by creating datasets based on metadatas associated with a DOI". It's very interresting! The only thing I want is to not create a new DOi for an existing DOI |
|
@tcoupin Indeed. It would be one step further to fetch the metadata based on the DOI, but the prerequisite is the same: Facilitate externally managed DOIs. @pdurbin I know I've had my fair share of disruption by creating and cross-referencing all kinds of issues. Maybe I can help cleaning up? Contact me :) |
|
We plan to remove our "New dataset with existing DOI" feature from Datasud and replace it by "Create dataset by harvesting a DOI". Similar to OAI client feature, it will create remote hosted dataset.
So not in the dataverse kernel ^^ So a micro service! |
|
@tcoupin I'm not sure I completely understand what you're proposing but let's keep talking about it! 😄 |
|
@RightInTwo Yes. This code creates a real dataset which can lead to an asynchronism between the metadata in dataverse and those associated with the DOI. I plan to set up an OAI-PMH service which will serve the metadata of a DOI list. In Dataverse, I will set up an OAI-PMH client to harvest this service. |
|
@tcoupin I though we could maybe merge these two issues as they serve the same use case. Of course, avoiding the async is quite important, so I'd be happy to support you with that solution and drop my makeshift code! |
|
Hi @tcoupin @RightInTwo, like @pdurbin, I'm not sure that I understand exactly what you're planning here. Is there a diagram that could be included about the proposal? |
|
@RightInTwo nice diagram. I'm copying it here too:
|
|
Thanks @tcoupin @RightInTwo @pdurbin. Since we'll be handling this with no changes to the Dataverse code, I'll close this out. |
|
To follow along from here, please see https://github.com/IQSS/doi2pmh-server , the repo we created as part of #5402. |
I create this issue to continue the PR "Feat existing doi on creation" #5105
On our dataverse https://dataverse.ird.fr, we allow user to provide an existing DOI.
This DOI can have the same prefix as set in
:Authority, or not. If DOI has the good prefix, Dataverse update it on publication and modification like a standard DOI. If not, no update is made.This feature allow us to use Dataverse as the main referencial for our institution: external data can be reference in this central point, expecially for non OAI-PMH data warehouse.
I think this feature can be useful to other and I can create a new PR with it. I you want, this feature can be disabled by default, and enabled with a new setting in database.
File changes: v4.17...tcoupin:v4.17-IRD3
Files:
The text was updated successfully, but these errors were encountered: