Successfully added sibling dataverse and push to parent dataverse

[xuyg16]

Previous Issues

• DataLad/Dataverse linking and push sometimes ran from the repository root instead of the BIDS dataset directory.
• This caused issues like:
  • special remote dataverse-storage already existing in the wrong repo
  • datalad push --to dataverse failing with “Unknown push target 'dataverse'”

changes

• datalad_create.py: used Dataset(...).is_installed() to do reliable check and to make sure Datalad dataset will be created.
• link_datalad_dateverse.py added --existing reconfigure to make repeated runs more stable. Also added cwd=(...)
• upload_to_dataverse.py used cwd=(...) to specify the correct target dir

Current issues

• error message: [DATALAD-ANNEX] fatal: couldn't find remote refs (repository deposit does not exist, or is inaccessible
• maybe it is the API problem.

[behinger]

I ran into a similar issue, I had to change:
dl.Dataset(dataset_path).status()

and later I chnaged

    os.chdir(dataset_path) # bug in datalad that requires to be in the same folder to save the datalad thingy
    dl.save(path = dataset_path, message=message)
    

maybe something with datalad api changed that it now needs to be in the same folder?