.TH datalad-add 1 2016\-11\-10 "datalad-add 0.4.1"
.SH SYNOPSIS
 \fBdatalad\-add\fR [--version] [-h] [-l LEVEL] [-p {condor}] [-s URL/PATH] [-d PATH]
            [--to-git] [--nosave] [-r] [--recursion-limit LEVELS]
            [--if-dirty {fail,save-before,ignore}] [--git-opts STRING]
            [--annex-opts STRING] [--annex-add-opts STRING] [-J NJOBS]
            [PATH [PATH ...]]


.SH DESCRIPTION
Add files/directories to an existing dataset.
.br

.br
Typically, files and directories to be added to a dataset would be placed
.br
into a directory of a dataset, and subsequently this command can be used to
.br
register this new content with the dataset. With recursion enabled,
.br
files will be added to their respective subdatasets as well.
.br

.br
Alternatively, a source location can be given to indicate where to obtain
.br
data from. If no PATH argument is provided in this case, the content will
.br
be obtained from the source location and a default local name, derived from
.br
the source location will be generated. Alternatively, an explicit PATH
.br
can be given to override the default.
.br

.br
If more than one PATH argument and a source location are provided, the
.br
PATH arguments will be sequentially used to complete the source URL/path
.br
(be means of concatenation), and an attempt is made to obtain data from
.br
those locations.
.br

.br

.br
By default all files are added to the dataset's annex, i.e. only their
.br
content identity and availability information is tracked with Git.
.br
This results in lightweight datasets. If desired, the \-\-to\-git flag
.br
can be used to tell datalad to inject files directly into Git. While
.br
this is not recommended for binary data or large files, it can be used
.br
for source code and meta\-data to be able to benefit from Git's track
.br
and merge capabilities. Files checked directly into Git are always and
.br
unconditionally available immediately after installation of a dataset.
.br

.br
NOTE
.br
  Power\-user info: This command uses git annex add, git annex addurl, or
.br
  git add to incorporate new dataset content.
.SH OPTIONS
  PATH                  path/name of the component to be added. The component
                        must either exist on the filesystem already, or a
                        SOURCE has to be provided. Constraints: value must be
                        a string [Default: None]

  \fB--version\fR       show the program's version and license information
  \fB-h\fR, \fB--help\fR, \fB--help-np\fR
                        show this help message. --help-np forcefully disables
                        the use of a pager for displaying the help message
  \fB-l\fR LEVEL, \fB--log-level\fR LEVEL
                        set logging verbosity level. Choose among critical,
                        error, warning, info, debug. Also you can specify an
                        integer <10 to provide even more debugging information
  \fB-p\fR {condor}, \fB--pbs-runner\fR {condor}
                        execute command by scheduling it via available PBS.
                        For settings, config file will be consulted
  \fB-s\fR URL/PATH, \fB--source\fR URL/PATH
                        url or local path of the to be added component's
                        source. Constraints: value must be a string [Default:
                        None]
  \fB-d\fR PATH, \fB--dataset\fR PATH
                        specify the dataset to perform the add operation on.
                        If no dataset is given, an attempt is made to identify
                        the dataset based on the current working directory
                        and/or the PATH given. Constraints: Value must be a
                        Dataset or a valid identifier of a Dataset (e.g. a
                        path) [Default: None]
  \fB--to-git\fR        flag whether to add data directly to Git, instead of
                        tracking data identity only. Usually this is not
                        desired, as it inflates dataset sizes and impacts
                        flexibility of data transport. [Default: False]
  \fB--nosave\fR        by default all modifications to a dataset are
                        immediately saved. Given this option will disable this
                        behavior. [Default: True]
  \fB-r\fR, \fB--recursive\fR
                        if set, recurse into potential subdataset. [Default:
                        False]
  \fB--recursion-limit\fR LEVELS
                        limit recursion into subdataset to the given number of
                        levels. Constraints: value must be convertible to type
                        'int' [Default: None]
  \fB--if-dirty\fR {fail,save-before,ignore}
                        desired behavior if a dataset with unsaved changes is
                        discovered: 'fail' will trigger an error and further
                        processing is aborted; 'save-before' will save all
                        changes prior any further action; 'ignore' let's
                        datalad proceed as if the dataset would not have
                        unsaved changes. [Default: 'ignore']
  \fB--git-opts\fR STRING
                        option string to be passed to git calls. Constraints:
                        value must be a string [Default: None]
  \fB--annex-opts\fR STRING
                        option string to be passed to git annex calls.
                        Constraints: value must be a string [Default: None]
  \fB--annex-add-opts\fR STRING
                        option string to be passed to git annex add calls.
                        Constraints: value must be a string [Default: None]
  \fB-J\fR NJOBS, \fB--jobs\fR NJOBS
                        how many parallel jobs (where possible) to use.
                        Constraints: value must be convertible to type 'int'
                        [Default: None]
.SH AUTHORS
 datalad is developed by The DataLad Team and Contributors <team@datalad.org>.