Publish/release Dataverse dataset
publish_dataset(dataset, minor = TRUE, key = Sys.getenv("DATAVERSE_KEY"),
server = Sys.getenv("DATAVERSE_SERVER"), ...)
An integer specifying a dataset identification number or an object of class “dataverse_dataset”. The identification number is the dataset's persistent identification number (not the integer specifying a specific version of the dataset, such as returned by dataset_versions
).
A logical specifying whether the new release of the dataset is a “minor” release (TRUE
, by default), resulting in a minor version increase (e.g., from 1.1 to 1.2). If FALSE
, the dataset is given a “major” release (e.g., from 1.1 to 2.0).
A character string specifying a Dataverse server API key. If one is not specified, functions calling authenticated API endpoints will fail. Keys can be specified atomically or globally using Sys.setenv("DATAVERSE_KEY" = "examplekey")
.
A character string specifying a Dataverse server. There are multiple Dataverse installations, but the defaults is to use the Harvard Dataverse. This can be modified atomically or globally using Sys.setenv("DATAVERSE_SERVER" = "dataverse.example.com")
.
A list.
Use this function to “publish” (i.e., publicly release) a draft Dataverse dataset. This creates a publicly visible listing of the dataset, accessible by its DOI, with a numbered version. This action cannot be undone. There are no requirements for what constitutes a major or minor release, but a minor release might be used to update metadata (e.g., a new linked publication) or the addition of supplemental files. A major release is best used to reflect a substantial change to the dataset, such as would require a published erratum or a substantial change to data or code.
# NOT RUN {
meta <- list()
ds <- create_dataset("mydataverse", body = meta)
publish_dataset(ds)
# }
Run the code above in your browser using DataLab