Community Call Today: CC0 and Deaccession/Curation Workflows

26 views
Skip to first unread message

danny...@g.harvard.edu

unread,
Aug 28, 2018, 10:31:55 AM8/28/18
to Dataverse Users Community
Hi everyone,

We'll have our usual call at Noon ET today. In addition to the usual community questions, there are two suggested topics. If you have topic suggestions for future calls, please let me know! 

For more details, including call in information, please check out the Community Calls page: 


Thanks,

Danny 

Philipp at UiT

unread,
Aug 30, 2018, 2:36:31 AM8/30/18
to Dataverse Users Community
I just had a look at the meeting notes. Interesting discussion about CC0 and deaccessioning. Here some input from DataverseNO:

CC0
- DataverseNO uses CC0 as default. So far, all datasets have CC0.

Deaccession and Curation Workflows at Dataverse Installations
- All datasets in DataverseNO are curated by subject librarians. Only curators can publish datasets. We have a test server for testing and demo. The curator guidelines for deaccessioning are available here.

Best,
Philipp

Courtney Mumma

unread,
Aug 30, 2018, 10:12:58 AM8/30/18
to dataverse...@googlegroups.com
Hi all,

Further to this -- when I was in the meeting with the TDR Steering Committee yesterday, we discussed this a little more and I can add the following feedback:

  • They would like a dropdown with the licenses available - a controlled vocab that could be supplemented by the admin
  • Very few have opted out of CC0. One institution gets more pushback from humanities researchers about CC0. 
  • They would love to search by license.
  • They noted that this could get more complicated as we progress the system to allow for handling of sensitive datasets.
Kindly,
Courtney


--
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/534fdf69-1f19-45e5-aa92-3f9796b0b2c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

danny...@g.harvard.edu

unread,
Aug 30, 2018, 10:22:55 AM8/30/18
to Dataverse Users Community
Thanks both for the details about how your communities are using licenses in Dataverse. I encourage people to check out the notes:

https://docs.google.com/document/d/1JpN8qkZ3FUhoQHBOCk3ZsR7F0_7AA5wv6Ky9iRtMz70/edit

... and to add to this thread with additional thoughts! 

Thanks,

Danny
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse-community@googlegroups.com.

Philipp at UiT

unread,
Aug 30, 2018, 10:47:24 AM8/30/18
to Dataverse Users Community
A short note on Courtney's feedback

They would like a dropdown with the licenses available - a controlled vocab that could be supplemented by the admin

This feature has been suggested previously; cf. this thread.

 - Philipp

To post to this group, send email to dataverse...@googlegroups.com.

julian...@g.harvard.edu

unread,
Aug 30, 2018, 3:46:15 PM8/30/18
to Dataverse Users Community
Thanks Phillip and Courtney for the details so far! The DataverseNO data curation guide is helpful to see.

Courtney, you wrote that for TDR 
  • Very few have opted out of CC0. One institution gets more pushback from humanities researchers about CC0.
Would you know why that is for humanities researchers (as opposed to others) and what terms or licenses they would prefer? I see some general insights about why in this great article, "State of the art report on open access publishing ofresearch data in the humanities", but nothing that seems specific to humanities research.

Thanks again!
Julian
Reply all
Reply to author
Forward
0 new messages