Closed B-Hartmann closed 2 years ago
A more sophisticated solution would be to have a notification that the supplementary metadata is not supported on the given DCOR instance and maybe automatically put them in the "comments" part or the "experimental detail: details" part, where unspecified information could be added in general, I guess and upload anyway.
Or just give a detailed error message and not upload.
The error message is misleading. These metadata supplements are probably not defined for DCOR-colab and they should be added. I also have to check whether any of that information got lost during the migration from the DCOR to the DCOR-colab instance.
Alright! I can see that the older, migrated data still has these metadata supplements, so that should be fine. Just keep me updated about adding the support for these supplements, then I can continue uploading once it's there :)
I fixed it and updated dcor_control
on DCOR-colab. Could you please check whether it works now?
It works! Thanks!
DCOR-Aid 0.11.8 dclab 0.46.0 upload to dcor-colab
When uploading data via the cli command
dcoraid.cli.upload_task
, and making sure I have access rights to the respective circle and collections, I get the following error message when uploading data:The .rtdc files get actually uploaded, but when DCOR or dcoraid try to change the metadata on the server, the error is thrown.
It seems that the additional supplementary resource metadata is the problem. This DCOR instance seems to not accept it. I can also not enter this information in the DCOR-Aid GUI when trying to do a manual upload.
How do we deal with this? Should I just not add supplementary resource metadata (at least when uploading data to the DCOR-colab instance)?