Check that all media and tables are available before start upload

[hagenw]

Make sure we are not starting a publishing process that will fail and leave behind a corrupted database.

[hagenw]

I think this might be no longer relevant as we now support that you cancel a publishing process in between and continue afterwards. @frankenjoe: correct?

[frankenjoe]

I think this might be no longer relevant as we now support that you cancel a publishing process in between and continue afterwards. @frankenjoe: correct?

Yes, publish() skips files that are already on the backend, but only if the checksum matches. We need this check to verify that files have been completely uploaded. I.e. it may fail if the user does not have rights to overwrite files on the backend.

[hagenw]

The original issue is solved, but we still have

I.e. it may fail if the user does not have rights to overwrite files on the backend.

This means if a user has only write permissions on the backend she can run succesfully audb.publish(), but it might fail if she does not have overwrite permissions, cancel audb.publish() in between and restart it, correct?

[hagenw]

I see three solutions:

• state in the documentation that a user needs write and overwrite permissions on the backend for publish()
• catch the error from the backend and raise a custom error stating that overwrite permissions are needed
• do nothing and stay with the current implementation that will simply present the error message from the backend to the user

[frankenjoe]

Yes, maybe we could mention in the documentation that restarting publish() after it was canceled may require overwrite permissions.