Next Dataverse Community Call: Handles Support (May 10)

[eca...@g.harvard.edu]

Hi Dataverse Community,

Our next Community Call on May 10 at 12pm EST will be of interest to those of you already using (or wanting to use) Handles as persistent identifiers for your datasets in Dataverse 4.x.

In preparation for this call please see the Business Requirement Document we have started putting together for Handles Support.

Call information is below my signature but please feel free to contact me or add a reply to this post if you have any questions or concerns.

Thank you,

Eleni

-- 

Eleni Castro
Research Coordinator, Data Curation and Outreach
IQSS, Harvard University
617-496-0703
http://www.iq.harvard.edu/people/eleni-castro 
http://orcid.org/0000-0001-9767-8536

Dial in Number:	1-866-889-3913 USA 1-334-323-7225 USA 108007141899 CHINAN* 108001401929 CHINAS* 08000229306 NETHER*
Passcode:	30867
Reserved Lines:	15

[Eugene Barsky]

I just wish that times would also allow West Coast folks to participate. While 6am are not always a problem for me personally, I feel that other team members are still asleep :)

E

On Tuesday, 26 April 2016 06:15:52 UTC-7, eca...@g.harvard.edu wrote:

Hi Dataverse Community,

Our next Community Call on May 10 at 9am EST will be of interest to those of you already using (or wanting to use) Handles as persistent identifiers for your datasets in Dataverse 4.x.

[Castro, Eleni]

Hi Eugene,

You are definitely right that this time is a tad on the early side for folks on the West Coast. It is challenging to figure out times that would work for everyone in the Dataverse Community. I am going to propose to my team that in the future we could host some of our community calls at a more reasonable hour for your side of the continent.

Thanks for your feedback,
Eleni

Eleni Castro
Research Coordinator, IQSS
Harvard University

--
You received this message because you are subscribed to a topic in the Google Groups "Dataverse Users Community" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dataverse-community/xM6vmat0LFI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to dataverse-commu...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/0411e88d-b39a-4bbf-a0a6-a8dbeeb0e363%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Eleni Castro]

Hi Eugene,

After speaking with my team we decided that going forward our Community Calls will be scheduled to start at 12pm EST / 9am PST / 6pm CEST. I hope this adjusted time works for everyone interested in attending these calls and from time to time, depending on the audience, we may adjust a specific meeting to begin at an earlier time (with advanced notice).

I have updated this information on our site under Community Calls and will send a reminder to the community next week.

Please let me know if you have any questions or concerns.

Best,

Eleni

To unsubscribe from this group and all its topics, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse-community@googlegroups.com.

[Eugene Barsky]

Eleni:

This is brilliant. Thanks! Letting my colleagues on West Coast know as well...folks, see below.

Are there any other Dataverses implemented on the West Coast?

Eugene

Eleni

To unsubscribe from this group and all its topics, send an email to dataverse-commu...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/0411e88d-b39a-4bbf-a0a6-a8dbeeb0e363%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to a topic in the Google Groups "Dataverse Users Community" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dataverse-community/xM6vmat0LFI/unsubscribe.

To unsubscribe from this group and all its topics, send an email to dataverse-commu...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/2140ce5e-7a40-4521-9771-4e842551ac8a%40googlegroups.com.

[Eleni Castro]

Eugene:

To my knowledge (see Dataverse installations map) ABACUS is the only one on PST but Alberta would benefit from a later call as well.

Cheers,

Eleni

Eleni

To unsubscribe from this group and all its topics, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse-community@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/0411e88d-b39a-4bbf-a0a6-a8dbeeb0e363%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "Dataverse Users Community" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dataverse-community/xM6vmat0LFI/unsubscribe.

To unsubscribe from this group and all its topics, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse-community@googlegroups.com.

[Joke Pol]

Hi, here some input for the call.

I tried to analyse the code base related to handles and DOI's. This could serve as some concrete input to discus during the community call planned for May 10.

I examined the DatasetCommand classes and service beans that seemed relevant to me leving resolving out of scope. As the DOI beans looked quite similar I tried to create and apply an interface for these two classes, this research exercise resulted in my observations in the following overview.

Command classes: 

CreateDatasetCommand

UpdateDatasetCommand

PublishDatasetCommand

DeleteDatasetCommand

DestroyDatasetCommand

UpdateTargetDatasetTargetUrlCommand

Beans:

DOIEZIdServiceBean

DOIDataCiteServiceBean

HandlenetServiceBean

None of the three beans are called by DeleteDatasetCommand nor DestroyDatasetCommand

I would expect the DOI and HandleNet beans being used by the dataset commands in a similar way, yet:

* DOIEZIdServiceBean lacks the method alreadyExists, HandlenetServiceBean has a completely different API

* DOIEZIdServiceBean is not called for by UpdateDatasetCommand nor UpdateTargetDatasetTargetUrlCommand

* HandlenetServiceBean is only called by UpdateTargetDatasetTargetUrlCommand

I suppose other subtle changes (especially error handling) are different evolutions after copy-pasting.

It looks like handles are only supported for changes to the target URL. I did not research whether the DOIEZIdServiceBean could implement the alreadyExists method somehow.

As handles should be persistent we (DANS) require to let the handle point to something after (deletion? and) destruction of a dataset. That something should at least produce the original citation, the reason for deletion, who requested it, gave permission and when it was destroyed.

Jo Pol

Software Developer

+31 6 20 10 55 18

Data Archiving and Networked Services (DANS)

DANS promotes sustained access to digital research data. Please visit www.dans.knaw.nl for more information. DANS is an institute of KNAW and NWO.

DANS | Anna van Saksenlaan 51 | 2593 HW The Hague | P.O. Box 93067 | 2509 AB The Hague | +31 70 349 44 50 | in...@dans.knaw.nl | www.dans.knaw.nl

[Kraffmiller, Stephen E]

Hi Jo,

A quick response to a couple of your observations about the DOI implementation.

1) We only update the metadata sited at DataCite/EZid on dataset publish so it is intentional that nothing happens in the UpdateDatasetCommand.

2) The UpdateTargetDatasetTargetUrlCommand calls the EZidServiceBean via the command context (ctxt.doiEZId().modifyIdentifier(target, metadata))

I am currently modifying this command to include support for DataCite.

Pengcheng Luo from Peking University wrote the DOIDataCiteServiceBean modeling it after the DOIEZidServiceBean which I wrote. I was responsible for integrating the DOIDataCiteServiceBean into the Dataverse code base. We can discuss your project in more detail outside the context of the community call if you would like.

Best,

Steve Kraffmiller

IQSS

--
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 post to this group, send email to dataverse...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/D349328D.443D%25joke.pol%40dans.knaw.nl.

[Ben Companjen]

Hi Steve,

Thanks for your quick response!

About your comment about currently modifying a command to support DataCite: what Jo has been trying to say is that we should consider moving the responsibility to support the different persistent identifier providers out of the commands so that you don't have to change every command for each new provider.

And while we're talking about moving responsibilities, perhaps we could also talk about moving the DOI and Handle beans to a more suitable package than the main edu.harvard.iq.dataverse package?

Regards,

Ben

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/B1012370-5C7B-4740-AE87-20A8B350C65B%40hmdc.harvard.edu.