iqss / dataverse-uploader Goto Github PK

Currently the DELETE flag can be set to TRUE or FALSE. Would it be possible to target a specific folder in the dataset to skip if the DELETE flag is set to TRUE?

A common use case would be to upload code files from GitHub to Dataverse, but add data files separately. When a new version of the code is released and triggers an update of the Dataverse dataset, it would be great to have all of the files from GitHub be deleted and the new files uploaded to the dataset (as how it currently works), but allow the user to add a flag to the YML file targeting folders to NOT delete. This allows the user to avoid having to upload the same data files to the dataset for each version update.

Hi,

thanks for contributing this GitHub action, it's a great extension to Dataverse!

We made some test with version 1.2 (available on GitHub Marketplace) and found a small problem: According to documentation on https://github.com/marketplace/actions/dataverse-uploader-action, the parameters "DELETE" and "PUBLISH" are not required and default values are used. However, when leaving them out, we get the following error whenever the action is triggered:

$GITHUB_REPOSITORY -d ""  -r ""  -p "" 
usage: dataverse.py [-h] [-d DIR] [-r {True,TRUE,true,False,FALSE,false}]
                    [-p {True,TRUE,true,False,FALSE,false}]
                    token server doi repo
dataverse.py: error: argument -r/--remove: invalid choice: '' (choose from 'True', 'TRUE', 'true', 'False', 'FALSE', 'false')
Error: Process completed with exit code 2.

This is the yml file:

on: 
  push:
  workflow_dispatch:
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Send repo to Dataverse 
        uses: IQSS/[email protected]
        with:
          DATAVERSE_TOKEN: ${{secrets.DATAVERSE_TOKEN}}
          DATAVERSE_SERVER: https://edmond.mpdl.mpg.de
          DATAVERSE_DATASET_DOI: doi:10.17617/3.TF31SS

When adding both parameters to the YML file, it works fine.

Since publishing an uploaded dataset has permanent implications, it is safer to default PUBLISH to FALSE, and require an explicit choice to make it TRUE.

While making the v1.5 release I learned a couple things for next time:

• Before making a release, we should bump the version in each place it appears in the README.
• When making the release, there's a box to check to also release to GitHub Marketplace.

Overall, it was quite straightforward.

Two tasks:

• rename DOI to more generally used PID
• when DOI is used make it work with both doi: prefix and without it.

Dear,
Can this uploader also been used inside GitLab?
Kind regards

We just merged this pull request:

• #19

... and as discussed on Zulip, we'd like to make a release.

@atrisovic would you be able to walk me through this? No rush! Thanks!

Would it be possible to enable the "PUBLISH" option to work with the Submit-for-Review workflow? Currently, if user permissions are set to "Contributor," they do not have the ability to publish and the Action fails when "PUBLISH: True."

Could a, for example, "PUBLISH: Submit_for_review" be created?