Dataverse Community Call Tomorrow 8/29

[danny...@g.harvard.edu]

Hi all,

Please join us for the Dataverse Community Call tomorrow (8/29) at Noon EDT! Details:

http://dataverse.org/community-calls

Thanks!

[Philip Durbin]

Thanks for calling in, Courtney. Here are the notes I took during yesterday's call at https://docs.google.com/document/d/1GD6eXEpdKQPBkZby_xKmPop5Q9mOuX5ksjQmVKEwhho/edit?usp=sharing

Phil

2017-08-29 Dataverse Community Call

Agenda

* Community Development Efforts
* Community Topics
 
Attendees

* Danny Brooke (IQSS)
* Phil Durbin (IQSS)
* Chris Perry (IQSS)
* Pete Meyer (HMS)
* Courtney Mumma (TDL)

Notes

* Community Development Efforts
   * Pinned topic "Which GitHub issues are being worked on by the Dataverse community?" on Google Group: https://groups.google.com/d/msg/dataverse-community/X2diSWYll0w/ikp1TGcfBgAJ
   * "Dev Efforts by the Dataverse Community" spreadsheet: https://docs.google.com/spreadsheets/d/1pl9U0_CtWQ3oz6ZllvSHeyB0EG1M_vZEC_aZ7hREnhE/edit?usp=sharing
   * Amber from Scholars Portal now has write access to the spreadsheet. Others are welcome to request write access as well.
* Community Topics
   * (Danny) Department of Transportation thread - "US Department of Transportation - Data Repositories Conformant with the DOT Public Access Plan": https://groups.google.com/d/msg/dataverse-community/nImLPepZMvs/nk_p-yR9CAAJ
      *  (Danny) I'll send you Jon's message
   * (Courtney) Testing 4.7.1 with Ryan's team. Will pass along feedback. 9 data liaisons.
   * (Danny) We've merged most of the S3 work for the next release. We're still looking at a performance issue. This is slated for 4.8.
   * (Courtney) Question from Nick about deleting files in a deaccessioned dataset.
      * (Phil) You can use the "destroy" API endpoint with a superuser API token to destroy test data. It isn't documented but here's the code we use in our test suite: https://github.com/IQSS/dataverse/blob/v4.7.1/src/test/java/edu/harvard/iq/dataverse/api/UtilIT.java#L551
      * (Phil) There's a related issue: Guides: Add information on deleting datasets, dataverses and destroy command - https://github.com/IQSS/dataverse/issues/2593
   * (Pete) How many users at TDL self-publish vs using the "submit for review" feature.
      * (Courtney) It's up to each of the institutions we host for.
   * (Danny) Is running a fork still necessary for TDL?
      * (Courtney) We just started testing 4.7.1.

--
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-community+unsubscribe...@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/470641e6-c7dc-4ee0-883c-151101c3cab7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

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

[Erin MacPherson]

Hi Phil,

I wanted to ask a related question - the "destroy" API can be used in published datasets on other than "test" data correct? Is this what you would recommend in the occasional case where someone has published sensitive or confidential data and it needs to be removed? Or do you just recommend deaccessioning?  I believe it was mentioned in June at the meeting that we can technically delete it if no one has already downloaded it - otherwise we would de-accession. I just need to clarify the wording for our Terms. 

Thank you,

Erin

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...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/470641e6-c7dc-4ee0-883c-151101c3cab7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.