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
ARC Commander Manual
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 Manual
Installation - Windows
Installation - macOS
Installation - Linux
QuickStart
QuickStart - Videos
ARCmanager Manual
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 Manual
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 Manual
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-08-10
A tool to make FAIR RDM easy
The ARC Commander is one of two central DataPLANT tools designed for convenient interaction with your ARC (the other one being SWATE).
It supports you in many actions on files within your ARC enabling you to sort, associate and keep track of your files.
The major function of the ARC Commander is to set up the ARC directory and put it under version-control for you. The ARC Commander creates the directory structure with the root directories "studies", "assays", "runs", and "workflows" (see ARC for details). According to the design of your project, you can use the ARC Commander to create study and assay sub-directories and add the associated details and data files. While setting up the root directory structure, the ARC Commander initializes your ARC as a git repository, allowing you to track changes of your ARC and easily back-up and synchronize it with the DataHUB. This includes an efficient mechanism to keep track of your large data files. The ARC Commander makes it straight-forward to download shared ARCs from the DataHUB for collaboration.
Apart from managing the ARC as a whole in terms of file handling, the ARC Commander supervises the integrity and connections between files of your ARC. It ensures that the ARC is intact following the ARC specifications as well as the ISA model to provide machine-readability of metadata. By (automatically) registering your studies and assays including their associated meta(data) files in the isa.investigation.xlsx
registry file, the ARC Commander makes the resources in your ARC identifiable and findable. It would also warn you about possible inconsistencies, such as duplicate ISA metadata files (e.g. every ARC stores only one isa.investigation.xlsx
) or studies and assays that may have been added manually and not registered, yet.
What the ARC Commander does not do
Unless you actively request it to, the ARC Commander does not delete, modify or move files within your ARC. While it may help with suggestions, the ARC Commander will not guess your intentions or override your decisions. For instance, the ARC Commander will not search any (ISA) metadata or other data files in your ARC and move them into the intended folders. If such files exist somewhere in your ARC, they will simply be ignored as "additional payload" (see ARC specifications). The ARC Commander does not operate / manage your ARC automatically. You have the full control over all actions. Whenever you decide to add or link new (meta)data in your ARC or synchronize it with the DataHUB, you can do so with a few commands.
Do I have to use the ARC Commander?
No. As with most tools and services developed in DataPLANT, you are not obliged to use the ARC Commander to benefit from DataPLANT's support in FAIR RDM.
However, we'd highly recommend to check it following the ARC Commander QuickStart.
The alternative would be to
- ...create the directory structure from scratch for every ARC?
- ...properly link all your isa.* metadata and files by hand?
- ...remember where to put what metadata information?
- ...learn a bunch of git and git-lfs commands by heart?
- ...
How does it work?
The ARC Commander runs on current Windows, Mac and Linux operating systems. At the moment, the tool is solely designed as a CLI-based software. For the future, the DataPLANT developers work on a GUI version, making it even more intuitive for all users.
For details, please
DataPLANT Support
Besides these technical solutions, DataPLANT supports you with community-engaged data stewardship. For further assistance, feel free to reach out via our
helpdesk
or by contacting us
directly
.