Domandata
FeaturesProductPlansAboutHelp
Sign InCreate Free Account
Domandata
Follow us on LinkedInFollow us on YouTubeFollow us on XFollow us on Bluesky

Product

  • Features
  • Product
  • Plans
  • Changelog

Company

  • About
  • Cite
  • Help
  • Feedback

Compare

  • Switch to Domandata

Account

  • Sign In
  • Create Account

Legal & Trust

  • Privacy
  • Terms
  • Security
  • Trust Center
  • Status
© 2026 Domandata LLC. All rights reserved.
Back to Help
Export

Deposit a Replication Package in Harvard Dataverse

Connect Harvard Dataverse, create or link a draft dataset, deposit replication files, and submit the dataset for repository review.

Connect Harvard Dataverse

Connect a Harvard Dataverse account when you want to deposit a Domandata replication package directly into a repository dataset. Domandata stores the API token encrypted and never displays it again.

Settings: Harvard Dataverse

  1. In Harvard Dataverse, open your account settings and create or view your API token.
  2. In Domandata, open Settings and expand Harvard Dataverse.
  3. Paste the token and choose Connect Harvard Dataverse.

Treat the token like a password. Disconnecting removes the encrypted token from Domandata but does not delete any dataset or file already deposited in Harvard Dataverse.

Deposit a Replication Package

Export: Harvard Dataverse

  1. Open the survey and select Export.
  2. In the Harvard Dataverse card, choose Deposit Replication Package.
  3. Choose whether to create a new dataset or use an existing dataset DOI or Handle.
  4. For a new dataset, review the title, author, contact, description, subject, and host collection alias.
  5. Review the privacy choices. The Privacy panel starts from The Public; choose Review to pick a different audience or change any column, and choose whether to include a GitHub Sync repo snapshot — see below.
  6. Choose whether the files should remain restricted after publication, then deposit the package.

A new deposit includes the response data, SPSS and Stata files, cleaning log, codebook, data dictionary, survey instrument, Flow diagram, analysis templates, README, and package metadata. Network identifiers are always removed.

For The Public, columns that identify someone directly and open free-text answers are dropped, and rare combinations of demographic answers are suppressed. Any column can be set to Keep, Broaden, Redact PII, Coded ID, Mask, or Drop instead, and the package README lists every choice — see Privacy Choices and GitHub Snapshots. If this survey has a GitHub Sync repo connected, you can also include a snapshot of that repo's current contents (its author-drafted analysis pipeline included) as an extra file in the deposit; see GitHub Sync.

Review Before Publishing

Domandata leaves every deposit unpublished. Open the draft dataset in Harvard Dataverse and review its citation metadata, file restrictions, privacy choices, and package contents before submitting it for review.

Submit for Review starts Harvard Dataverse's administrative review workflow; it does not publish the dataset immediately. If you deposit into an already published dataset, Harvard Dataverse creates or updates its draft version.

Do not publish respondent data that your consent language, IRB protocol, data-use agreement, or institutional policy does not permit you to share. File restriction settings are not a substitute for removing direct and indirect identifiers.

Related Help

  • Connect OSF, Preregister, and Push Replication Packages
  • Privacy and Anonymity in Research Surveys
  • Survey Data Quality Checks
  • GitHub Sync