You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the latest changes we would like to re-test the harvester after the provided feedback - this will enable us to switch the task on production
run the full task for thesis type of record, with since argument: 2025-05-15
check thoroughly the types of errors we are receiving. Which errors are code errors and which are metadata related? - evaluate the code errors and let's review the list together
check if we are still getting conflicts on the publication date. Is publication date correctly assigned after the change?
verify the assignment of other metadata fields. Do they make sense?
Evaluate overall user experience for harvester reports - are they easy to understand and act on?
add a loader to this button (or both buttons) because it takes long time for the view to load, the user might think somethign is broken and click many times (I did):
create another task assigned to the librarians, following Thesis Harvester - feedback and discussion #765 with instructions on how to test (with new batch of tested records), specifically mention what we changed - most important stuff is for them to evaluate the metadata assignment changes, so the removal of conflict on publication date
fromt he latest report for the record hzvya-n2g27 there is a bug in assigning CDS report number - when it starts with CERN- it should be assigned in identifiers, not related identifiers
After the latest changes we would like to re-test the harvester after the provided feedback - this will enable us to switch the task on production