Dataverse moved to v5 in late 2020. All our new tests are tested against 5 so we can claim to cover that? (cc @wibeasley)

Author: kuriwaki

DESCRIPTION

@@ -53,7 +53,7 @@ Suggests:
     testthat,
     UNF,
     yaml
-Description: Provides access to Dataverse version 4 APIs <https://dataverse.org/>,
+Description: Provides access to Dataverse APIs <https://dataverse.org/> (versions 4-5),
     enabling data search, retrieval, and deposit. For Dataverse versions <= 3.0,
     use the archived 'dvn' package <https://cran.r-project.org/package=dvn>.
 License: GPL-2

README.Rmd

@@ -1,5 +1,5 @@
 ---
-title: "R Client for Dataverse 4 Repositories"
+title: "R Client for Dataverse Repositories"
 output: github_document
 ---
 
@@ -13,7 +13,7 @@ Sys.setenv("DATAVERSE_SERVER" = "dataverse.harvard.edu")
 
 [![Dataverse Project logo](https://dataverse.org/files/dataverseorg/files/dataverse_project_logo-hp.png)](https://dataverse.org)
 
-The **dataverse** package provides access to [Dataverse 4](https://dataverse.org/) APIs, enabling data search, retrieval, and deposit, thus allowing R users to integrate public data sharing into the reproducible research workflow. **dataverse** is the next-generation iteration of [the **dvn** package](https://cran.r-project.org/package=dvn), which works with Dataverse 3 ("Dataverse Network") applications. **dataverse** includes numerous improvements for data search, retrieval, and deposit, including use of the (currently in development) **sword** package for data deposit and the **UNF** package for data fingerprinting.
+The **dataverse** package provides access to [Dataverse](https://dataverse.org/) APIs (versions 4-5), enabling data search, retrieval, and deposit, thus allowing R users to integrate public data sharing into the reproducible research workflow. **dataverse** is the next-generation iteration of [the **dvn** package](https://cran.r-project.org/package=dvn), which works with Dataverse 3 ("Dataverse Network") applications. **dataverse** includes numerous improvements for data search, retrieval, and deposit, including use of the (currently in development) **sword** package for data deposit and the **UNF** package for data fingerprinting.
 
 ### Getting Started
 
@@ -32,7 +32,7 @@ library("dataverse")
 
 #### Keys
 
-Some features of the Dataverse 4 API are public and require no authentication. This means in many cases you can search for and retrieve data without a Dataverse account for that a specific Dataverse installation. But, other features require a Dataverse account for the specific server installation of the Dataverse software, and an API key linked to that account. Instructions for obtaining an account and setting up an API key are available in the [Dataverse User Guide](https://guides.dataverse.org/en/latest/user/account.html). (Note: if your key is compromised, it can be regenerated to preserve security.) Once you have an API key, this should be stored as an environment variable called `DATAVERSE_KEY`. It can be set within R using:
+Some features of the Dataverse API are public and require no authentication. This means in many cases you can search for and retrieve data without a Dataverse account for that a specific Dataverse installation. But, other features require a Dataverse account for the specific server installation of the Dataverse software, and an API key linked to that account. Instructions for obtaining an account and setting up an API key are available in the [Dataverse User Guide](https://guides.dataverse.org/en/latest/user/account.html). (Note: if your key is compromised, it can be regenerated to preserve security.) Once you have an API key, this should be stored as an environment variable called `DATAVERSE_KEY`. It can be set within R using:
 
 ``` r
 Sys.setenv("DATAVERSE_KEY" = "examplekey12345")

README.md

@@ -1,4 +1,4 @@
-R Client for Dataverse 4 Repositories
+R Client for Dataverse Repositories
 ================
 
 [![CRAN
@@ -12,10 +12,10 @@ Status](https://travis-ci.org/IQSS/dataverse-client-r.png?branch=master)](https:
 logo](https://dataverse.org/files/dataverseorg/files/dataverse_project_logo-hp.png)](https://dataverse.org)
 
 The **dataverse** package provides access to
-[Dataverse 4](https://dataverse.org/) APIs, enabling data search,
-retrieval, and deposit, thus allowing R users to integrate public data
-sharing into the reproducible research workflow. **dataverse** is the
-next-generation iteration of [the **dvn**
+[Dataverse](https://dataverse.org/) APIs (versions 4-5), enabling data
+search, retrieval, and deposit, thus allowing R users to integrate
+public data sharing into the reproducible research workflow.
+**dataverse** is the next-generation iteration of [the **dvn**
 package](https://cran.r-project.org/package=dvn), which works with
 Dataverse 3 (“Dataverse Network”) applications. **dataverse** includes
 numerous improvements for data search, retrieval, and deposit, including
@@ -34,7 +34,7 @@ library("dataverse")
 
 #### Keys
 
-Some features of the Dataverse 4 API are public and require no
+Some features of the Dataverse API are public and require no
 authentication. This means in many cases you can search for and retrieve
 data without a Dataverse account for that a specific Dataverse
 installation. But, other features require a Dataverse account for the
@@ -257,13 +257,12 @@ subsequent pages, specify `start`.
 
 ### Data Archiving
 
-Dataverse provides two - basically unrelated - workflows for managing 
-(adding, documenting, and publishing) datasets. The first is built on 
-[SWORD v2.0](http://swordapp.org/sword-v2/). This means that to create a 
-new dataset listing, you will have to first initialize a dataset entry with 
-some metadata, add one or more files to the dataset, and then publish 
-it. This looks something like the following:
-
+Dataverse provides two - basically unrelated - workflows for managing
+(adding, documenting, and publishing) datasets. The first is built on
+[SWORD v2.0](http://swordapp.org/sword-v2/). This means that to create a
+new dataset listing, you will have to first initialize a dataset entry
+with some metadata, add one or more files to the dataset, and then
+publish it. This looks something like the following:
 
 ``` r
 # retrieve your service document