NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: For HPCDATAMGM-1828: Added dbGaP.
Note

This page is a work in progress.

The following table defines various conceptsterms:

Advanced Tables - Table Plus
sortColumn1
Concept location in which you can store data for later retrieval that data (To request more collection types, contact NCIDataVault@mail.nih.gov.) The metadata. Metadata make it easier for you to find the associated data a upload Upload uploaded to DME.A program that supports asynchronous Globus with DME such as gridftp
TermDefinition
DOCA division, office, or center.
archiveA long-term storage location for datasets, or the process of storing datasets in that location.
collectionA folder for a dataset or project. A collection might have one or more collections within it. A collection can be identified by a custom collection type such as Project, Study, Sample, and so on, the default being Folder.
collection pathThe unique location of each collection in DME.
metadataAttribute values associated with your data in the archive. Metadata describe the data, such as the date and origin of creation, its contents, its condition, its processing, or its associations to other objects. Metadata can make data searches faster, more specific, and also enable and promote data sharing among scientists. The system automatically generates some metadata for each collection or file in the archive. Some data might also have custom (user-defined) attributes. The DOC policy file specifies the required attributes for each collection type. If the DOC policy file specifies that a particular attribute is required for a particular collection type, then DME requires a value for that attribute during registration.
metadata fileA file that contains metadata for each object (data file) or collection in bulk registration, as described in Preparing a Metadata File for Bulk Registration.
attributeA field for a piece of information that helps to describe your data.
data hierarchyAn arrangement or classification of data. In DME, data are stored as objects, which are organized into collections (folders), and a collection might have one or more collections within it. A collection can be identified by a custom collection type such as Project, Study, Sample, and so on, the default being Folder.
metadata policy fileA file that defines valid collection types. (To develop or modify this file, contact NCIDataVault@mail.nih.gov.)
DOC policy fileA file that specifies the required attributes for each collection type. (To develop or modify this file, contact NCIDataVault@mail.nih.gov.)
data object or data fileA file that will be or has been
synchronousTransfer of files using processes that run sequentially. This type of transfer is not optimal for large files.
asynchronousHigh performance transfer (upload or download) of large files, using processes that run independently of other processes.
registered into DME. It can be a single file or a compressed file.
data file pathThe unique location of each data file in DME.
dbGaP

The NIH database of Genotypes and Phenotypes.

Globus

A system that performs

Globus

transfer of large files. For instructions, refer to Preparing to Use

Globus. For Globus-specific terms, refer to the following glossary:

http://toolkit.globus.org/toolkit/docs/4.1/glossary.html

Multiexcerpt include
MultiExcerptNameExitDisclaimer
nopaneltrue
PageWithExcerptwikicontent:Exit Disclaimer to Include

Google DriveA file storage service.
Google CloudA file storage service.
endpointA destination that represents a location on a file transfer service server.
AWS S3Amazon Simple Storage Service. If you intend to use DME CLU, refer to Preparing to Use AWS S3 Bucket for the CLU
GUIThe graphical user interface, which allows basic search, registration, and download activities in DME.
CLUThe Command Line Utilities, which allow integration of DME into your scientific workflow or fine-grained control of DME.
tierA layer of the DME deployment architecture. All users ultimately use the Production tier. Some users use the User Acceptance Testing (UAT) tier as a testing environment.
UUIDThe Universally Unique Identifier for a data entity.
iRODS iCATA DME integration that manages metadata and its security for both collections and data files. 
registrationTransfer collections, files, and metadata to DME from another system (such as your local system, Globus, Google Drive, Google Cloud, or AWS S3).
downloadTransfer collections and files from DME to another system (such as your local system, Globus, Google Drive, Google Cloud, dbGaP, or AWS S3).