András Németh

Two notes on replication: - At least for me, the fields are only validated on submit, not when typing. - If the user is logged in, the name field is...

Resolved by https://github.com/zenodo/developers.zenodo.org/commit/8a55315f94e7cb37aa19d63ae39234ec852d834a - @slint

I'm having the same problem, but I'm getting an 500 Internal Server Error response.

Something that is definitely wrong is that the new file API uses a PUT request instead of the POST request of the old one. From the documentation: ```Python with open(path,...

Did you make the access token on the main or sandbox site? You can't use one on the other, see also #2249

Can you check whether the token has deposit:write scope? I've experienced some strange behavior that the scope does not save on creation in the sandbox.

As far as I've been able to find this feature comes from the ObjectResource class in invenio-files-rest. See https://github.com/inveniosoftware/invenio-files-rest/blob/563609bca4dd408532c07c50d44db80a461d21dc/invenio_files_rest/views.py#L449

If I understand correctly, the problem is that someone wants to download e.g. all treatment deposits that 3476748 has as a has-part relation. The upload filename is not modfied from...

The /api/records endpoint has these options and returns a JSON object: https://zenodo.org/api/records/?page=1&size=20&q=%2210.5852%2Fejt.2020.610%22 See also the API reference: https://developers.zenodo.org/#list36

For upload verification: Successful API (201 Created) upload operations should return a file deposition resource JSON object, which contains a `"checksum": "md5:xyz"` field that can be used for that purpose....