This document discusses how Dataverse helps researchers publish and share their data through automation and integration with other systems across the research data lifecycle. Dataverse provides APIs for harvesting, depositing, searching, and downloading data. It aims to integrate with tools for data management planning, data analysis, journal publishing workflows, and long-term data preservation in archives. The goal is to make research data more discoverable, reusable, and able to assess its impact over time.

1. Dataverse: Helping Researchers Publish Their Data
Through Automation
Eleni Castro, Research Coordinator
IQSS, Harvard University
IDCC 2016 - Feb 24, 2016
@dataverseorg Dataverse.org

2. Helping Researchers Share & Archive Data At Their Point of Need
catalog.archives.gov/id/554290
2

3. Our Quest For Interoperability and Automation
● OAI-PMH for harvesting metadata from Dataverse
● SWORD API: depositing metadata + data from a SWORD client into
Dataverse
● Search API: searching dataverses, datasets and files within Dataverse
● Data Access API: downloading files from datasets found in Dataverse
● Native API: for performing GUI and super-user functionality programmatically
via REST
In 2016: adding meta-tags and schema.org metadata for datasets
More info at: http://guides.dataverse.org/en/latest/api/index.html 3

4. Research Life Cycle Workflow
Modelled off UCI Libraries diagram: http://previous.lib.uci.edu/dss/images/lifecycle.jpg
4

5. 1. Planning Phase
5

6. Future Integration with DMPTool
See: http://blog.dmptool.org/2016/01/22/dmptool-maintenance-and-a-roadmap
6

7. 2. Implementation Phase
7

8. OSF Dataverse Add-On to archive data
via SWORD API
See: https://osf.io/getting-started/#dataverse 8

9. R package to deposit data & search Dataverse
Thomas Leeper’s code: https://github.com/rOpenSci/dvn
9

10. Data Visualizations from Dataverse...
10

11. Data Visualizations from Dataverse via WorldMap
11http://worldmap.harvard.edu

12. Data Visualizations and Analysis with ClioInfra
https://www.clio-infra.eu/
via Data Access API
+ Native API
12

13. 3. Publishing Phase
13

14. Integrate Journal and Data Publishing Workflows
Paper: http://journal.code4lib.org/articles/10989 14

15. Future: Integrate data quality review + verification
15
http://ajps.org/2015/03/26/the-ajps-replication-policy-innovations-and-revisions/

16. Future: Dataverse / ORCID Integration
See: Requiring ORCID in Publication Workflows: Open Letter 16
1. Allow users to authenticate using their ORCID ID.
2. Automatically insert ORCID ID into Dataset and
search ORCID ID to insert for co-authors.
3. Add to and update ORCID records (Subject to
permissions granted by iD holders).

17. 4. Discovery & Impact Phase
17

18. Expand Dataset Discovery via SHARE Notify
http://www.share-research.org/projects/share-notify/ 18

19. Send Dataset Metadata to DataCite
Coming soon in Dataverse
19DataCite Metadata 3.0

20. Future: Measure Dataset Impact with Altmetrics
Example from Univ of Southampton
Example from Univ of Zurich
20
See Repository Badges documentation:
https://www.altmetric.com/products/free-tools/institutional-repository-badges/

21. 5. Preservation Phase
21

22. Scholars Portal Dataverse Integration With Archivematica
Image source & read more: https://wiki.archivematica.org/Dataverse 22

23. Helping Future
Researchers Re-Use
Data
23

24. Thank You!
Questions?
ecastro@fas.harvard.edu 24