Great call today! I love hearing about new code, new projects, that the community is working on. Here are the notes:
2018-01-30 Dataverse Community Call
Agenda
* Dataverse Survey (
https://groups.google.com/forum/#!topic/dataverse-community/HMsy1t4BVT4 )
* 4.8.5 Release
* 4.9 Release
* Community Questions
Attendees
* Danny Brooke (IQSS)
* Sherry Lake (UVa)
* Pete (HMS)
* Courtney (TDL)
* Nick W (TDL)
* Slava (DANS)
* Paul (DANS)
* Kevin (SP)
* Don (Odum)
* Phil (IQSS)
* Gustavo (IQSS)
Notes
* Survey
* (Kevin) Should multiple people from the same installation fill it out?
* (Danny) Ideally, one per installation but we can work it out.
* 4.8.5 Release:
https://github.com/IQSS/dataverse/releases/tag/v4.8.5 * IP Group fix.
* Guestbook fix.
* 4.9 Release:
https://github.com/IQSS/dataverse/milestone/68 * Persistent IDs for files.
* Modular Explore.
* Data Explorer
* (Kevin) Data Explorer can be added to Dataverse by running a curl command against a config file. Allows exploration of tabular files. See
https://github.com/IQSS/dataverse/issues/4249 * (Sherry) Can I try it out somewhere?
* (Phil) For today anyway, you can try it at
https://dev1.dataverse.org/file.xhtml?fileId=15 (people are welcome to create datasets, etc but this server will be repurposed soon.) Sherry: Don would like to set it up at Odum and you’re welcome to beat up on it.
* (Kevin) Full production release not expected until March.
* Demo -
https://github.com/scholarsportal/Dataverse-Data-Explorer * (Slava) Does it work with restricted files?
* (Kevin) If you log in, it should work, using an API token.
* (Phil) The logic is that if you see the download button for a file, you can see the explore button for that file (tabular files only).
* (Slava) We're interested in using docker-compose to include external tools.
* Dataverse europe working on using different glassfish container for localization w\ different bundle properties (solr, postgres in separate containers)
* Community Questions
* (Danny) I'm excited to learn more about DataverseEU. We'd be happy to share a link to a website.
* (Courtney and Nick W) Nick W was working on support for institutional members (reports). Top level dataverses for each institution. Interested in download counts. Code at
https://github.com/TexasDigitalLibrary/dataverse-reports (uses Dataverse API and direct database connection). Reports are in CSV format. Configurable fields at the top. Helps liaisons know when new users have created dataverses.
* (Danny) I'll work with Courtney on including this in docs, etc.
* (Sherry) Questions about terms of use and access for files. Files in a dataset might have different licenses. Currently, the license can only be defined at the dataset level.
https://github.com/IQSS/dataverse/issues/1753 is related (but doesn't seem to mention file-level access).
* (Sherry) Seeing unexpected behavior from the "Download URL" for files related to terms of use, etc. When unrestricting a file, I was surprised that I would have to go to the "Terms" tab to make the popup go away.
* (Gustavo) There is design going on around Dataverse 5 and DataTags that's related. Adding GitHub issues is encouraged.
* (Kevin) We had created an Excel spreadsheet for metrics reported. Converted it to CSV, then a web report. Any interest in showing charts from Nick's "dataverse-reports" tool?
* (Nick) I've started looking at Python libraries for charting.
* (Courtney) Next step is to show reports to TDR steering committee.
* (Kevin) Web report -
https://scholarsportal.github.io/Dataverse-Web-Report/ * Source code
https://github.com/scholarsportal/Dataverse-Web-Report