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-13
Challenge
- No direct access rights to the main branch (which can be handled via the DataHUB) or
- Many people working on the same repository, making direct pushing to main branch chaotic.
Solution
Work on a second branch and contribute to the main branch using merge/pull requests
Workflow
- Use
arc get to get the main branch of the repository.
- Work on the ARC.
- Use
arc sync -b SecondBranchName.
💡 This will create a commit with your newest changes and push the commit to a new branch with the given name. When you finished editing your ARC, you can merge your progress into the main branch.
Git status
You can check on which branch you are currently working on and the status of this branch by using
git status
💡 This will print to the console, if you are behind, up to date, or ahead of the main branch.