### Integrating Dataverse with Language Resource Switchboard.
### Integrating Dataverse with the Language Resource Switchboard.
This repository contains a collection of files that are built according to the [Dataverse external tools interface](https://guides.dataverse.org/en/latest/admin/external-tools.html) in order to make the Clarin [Language Resource Switchboard](https://switchboard.clarin.eu) available through the external tools button on Dataset pages (left). Some of these files also implements data previewer apps for embedded display on Datafile pages (right), these previewers are based on those originally developed by the [Qualitative Data Repository](https://qdr.syr.edu).
#### Installation
The files can be installed on a Dataverse instance by executing the curl command(s) below to register them with the local Dataverse instance. In alternative the code can be downloaded and used locally.
The files can be installed on a Dataverse instance by executing the curl command(s) below to register them with the local Dataverse instance. In alternative the code can be downloaded and used locally. Detailed instructions for a local installation can be found at the [Dataverse Projcet site](https://guides.dataverse.org/en/latest/admin/external-tools.html#).
In the current release there is one file for each mime type.
In the current release there is one file for each mime type, each file can be installed independently from others.
#### Known limitations
To send a protected file to the Switchboard or to preview it, the permission to access the dataset version containing the file is required, this means that a valid API Token must be used. Instead sending/viewing public content does not require an API Token. Files in the current release *do not allow* to send to LRS or to preview protected files, this feature will be implemented in next releases.
Files in the current release *do not allow* to send to LRS or to preview restricted content (i.e. non public files). To send a non public file to the Switchboard or to preview it, the permission to access the dataset version containing the file would be required, technically speaking this means that a valid API Token should be used. Instead sending/viewing public content does not require an API Token.
The decision to implement the processing of restricted content depends on the security policy that will be adopted.
The current release has been tested with Dataverse v5.11+, however it should work also with Dataverse releases v4.12+.
*This is an in progress activity, code may change and may be not stable all the time.*
*This is an in progress activity, code may change and may not be stable all the time.*
#### Curl commands to configure and run web applications with a Dataverse instance:
