You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #354 we learned that DataVerse distinguishes dataset PIDs and file PIDs. Given that information, it could be discussed whether the following code should be supported:
I think it would be perfectly valid to discard this as out of scope - I just wanted to put out the question. The reasoning for out of scope would be: DOI resolution in pooch assumes a one-to-one correspondence of a pooch.Pooch instance and a data set. DOI resolution outside of this context is not supported. If on the other hand DOI resolution is extended to retrieve, this might happen for other data repositories as well, so it needs to be done proper.
Are you willing to help implement and maintain this feature?
Yes, with no specific timeline for the implementation.
The text was updated successfully, but these errors were encountered:
@dokempf I've been thinking about this and it would generate a bit of a disconnect between pooch.Pooch and pooch.retrieve since it wouldn't make sense to create a Pooch class for a repository with a single file. But if the individual file has a DOI and we keep the syntax of URLs having file names at the end, then I'd be fine with this use case. I guess it would mean putting in some checks in the Dataverse downloader, right? Is the API response for file and dataset different?
Description of the desired feature:
In #354 we learned that DataVerse distinguishes dataset PIDs and file PIDs. Given that information, it could be discussed whether the following code should be supported:
I think it would be perfectly valid to discard this as out of scope - I just wanted to put out the question. The reasoning for out of scope would be: DOI resolution in
pooch
assumes a one-to-one correspondence of apooch.Pooch
instance and a data set. DOI resolution outside of this context is not supported. If on the other hand DOI resolution is extended toretrieve
, this might happen for other data repositories as well, so it needs to be done proper.Are you willing to help implement and maintain this feature?
Yes, with no specific timeline for the implementation.
The text was updated successfully, but these errors were encountered: