Any fish can tell you: It’s important to know the waters you’re swimming in. To that end, Usability Researcher Derek Murphy and Product Research Specialist Julian Gautier have put together a spreadsheet that compares Dataverse’s features, usage, and governance with other prominent online data repositories. In this way, we sought to discover trends in repository design to help inform future development of Dataverse. Now we would like to share our findings with the community.
This release introduces a user management view to the administrator dashboard, listing relevant user information, providing search and super user promotion/demotion functionality. A few other community requested fixes and modifications are also provided.
Display installation users in table format.
Provide super user toggle functionality.
Add additional information to user table: creation time, last login, last api use.
Attendees fill the garden for a group photo at Dataverse Community Meeting 2017.
Photo by Dwayne Liburd
Last week, more than 200 participants from around the world gathered to learn about, discuss, and improve Harvard’s own open-source research data repository software, Dataverse. Dataverse is developed at the Institute for Quantitative Social Science (IQSS) and used by researchers and journals at Harvard University and beyond to archive, share and receive credit for data. At the 2017 Dataverse Community Meeting, attendees and speakers from over 60 universities and other research organizations convened to discuss and address subjects such as data sharing, reproducibility of research, the data lifecycle, and integrating Dataverse with visualization tools, computational resources, and expanded data storage options.
This release provides more customization and branding options for installations, improves documentation, provides better interoperability with citation tools, and incorporates code and bug fixes contributed by the Dataverse developer community during our recent community meeting hackathon.
Allow creating a custom homepage, header, footer, navbar logo.
Remove the system generated word Dataverse from dataverse names, making it optional.
Make all system notifications use the name of the root dataverse in place of the word
This release includes improvements to mapping tabular data via WorldMap, support for object storage using Swift, support for Handles as persistent identifiers, improvements to the guides and various bug fixes:
Fixed classification for latitude/longitude maps
Restored WorldMap preview modal
Added map thumbnail to dataset page
Remove map data that subsequently becomes restricted
Verify WorldMap links remain valid
Improved Geoconnect documentation based on UX review
The Canadian Association of Research Libraries (CARL) Portage Network (https://portagenetwork.ca/), is a national, library-based research data management network that coalesces initiatives in research data management to build capacity and coordinate activities.
Under the auspices of the Portage Network, Dataverse North (https://portagenetwork.ca/dataverse-north-working-group/) is a Canadian research library initiative created to develop a community of practice for libraries using or interested in using Dataverse as a repository for research data in Canada. Comprised of members
This release introduces support for ORCID authentication, a file replace feature, Native API upload, and several enhancements and bug fixes.
Major new features:
In addition to the existing options of a Dataverse account and Shibboleth, users can now sign in through ORCID, Google, and Github. These options can be turned on and off at the installation level, so administrators will be able to set the options that work best for each installation.
The main feature of this release is a File Landing Page, which provides a static URL for files and will serve as a base for expanded file options, such as versioning, provenance, and metadata explorations. Features and bug fixes in this release include:
