Community Call Tomorrow (12/5) Noon EST

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

Hi everyone,

We'll have our Community Call tomorrow (12/5) at noon EST. We'll talk OR2018, release updates, and community questions. 

As always, you can find the details to call in here:

https://dataverse.org/community-calls

See you soon!

- Danny

[Philip Durbin]

Thank you to Sherry and Courtney for calling in. Here are the notes from https://docs.google.com/document/d/1kDB2q9KcdFAQzEAYCQx_YtI6rhlbxXk7ux1-M8UGbTQ/edit?usp=sharing

2017-12-05 Dataverse Community Call

Agenda

* OR2018 (https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/dataverse-community/_DCN40l1C20)
* 4.8.4 Release
* 4.9 Release
* 5.0 Release
* Community Questions
 
Attendees

* Danny Brooke (IQSS)
* Gustavo Durand (IQSS)
* Phil Durbin (IQSS)
* Pete Meyer (HMS)
* Sherry Lake (UVA)
* Courtney Mumma (TDL)

Notes

* OR2018 - Notes from Sherry to discuss: https://docs.google.com/document/d/1ouoLnwLZK2pS8GiibHne_hKse0rxrZynJ13QQqxTsZw/edit?usp=sharing
   * Possible idea (Pete rambling/brainstorming): phrasing in terms of openness; different repositories funded differently and targeting different user bases (IQSS,UVA,TDL), one aspect is open source collaborating on open source sw (reducing dev effort and required funding for different individual repositories)
   * Danny - suggestion about SBGrid / HMS dataverse, structural biology focused; Pete needs to check availability
* 4.8.4 Release
   * Schema.org focus ( https://github.com/IQSS/dataverse/releases/tag/v4.8.4 )
* 4.9 Release
   * DOIs for files
* 5.0 Release
   * (Danny) We are taking the opportunity to redesign the dataset page and deposit workflows.
* Community Questions
   * (Sherry) Do we have to mint DOIs for files once 4.9 comes out?
      * (Gustavo) Yes, you will have to. It's a best practice to support granularity at the file level. We sent an email about it. No one responded related to this (we did get a response about the format of the identifier). See https://groups.google.com/d/msg/dataverse-community/Jv8i31Wg_Fw/zDytm_VJBAAJ
      * (Sherry) There's a limit for a certain price for DOIs.
      * (Sherry) If you use "file replace" does it get a new DOI?
      * (Gustavo) Yes.
      * (Pete) Do you push the checksum to the DOI provider? What do best practices say?
      * (Gustavo) We don't know.
   * (Courtney) Will we be required to mint DOIs for older files using the method you mentioned?
      * (Gustavo) Yes.
   * (Courtney) Our next production version is going to be 4.8.4 and we plan to use S3. Our developer Nick has seen an issue where only new data files go to S3. Also, datasets are going to S3 but dataverses are not.
      * (Phil) We are working on a script to migrate data files from a filesystem to S3. We recommend waiting until the script is ready.
      * (Danny) We'll identify which GitHub issue is about creating the script.
      * (Phil) For now you can look at https://github.com/IQSS/dataverse/issues/4322 which talks about "moving production data, config, and files to the AWS environment".
      * (Pete) Any more information about dataverses not being on S3?
         * (Danny) Courtney, please create a GitHub issue.

--
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+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/6a930f38-aea4-4ac0-9635-76afcd51a940%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