Handle.net PIDs - identifier globally visible even for unpublished datasets

[Volodymyr Kushnarenko]

Dear Dataverse community,

I am currently testing a combination of Dataverse with handle.net PIDs and have some questions, because I see a different behaviour compare to DOIs.

1) I see, that every new handle will be stored as globally visible (with a permission "public read"), that you can find it right away on the http://hdl.handle.net/ server, even if the corresponded dataset is not published yet (is only a draft). Is such a behaviour correct or I have just a wrong configuration of the local handle server? If it is correct - can this visibility of handles be critical for the private not published data or not? Looks like not, because after the click on the handle link an authentication on the repository side is needed, to access this not published data... 

2) In the handle.net manual stands, that you can edit permissions via admin GUI [1] or via a batch submission [2, MODIFY command] - looks like for the "URL" Handle Data we need permissions "1100" instead of standard "1110" to hide these unpublished datasets. Could it be practical for Dataverse to have a similar behaviour for handles like we have it for DOIs on DataCite - unpublished datasets get only reserved and not-findable PIDs, and when dataset is published, PID becomes also globally visible? Or such a complexity in case of handles is just not needed?

Many thanks for your reply in advance,

Vladimir

[1] http://www.handle.net/HSj/admin-tool-help.html#modifyhandle_html

[2] http://www.handle.net/HSj/admin-tool-help.html#batchhandle_html

[James Myers]

Vladimir,

I haven’t used Handles and don’t know if there’s a reason for the current behavior, or if it is a function of your server. Hopefully others with more history and/or anyone using Handles today can help.

 

That said, with a quick look in the code, it appears to me that handles are created/reregistered with publicRead – true (e.g. in https://github.com/IQSS/dataverse/blob/ba0183d1eda2260f9eccbda886f60c9b800c90ee/src/main/java/edu/harvard/iq/dataverse/HandlenetServiceBean.java#L116-L122 I think publicRead is the last true) rather than public read depending on whether the dataset is released or not.

 

Assuming this isn’t as intended you could submit an issue in github.

 

W.r.t. your question 1 – as you say Dataverse still protects the draft dataset from being visible so the main concern is that seeing the handle tells you the dataset exists and that it is in a given Dataverse.

 

-- Jim

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/eea51af6-50c6-4bdb-9fb3-8ecc711364c9n%40googlegroups.com.

[Philip Durbin]

Vladimir, thanks for creating https://github.com/IQSS/dataverse/issues/8881 about this.

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/MN2PR07MB7343A4FAF3A9943F174770DDBF909%40MN2PR07MB7343.namprd07.prod.outlook.com.

--

Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin