Notification Service JS Demo

Configure the client, then try subscribing, unsubscribing, or listing subscriptions for a resource.

1. Configure the client

API prefix URL Access token

The token is read from this field right before each request via the getToken callback.

* If using url https://notifications.test.dataone.org/notifications, you can get a test token from metacat-dev.test.dataone.

Resource types (comma-separated)

These populate the resource type selectors below and are passed to the client as resourceTypes.

Requests rely on your network environment and token. Any thrown error is logged below so you can see what the client received from the service.

How this demo uses the library

A single NotificationClient instance is created after you submit the configuration form.
getToken is a promise-returning callback that reads the token input. In production, you can pass in a method that fetches a fresh token from the dataone token endpoint.
validatePID is a simple async check that ensures the PID input is not empty. In the future, we could replace it with verification that the resource type matches the format ID of the object.
Each form handler awaits the client call and pushes either the JSON response (if any) or the thrown error into the log viewer.