-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
uploadDataPackage should support 'common' objects #251
Comments
It would be great to get this implemented - we share species and site tables across multiple datasets and currently do not have a way to upload these datasets in R unless we create different identifiers for the same table; we would prefer not to do that if possible! |
Existing DataONE objects can now be included into new DataPackages. The workflow to use is:
A minor fix was made to |
A typical DataONE use case is to have the same data object in multiple packages.
It should be possible to download a package using
getDataPackage()
, add a package member for a pid that already exists in DataONE (in another package, for example), and upload the package usinguploadDataPackage()
. In this case,uploadDataPackage()
should not try to upload the 'common' data object to DataONE again, and should include this new package member in the resource map.The text was updated successfully, but these errors were encountered: