Import API example in the guide needs improvement

[PaulBoon]

I am experimenting with the import API and I use the provided example json.

http://guides.dataverse.org/en/latest/api/native-api.html#import-a-dataset-into-a-dataverse

First of all I need to use a 'resolvable' DOI otherwise import fails with
"Provided PID does not exist. Status code for GET 'https://doi.org/ZZ7/MOSEISLEYDB94' is 404."}
If I change the DOI to one that does resolve the import works, but I cannot add files to it:
"File upload via HTTP disabled since this dataset already contains a package file."
or on the UI
"HTTP upload is disabled for this dataset because you have already uploaded files via rsync. If you would like to switch to HTTP upload, please contact DataverseNL support."

This 'package file' use in the import example complicates things or at least needs some more explanation or references.

[djbrooke]

Hey @PaulBoon - would you be willing to put up a PR to address this?

[PaulBoon]

Hi @djbrooke, I could do that, but I don't think I have much to contribute.
Where it states: The import will fail if no PID is provided, or if the provided PID fails validation. we could add that the PID must also resolve.
Replacing the example json is a bit more involved, I don't have a good example because I just removed the files to get my test going. Maybe someone else has a good replacement for that example or knows how to best reference the packaging.

[pdurbin]

@PaulBoon does the migration API work better for you?

https://guides.dataverse.org/en/5.12/developers/dataset-migration-api.html

Also, it's weird that you're seeing those references to rsync and "package". These are part of the rsync feature that we're thinking about deprecating and removing:

• remove rsync from guides (deprecated) #8985