 |
Page History
The following table lists some frequently asked questions about DME:
| Question | Answer | |||
|---|---|---|---|---|
| What kind of data can be stored in DME? | (TBD: Ben's message mentioned Long term storage, high value datasets; Lab data; and External datasets for this question. The Word document user guide mentions data produced from high performance computing systems; the data storage and data management needs of NCI cancer community; sequencing project, imaging study or any data analysis project; A collection can be any category of business domain entities such as: Project, Dataset, Folder, Samples, Runs, and so on. Which of these points are currently valid? What else can this row mention?) | |||
| Why should I use DME? | Each laboratory or NCI business unit may adopt or engage with a variety of biomedical/clinical research and produce many forms of data. A Division/Office/Center (DOC) can define its own metadata structure and data hierarchy rules. With input from each DOC’s group administrator, a DME system administrator configures the required metadata and validation rules for each collection type. Some DOC groups may script or automate the generations of their actual data/metadata files in their Laboratory Information Management System (LIMS) system to enable seamless integration between the LIMS and DME, with little human intervention. (TBD: The Word document user guide mentions the above points. What else can this row mention?) | You can safeguard your data and easily access it. | ||
| What kind of data can be stored in DME? | You can store scientific high-value datasets. | |||
| How can I store How can I register data in DME? | You can register store an individual file (up to 10 GB) from your file local system or register store data in bulk from Globus, AWS S3, Google Drive, or Google DriveCloud storage. You You can register store data using the web application's graphical user interface (GUI) or Command , Command Line Utilities (CLU). | Include Page | | shared info - CLU vs GUI | shared info - CLU vs GUI | For details, refer to Uploading or Registering Data. (TBD: Ben's message mentioned shared drive & Biowulf for this question. What can this row say about those?), or the REST API. If you want fine-grained control of the activity, or if you want to integrate it into your scientific workflow, consider using CLU or API. Otherwise, consider using the GUI.
| How can I access my data? | You can access your data using the web application ( GUI) or Command Line Utilities (CLU). | Include Page | | shared info - CLU vs GUI | shared info - CLU vs GUI | For details, refer to Finding Data, Viewing or Retrieving Metadata, and Downloading Data. (TBD: Ben's message mentioned API and NIDAP for this question. The wiki user guide doesn't currently say much about the API. What can this row say about API and NIDAP?), CLU, or REST API.
| How is my data secured? | If To access DME data, users must have an NIH account and request a DME account from NCIDataVault@mail.nih.gov. DME employs geographical redundancy to protect data against accidental deletion. Also, if your user account has the Own permission level on a collection or a data file, you can manage permissions on that data. You can manage permissions on one file or collection at a time, or in bulk. Permission levels include Own, Write, Read, and None. For details, refer to Managing Permissions. (TBD: Ben's message mentioned "Security stuff, passwords" for this question. What can this row say about that? The following row already mentions about NIH account.) | |||
| How can I get an account? | If you have an NIH account, the NCI Data Vault team can give you access to DME. For access requests or any other questions, contact NCIDataVault@mail.nih.gov. | |||
| What data is already available in DME?(TBD: Ben's message mentioned "Sequencing Facility" and "TCGA" for this question. Do we need permission from the data owners before listing their data here? Are there any other examples we can list here?) | Presently, DME stores 11 TB of data including next generation sequencing and high throughput data. |
