Skip to content

Service Providers

A Service Provider is an Organisation that acts on behalf of a Customer. Customers are able to authorise service providers to perform various actions on their behalf. This is configurable, site-by-site, by the customer. The Service Provider is not able to view reports for the Customer, or log into the Customer's Oversight account.

A Customer may set 'Read' or 'Write' permission to a Service Provider for a given Site.

'Read' access allows Service Providers to:

  • Check the status of a Submission
  • Recieve a status callback for a Submission

'Write' access allows Service Providers to:

  • Upload a Submission

Use Cases

Using these permissions, it is possible for Service Providers to handle the entire flow, or only part of it. The following use cases are possible:

1: Service Provider is a Manuscript Tracking Platform with alerts

Service Provider is a Manuscript Tracking System which will send data to Oversight, and get data back. Alerts will be shown to users, and they will be linked to the report.

Permission: Read + Write for each Site

Setup:

  1. Prerequisites
    1. The Publisher is a customer of Clear Skies and has set up an account.
    2. The Service Provider has an account on Oversight, and we have configured it as a Service Provider.
  2. Configuration
    1. Publisher sets up a Site on Oversight for each Journal (contact support).
    2. Publisher sets up a site on Service Provider for each Journal.
    3. Publisher grants Read + Write access to Service Provider for each Site.
    4. Service Provider registers domains for callbacks, and secrets.
    5. Optional: Service Provider sets a callback domain for all sites.
  3. Operation
    1. Service Provider POSTs a submission when it is received.
    2. Optional: A callback URL is sent for each Submission, rather than at the Site configuration level.
    3. Service Provider polls for updates, or listens for callbacks.
    4. Service Provider shows an alert level in the system, and links out to the report in Oversight.

2: Service Provider provides a Dashboard, but Submissions are sent by another Integration.

Service Provider is a dashboard that shows alerts. It does not send Submissions. Instead these are sent by ScholarOne (S1) or Editorial Manager (EM).

  1. Prerequisites
    1. The Publisher is a customer of Clear Skies and has set up an account.
    2. The Publisher is a customer of EM/S1 and has set up an account.
    3. The Publisher is a customer of Service Provider.
    4. The Service Provider has an account on Oversight, and we have configured it as a Service Provider.
  2. Configuration
    1. Publisher sets up a Site on EM/S1 for each Journal.
    2. Publisher sets up a Site on Oversight for each EM/S1 Site (contact support). All configuration is completed.
    3. Publisher grants Read access to Service Provider for each Site.
    4. Service Provider registers domains for callbacks and file uploads, and configures secrets.
    5. Service Provider sets a callback domain for all sites.
  3. Operation
    1. EM/S1 sends Submissions to Oversight directly.
    2. Service Provider recieves callbacks for updates.
    3. Service Provider optionally polls for new Submissions.
    4. Service Provider retrieves submission information, including the External ID, status and report URL.
    5. Service Provider shows an alert level in the system, and links out to the report in Oversight.

3: Service Provider is a Manuscript Tracking Platform that doesn't show alerts.

Service Provider is a Manuscript Tracking System which will send data to Oversight. There is no way to show alerts to users within the Service Provider's system, and users are encouraged to check Oversight for alerts.

Permission: Write for each Site

Setup:

  1. Prerequisites
    1. The Publisher is a customer of Clear Skies and has set up an account.
    2. The Service Provider has an account on Oversight, and we have configured it as a Service Provider.
  2. Configuration
    1. Publisher sets up a Site on Oversight for each Journal (contact support).
    2. Publisher sets up a site on Service Provider for each Journal.
    3. Publisher grants Write access to Service Provider for each Site.
    4. Service Provider registers domains for file uploads, and configures secrets.
  3. Operation
    1. Service Provider POSTs a submission when it is received.
    2. User checks Oversight or waits for email digest.