Introduction to configuring RSpace Apps

This section is for administrators - if you are looking at enabling apps as a user of RSpace, please see Apps Introduction.
This section can be ignored if you are using an RSpace that is hosted by ResearchSpace, i.e if it has a URL ending in 'researchspace.com'. The instructions here only to RSpace installations with their own domain name.

Introduction

RSpace users can easily link to data on other services in RSpace, using APIs provided by those services. This section of the documentation explains how to set up RSpace so that it is authorised to be able to access users' accounts on their behalf.

Requirements for App activation

For an app to be usable, it needs to be:

  1. available - i.e., your institution allows you to use the Integration (see "Configuring availability of apps" below)
  2. enabled - a personal decision by the end-user in the Apps page
  3. configured - some Apps can be configured by the end user, others require assistance from RSpace support as part of the initial setup (see table below)
    For Apps requiring RSpace Support, this is a one-off initial setup - it's not required to be performed for every individual user on the system.

App Name

Additional configuration instructions

Action required

Dropbox

None

None

Box

None

None

OneDrive

RSpace server must be registered with Microsoft Azure as a OneDrive client application

Contact RSpace Support

GoogleDrive

RSpace server must be registered with Google as a client application

Read more at Setting up RSpace - Google Drive app

Contact RSpace Support

OwnCloud

RSpace server must be registered as a client application with your OwnCloud server

Admins should refer to Setup instructions. Setup will require assistance from your ownCloud admins as well as RSpace Support

Protocols IO

RSpace server must be registered as a client application with Protocols.io

Read more at Setting up Protocols.io integration

Contact RSpace Support

Mendeley

RSpace server must be registered as a client application with Mendeley

Contact RSpace Support

Egnyte

RSpace server must be registered as a client application with Egnyte

Contact RSpace Support

Github

1. RSpace server must be registered as a client application with Github.

Contact RSpace Support

Dataverse

End-user can configure access to their Dataverse in the Apps page

None

Figshare

RSpace server must be registered as a client application with Github

Read more at Setting up integration with Figshare Repository

Contact RSpace Support

Orcid

RSpace server must be registered as a client application with Orcid

Read more at Setting up Orcid integration

Contact RSpace Support

Chemistry

None

None

Microsoft Office Online

1. If using a .researchspace.com RSpace cloud-hosted instance, add reverse proxy to MSOffice instance

2. If using an on-prem RSpace instance, your domain will need to be registered with Microsoft as a wopi client.

Contact RSpace support for either scenario.

Evernote

None

None

Microsoft Teams

Follow instructions here

None

Slack

RSpace Slack App must be registered with your Slack Workspace

Contact RSpace support

Pyrat

None

None

Configuring availability of apps

The System Admin can set the availability of Apps across an entire RSpace instance. If an App is not available, no user users will be able to access the App. If the App is available, users can individually choose to enable it or not for their accounts.

So, for example, if your institution does not want users to link to information on external filestores such as Dropbox or Box, then you can prevent users from using RSpace’s Box/Dropbox integrations by making these Apps unavailable. (Of course, if a user insists on using Dropbox and manually inserting links to Dropbox into RSpace, that is not something that RSpace can stop).

To set up the configuration, navigate to System->Configuration->System Settings

Screen Shot 2016-04-28 at 22.50.40

Each setting can be set independently. Most are simple boolean switches.

Note that some apps require additional configuration (see table above).


How did we do?


Powered by HelpDocs (opens in a new tab)

Powered by HelpDocs (opens in a new tab)