Skip to content

Latest commit

 

History

History
111 lines (67 loc) · 3.68 KB

installation.md

File metadata and controls

111 lines (67 loc) · 3.68 KB
Raw

Installation

Recommended versions node >=16 and npm >=8.

Getting Started with the Stable Version

A stable 1.x version of this package is available as js-dataverse at https://www.npmjs.com/package/js-dataverse

Install the package stable version using npm:

npm install js-dataverse

Getting Started with the Development Version

An unstable 2.x version of this package with breaking changes is under development.

Until a 2.0 version is officially released, it can be installed from https://github.com/IQSS/dataverse-client-javascript/pkgs/npm/dataverse-client-javascript

Create a .npmrc file and add a token

To install the @iqss/dataverse-client-javascript from the GitHub registry, follow these steps to create an .npmrc file in the root of your project using your GitHub token.

  1. Create .npmrc in your project's root directory.

    touch .npmrc

  2. Replace the Token

    Open the newly created .npmrc file and replace YOUR_GITHUB_TOKEN with your actual GitHub token.

    legacy-peer-deps=true

 //npm.pkg.github.com/:_authToken=<YOUR_GITHUB_AUTH_TOKEN>
 @iqss:registry=https://npm.pkg.github.com/

How to Get a GitHub Token

If you don't have a GitHub token yet, follow these steps:

  1. Go to your GitHub account settings.

  2. Navigate to "Developer settings" -> "Personal access tokens."

  3. Click "Personal access tokens" -> "Tokens (classic)" -> "Generate new token (classic)".

  4. Give the token a name and select the "read:packages" scope.

  5. Copy the generated token.

  6. Replace YOUR_GITHUB_AUTH_TOKEN in the .npmrc file with the copied token.

Now, you should be able to install the Dataverse JavaScript client using npm.

Install the package

Install the package development version using npm:

npm install @iqss/dataverse-client-javascript

Initialization

In order for the package to connect to the Dataverse API, there is an APIConfig object that should be initialized to set the preferred authentication mechanism with the associated credentials for connecting to the Dataverse API.

Currently, the supported authentication mechanisms are:

  • API Key: The recommended authentication mechanism. The API Key should correspond to a particular Dataverse user account.

  • Session Cookie: This is an experimental feature primarily designed for Dataverse SPA development. To use this mechanism, you must enable the corresponding feature flag in the Dataverse installation (See https://guides.dataverse.org/en/latest/installation/config.html?#feature-flags). It is recommended not to use this mechanism and instead use API Key authentication.

It is recommended to globally initialize the ApiConfig object from the consuming application, as the configuration will be read on every API call made by the package's use cases.

For example, in a React application, we can globally initialize the ApiConfig object in the App file, like this:

ApiConfig.init(<DATAVERSE_API_BASE_URL>, DataverseApiAuthMechanism.API_KEY, <DATAVERSE_API_KEY>)

function App() {
  /* Yor App code */
}

export default App

The same example but with example values set:

ApiConfig.init(
  'http://localhost:8000/api/v1',
  DataverseApiAuthMechanism.API_KEY,
  'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx'
)

function App() {
  /* Yor App code */
}

export default App

We can initialize the ApiConfig object as an unauthenticated user, by setting undefined as the API Key value.

This will allow use cases that do not require authentication to be successfully executed, but those that do require authentication will fail.