search

dataquest-dev / dspace-import

Blackbox tests for dspace repository
Other
0 stars 2 forks source link

UFAL/PY-license_resource_user_allowance old 10734 != new 41345 #85

Closed milanmajchrak closed 12 months ago

milanmajchrak commented 1 year ago

This issue is very connected with user_metadata issue: https://github.com/dataquest-dev/dspace-python-api/issues/86

The main reason of these issues is that the endpoint for importing the user metadata is called for every user metadata and in every call it is created license_resource_user_allowance record. How to fix: Call user metadata importing endpoint with LIST of user metadata instead of passing single user metadata in every request.

milanmajchrak commented 12 months ago

After the code modification there are still missing some user_metadata and license_resource_user_allowance. Actual status: user_metadata: 40401 imported instead of 41387 license_resource_user_allowance: 10577 imported instead of 10734

license_resource_user_allowance 7 records wasn't imported because of the same problem like here: https://github.com/dataquest-dev/dspace-python-api/issues/84

Some license resource mappings has reference to the bitstream which is already deleted and because of that it is not imported. I discovered that license resource mappings has reference to 600 bitstreams which are already deleted.
The data from the CLARIN-DSpace5 wasn't consistent.

150 records wasn't imported because they have token set to null, license_resource_user_allowance and user_metadata records cannot be imported with token = null

10734 - 157 = 10577 what is current status from the import. I think it is correct.