Introduction to configuring RSpace Apps
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:
- available - i.e., your institution allows you to use the Integration (see "Configuring availability of apps" below)
- enabled - a personal decision by the end-user in the Apps page
- 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 | Does RSpace data leave server? |
Dropbox | None | None | No |
Box | None | None | No |
OneDrive | RSpace server must be registered with Microsoft Azure as a OneDrive client application | Contact RSpace Support | No |
GoogleDrive | RSpace server must be registered with Google as a client application Read more at Setting up RSpace - Google Drive app | Contact RSpace Support | No |
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 | No |
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 | No |
Mendeley | RSpace server must be registered as a client application with Mendeley | Contact RSpace Support | No |
Egnyte | RSpace server must be registered as a client application with Egnyte | Contact RSpace Support | Yes, if used as file backend. No, otherwise |
1. RSpace server must be registered as a client application with Github. | Contact RSpace Support | No | |
Dataverse | End-user can configure access to their Dataverse in the Apps page | None | Yes- RSpace exports |
Figshare | RSpace server must be registered as a client application with Github Read more at Setting up integration with Figshare Repository | Contact RSpace Support | Yes- RSpace exports |
Orcid | RSpace server must be registered as a client application with Orcid Read more at Setting up Orcid integration | Contact RSpace Support | No |
None | None | No | |
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. | Yes, to Microsoft servers, which could be located anywhere. | |
None | None | No | |
2. If server is not on *.reserachspace.com domain the Teams app needs to be updated to explicitly whitelist the URL of the server. | Contact RSpace support in second scenario. | Yes, via content of messages | |
RSpace Slack App must be registered with your Slack Workspace | Contact RSpace support | Yes, via content of messages | |
Requires a client ID set on the RSpace server. This must be obtained from a PyRAT administrator | Contact RSpace support | No. Pyrat data is imported to RSpace | |
Requires a client ID /secret set on the RSpace server. | Contact RSpace support | No to browse DMPS; yes if RSpace data exported | |
Requires a client ID /secret set on the RSpace server. | Contact RSpace support | No. Clustermarket data is imported into RSpace | |
RSpace must have network reachability to a Collabora instance. | Contact RSpace support | Yes, to Collabora instance that is configured. | |
To access full content from JoVE you must have an active subcription with JoVE, and your RSpace email much match the one used with JoVE | Contact Sysadmin to enable the integration | No | |
Dryad must be configured to authenticate with RSpace server. | Contact RSpace Support | Yes- RSpace exports |
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 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
Each setting can be set independently. Most are simple boolean switches.
