Community Call Tomorrow (10/24)

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

Hi everyone,

We'll have our regular community call tomorrow at Noon EDT. For more info, including an agenda, check out the Community Calls page on the Dataverse site:

https://dataverse.org/community-calls

- Danny

[Philip Durbin]

Some notes from https://docs.google.com/document/d/1hDDkRhVnOHrGMBQllPGWXGtJ7dGrIb5qXy8SpJWgYHE/edit?usp=sharing

2017-10-24 Dataverse Community Call

Agenda

* 4.8.1 Release
* 4.8.2 Release
* Community Questions
 
Attendees

* Danny Brooke (IQSS)
* Gustavo Durand (IQSS)
* Phil Durbin (IQSS)
* Pete Meyer (HMS)
* Julian Gautier (IQSS)
* Valessio Brito (Community: Free Software Brazil)
* Sherry Lake (UVa)
* Slava Tikhonov (DANS)
* RC Carter (Microsoft)

Notes

* 4.8.1
   * Released and on GitHub. Mostly performance enhancements: https://github.com/IQSS/dataverse/releases/tag/v4.8.1
* 4.8.2
   * Updates to locking behavior
      * Curators will be able to edit dataset in review: https://github.com/IQSS/dataverse/issues/4139
   * Docker images
      * Dev only: https://github.com/IQSS/dataverse/issues/3938
   * Security enhancements
      * Mitigation of password guessing attacks: https://github.com/IQSS/dataverse/issues/3153
* Community Questions
   * (RC) We're having trouble with S3
      * (Danny) https://github.com/IQSS/dataverse/issues/4223 is being worked on. Waiting for more information from reporter.
      * (Phil) I think we should improve the documentation for S3
      * (RC) It probably is documentation. Learning curve to overcome. We run Dataverse on Azure. We want to replicate in S3, have local Dataverse. Want to add support for Azure blob storage. RC's GitHub username: drizlrc.
         * (Phil) I'll add "Azure Blog Storage" to the "Dev Efforts from Community" spreadsheet: https://docs.google.com/spreadsheets/d/1pl9U0_CtWQ3oz6ZllvSHeyB0EG1M_vZEC_aZ7hREnhE/edit?usp=sharing
      * (RC) We are also working with Galaxy. Any interest?
         * (Danny) Yes, we're interested in Galaxy. It's more of a priority to get Dataverse running on Azure.
   * (Slava) In Norway it was established service DataverseNO, the model is the same as DataverseNL
      * https://dataverse.no
   * (Slava) Finished integration of DataverseNL and EASY Trusted Digital Repository
      * Using Docker, publishing to Docker Hub.
      * Also uses Archivematica and Islandora
      * Could be interesting for Dataverse community.
   * (Danny) dataverse-cessda.eu domain
      * (Slava) Submitted proposal and it was funded. Four partners. More will join.
   * (Sherry) We have a web designer working on our new custom homepage.
   * (Sherry) Would like a drop down of all the dataverses to search in.
   * (Sherry) Would like to have the "featured dataverses" on a custom homepage rather than the normal dataverse page.
   * (Phil) Please see "how to make a pull request" at http://guides.dataverse.org/en/4.8/developers/version-control.html
   * (Julian) We started harvesting from UVA, DataverseNL, and DataverseNO. We are harvesting sets listed in the "List of Dataverse installation OAI-PMH (Harvesting) URLs" spreadsheet: https://docs.google.com/spreadsheets/d/12cxymvXCqP_kCsLKXQD32go79HBWZ1vU_tdG4kvP5S8/edit?usp=sharing
   * (Slava) Metrics
      * We connected miniverse to EASY, using MongoDB as a backend.
      * Maybe our version should be "miniverse2" since it's different.
   * (Phil) Galaxy is used at Harvard Medical School: http://www.refinery-platform.org . We had a meeting in this room just last week. See https://github.com/IQSS/open-source-at-harvard/issues/11 . They might create datasets in Dataverse and upload provenance information.
      * (RC) Maybe Galaxy could call the Dataverse datastore. Very interested in reproducibility.
      * (Pete) Is Galaxy using its own workflow description language? We are always interested in workflows and how to generalize them.
         * (RC) Internally they use Slurm templates.
   * (Sherry) Couldn't access harvested UVa data on Harvard Dataverse. When I go here: https://dataverse.harvard.edu/dataverse/uva_harvested (logged in, because I was prompted to):  Get 403 error: Not Authorized - You are not authorized to view this page.
      * (Julian) We'll check it out. Thanks.

--
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/42ff489a-efd3-4034-b093-f19f18781bc9%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