Home
Fundamentals
Research Data Management
FAIR Data Principles
Metadata
Ontologies
Data Sharing
Data Publications
Data Management Plan
Version Control & Git
Public Data Repositories
Persistent Identifiers
Electronic Lab Notebooks (ELN)
DataPLANT Implementations
Annotated Research Context
ARC specification
ARC Commander
Swate
MetadataQuiz
DataHUB
DataPLAN
Ontology Service Landscape
Manuals
ARC Commander
Setup
Git Installation
ARC Commander Installation
Windows
MacOS
Linux
ARC Commander DataHUB Access
Before we start
Central Functions
Initialize
Clone
Connect
Synchronize
Configure
Branch
ISA Metadata Functions
ISA Metadata
Investigation
Study
Assay
Update
Export
ARCitect
Installation - Windows
Installation - macOS
Installation - Linux
QuickStart
QuickStart - Videos
ARCmanager
What is the ARCmanager?
Connect to your DataHUB
View your ARCs
Create new ARCs
Add new studies and assays
Upload files
Add metadata to your ARCs
Swate
QuickStart
QuickStart - Videos
Annotation tables
Building blocks
Building Block Types
Adding a Building Block
Filling cells with ontology terms
Advanced Term Search
File Picker
Templates
Contribute Templates
ISA-JSON
DataHUB
Overview
User Settings
Generate a Personal Access Token (PAT)
Projects Panel
ARC Panel
Forks
Working with files
ARC Settings
ARC Wiki
Groups Panel
Create a new user group
CQC Pipelines & validation
Find and use ARC validation packages
Data publications
Passing Continuous Quality Control
Submitting ARCs with ARChigator
Track publication status
Use your DOIs
Guides
ARC User Journey
Create your ARC
ARCitect QuickStart
ARCitect QuickStart - Videos
ARC Commander QuickStart
ARC Commander QuickStart (Experts)
Annotate Data in your ARC
Annotation Principles
ISA File Types
Best Practices For Data Annotation
Swate QuickStart
Swate QuickStart - Videos
Swate Walk-through
Share your ARC
Register at the DataHUB
DataPLANT account
Invite collaborators to your ARC
Sharing ARCs via the DataHUB
Work with your ARC
Using ARCs with Galaxy
Computational Workflows
CWL Introduction
CWL runner installation
CWL Examples
CWL Metadata
Recommended ARC practices
Syncing recommendation
Keep files from syncing to the DataHUB
Managing ARCs across locations
Working with large data files
Adding external data to the ARC
ARCs in Enabling Platforms
Publication to ARC
Troubleshooting
Git Troubleshooting & Tips
Contribute
Swate Templates
Knowledge Base
Teaching Materials
Events 2023
Nov: CEPLAS PhD Module
Oct: CSCS CEPLAS Start Your ARC
Sept: MibiNet CEPLAS Start Your ARC
July: RPTU Summer School on RDM
July: Data Steward Circle
May: CEPLAS Start Your ARC Series
Start Your ARC Series - Videos
Events 2024
TRR175 Becoming FAIR
CEPLAS ARC Trainings – Spring 2024
MibiNet CEPLAS DataPLANT Tool-Workshops
TRR175 Tutzing Retreat
Frequently Asked Questions
last updated at 2022-12-13
Addition of assays
⚠️ Make sure to close all isa.*.xlsx files before submitting a new command to the command line, as otherwise the information cannot be saved by the ARC Commander.
- An assay may consist of experimentally measured data together with experimental protocols.
- An assay folder structure can be created by using
arc a init
. Under assays an assay folder named after the assay identifier is created which includes:
- dataset
- protocol
- assay.isa.xlsx
- README.md
- An existing assay can be registered to the investigation by using
arc a register
.
- To create the folder structure and afterwards register the new assay
arc a add
can be used. This command combines init and register.
⚠️ An assay identifier also sets the folder name, so ensure to avoid special characters!
Field |
Description |
Input |
StudyIdentifier |
Name of the study in which the assay is situated |
|
AssayIdentifier (Mandatory) |
Name of the assay of interest |
GelBasedProteomicsWT |
MeasurementType |
A term to qualify the endpoint, or what is being measured (e.g. gene expression profiling or protein identification). The term can be free text or from, for example, a controlled vocabulary or an ontology. If the latter source is used the Term Accession Number and Term Source REF fields below are required. |
Proteomics |
MeasurementTypeTermAccessionNumber |
The accession number from the Term Source associated with the selected term. |
|
MeasurementTypeTermSourceREF |
The Source REF has to match one of the Term Source Name declared in the Ontology Source Reference section. |
|
TechnologyType |
Term to identify the technology used to perform the measurement, e.g. DNA microarray, mass spectrometry. The term can be free text or from, for example, a controlled vocabulary or an ontology. If the latter source is used the Term Accession Number and Term Source REF fields below are required. |
Mass spectrometry |
TechnologyTypeTermAccessionNumber |
The accession number from the Term Source associated with the selected term. |
|
TechnologyTypeTermSourceREF |
Identifies the controlled vocabulary or ontology that this term comes from. The Source REF has to match one of the Term Source Names declared in the Ontology Source Reference section. |
|
TechnologyPlatform |
Manufacturer and platform name, e.g. Bruker AVANCE |
AB Sciex TT6600 |
If no study identifier is given, a study is created with the assay identifier as study identifier. Instead of using the editor, the following command can be used:
arc assay add -a GelBasedProteomicsM21 --measurementtype Proteomics --technologytype "Mass spectrometry" --technologyplatform "AB Sciex TT6600"
Listing and inspecting registered assays
- Registered assays can be listed by
arc a list
.
- To get detailed information about a specific entry use
arc a get
. If no arguments are specified an editor will request study and assay identifier (mandatory) to print all registered information into the shell.
Editing assay information
- An assay can be edited using
arc a edit
.
- If no further arguments are specified an editor opens, that asks for the assay and study identifier that should be edited.
- If the assay exists, another editor opens with information already known for the respective assay. The required values can be edited.
- Instead of using the editor, the following command can be used. To circumvent editor pop ups, not
arc a edit
, but arc a update
must be used:
arc a update -s GelBasedProteomicsWT -a GelBasedProteomicsWT --technologyplatform "AB Sciex TT6600"
Removing assays
- An assay can be unregistered from the investigation by using
arc a unregister
.
- An assay folder structure can be deleted by using
arc a delete
.
- To both, delete the assay folder structure and unregister it from the investigation
arc a remove
can be used.
- Supply a study identifier and assay identifier to directly use these commands via command line, i.e.:
arc a unregister -s <study identifier> -a <assay identifier>
arc a delete -s <study identifier> -a <assay identifier>
arc a remove -s <study identifier> -a <assay identifier>
💡 To remove, unregister, or delete an assay both study identifier and assay identifier are required to ensure the correct assay is chosen.
Moving assays
- If an assay was mis-assigned to an incorrect study, or some assays should be grouped together (e.g. when a new study is created and some old assays would fit better to this new study), an assay can be moved from one study to another by using
arc a move
. After definition of the assay identifier together with old, and target study identifier, the assay is moved. If no study exist, that matches the given target study identifier, a new study is registered.
- Instead of using the editor, the following command can be used:
arc a move -s GelBasedProteomicsWT -a GelBasedProteomicsWT -t WTProteomics