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
Adding a LICENSE to your ARC
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
Working with branches
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
CEPLAS ARCify your research project
Frequently Asked Questions
last updated at 2023-06-28
About this guide
In this guide we show you how to keep files from syncing to the DataHUB. This can help to keep large intermediate, sensitive or unpublished data from uploading to the DataHUB.
Before we can start
☑️ You have created an ARC before using the ARC Commander
☑️ The latest version of the ARC Commander is installed on your computer
☑️ You have a DataPLANT account
☑️ Your computer is linked to the DataHUB via personal access token
The .gitignore file
Every ARC comes with a special file called .gitignore
, that resides in the root of your ARC. Files and folders listed in your ARC's .gitignore
will be ignored by the ARC's version control system. That means changes to those files will not be tracked by ARC tools (e.g. ARC Commander or ARCitect) nor will the files be synced to the DataHUB.
💡 If .gitignore
does not exist in your ARC, you can simply create it in your ARC's root using a text editor or the ARCitect.
💡 By default, this file is hidden from your File Explorer (Windows) or Finder (macOS).
💡 Since files added to .gitignore
on one machine will not be synced to the DataHUB, they will also become available on another machine, to where you sync your ARC.
⚠️ If a file in your ARC was already synced to the DataHUB, adding it to .gitignore
will only keep it from future syncs, it will however not remove the existing file.
Adding files to .gitignore
- Open your ARC in the ARCitect or in your File Explorer (Windows) or Finder (macOS)
- Add a new file
my-personal-notes.txt
or folder intermediate-results
to the ARC
- Open
.gitignore
via ARCitect or a text editor.
- Add a new line
my-personal-notes.txt
or intermediate-results/
at the end of the file
- Save and close the file.
- Sync the ARC via ARC commander or ARCitect.
- Check your ARC in the DataHUB, to see that the file
my-personal-notes.txt
or folder intermediate-results/
does not exist there.
Allowing files to sync
If at some point you want the ignored file or folder to sync, you can simply remove the respective line from your ARC's .gitignore
file.
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
.