Provide a Staging Area for Your Files
In previous sections we discussed how you can provide researchers with information about the files in your database, both in the small with file-specific metadata and in the large with a text-based search capability. Now we turn our attention to the process of allowing these users to access these files and transfer them to other locations for analysis and manipulation by site-specific processes.
Recall that the Data Transfer System (DTS) orchestrates transfers of data between the databases of participating organizations like yours. Transferring such data invariably involves moving files from a "source" staging area in one organization to a "destination" staging area in another. Here, a staging area is a file system visible to some file transport mechanism such as Globus. To allow the DTS to access your data for transfer, your organization must establish and maintain such a file staging area.
At this time, the DTS relies on Globus to move files between different databases and organizations. Globus is widely used in the scientific research community by universities and DOE national laboratories, and its design reflects its focus on helping researchers share and access data. Additionally, Globus can be integrated with other file storage and transfer platforms like Amazon S3, Google, and many others. This interoperability allows Globus clients to interoperate seamlessly even in heterogeneous technological settings.
Setting up a Staging Area
First, your organization must allocate a file staging area on a filesystem that
you can expose to Globus. The directory structure of this staging area for your staged
files isn't important to anyone outside your organization, as long as all of the
files staged there can be made accessible to Globus (and transitively, to the
DTS). Recall, though, that the path
element in the
Frictionless DataResource
metadata specification for each file should match your staging area's directory
structure--otherwise, the DTS won't be able to locate your file.
Probably the most important decision you'll make about the staging area is the directory in the filesystem that serves as the effective "root" directory for the staging area. This "root" directory determines the root path you'll use when you create a Globus guest collection that allows the DTS to access its files.
The DTS is a work in progress, and we haven't yet worked out all the details for handling private or embargoed datasets. We're interested to hear your opinions on this and other topics!
Exposing Your Staging Area to Globus
If your organization has a Globus subscription, you'll have an easy time configuring a file staging area that can be integrated with the DTS. Globus has extensive documentation to help you understand how to share your data effectively.
To make your staging area available to the DTS, you'll need to set up a Globus guest collection. The following links can help you configure your Globus setup:
- How to Share Data Using Globus: a step-by-step guide to creating a guest collection that can serve as a staging area for your organization
- Storage Connector Usage Guides: a landing page for documentation about Globus's connectors, which allow you to access data stored on other platforms like Amazon S3 and Google Cloud Storage
- The Modern Research Data Portal: an article describing a design pattern for providing secure, scalable, and high performance access to research data
- Globus Connect Server: information about how Globus can be deployed within your organization (probably most useful to an IT department!)
In particular, the first link walks you through the steps of creating a guest collection. When you've set up a guest collection in which you can stage files for transmission and receipt, the DTS team can work with you to authorize the Data Transfer Service to use this guest collection so it can access these files.