Fundamentals
Research Data Management
FAIR Data Principles
Metadata
Ontologies
Data Sharing
Data Publications
Data Management Plan
Version Control & Git
Public Data Repositories
Persistent Identifiers
Implementation within DataPLANT
Annotated Research Context
User Journey
ARC Commander
QuickStart
QuickStart (experts)
Swate
QuickStart
Walk-through
Best Practices For Data Annotation
DataHUB
DataPLAN
ARC Commander Manual
Setup
Installing Dependencies
Configure Git
Installing the ARC Commander
Windows
MacOS
Linux
DataHUB Access
Before we start
Central Functions
Initialize
Clone
Connect
Synchronize
Configure
Branch
ISA Metadata Functions
ISA Metadata
Investigation
Study
Assay
Update
Export
Swate Manual
Setup
Installing Swate
Browser
Desktop, via installer (beta-stage)
Desktop, manually (recommended)
MacOS
Organization-wide
Core Features
Annotation tables
Building blocks
Building Block Types
Adding a Building Block
Using Units with Building Blocks
Filling cells with ontology terms
Advanced Term Search
Templates
Contribute Templates
File Picker
Expert Features
ISA-JSON
Frequently Asked Questions
Teaching Materials
DataPLANT Overview
Big Picture
ARC structure
ARC Demo
last updated at 2022-12-20
Some users might want to use different signatures for different repositories, e.g., developing software on GitHub and working on ARCs on the DataHUB. Besides your global git configuration, you can store the information you want to use for editing ARCs within the ARC Commander config:
arc config set -g -n "general.gitname" -v "Name of choice"
arc config set -g -n "general.gitemail" -v "Email of choice"
To transfer the information from the global ARC Commander config to the local git config of the ARC use
arc config setgituser
💡 This will automatically transfer the info stored globally in the ARC Commander config to the local git config of the ARC.