search

culibraries / ir-scholar

CU Scholar - Institutional Repository Hyrax
0 stars 0 forks source link

Error when updating submission #79

Closed mbstacy closed 3 years ago

mbstacy commented 3 years ago

Reporting another case of the "Something went wrong" error on CU Scholar when trying to update a submission. Let us know if we should keep this ticket running with each instance of the error, submit a new ticket each time, or something else.

Service Now Issue

Submitted By: Ryan Calliet

Acceptance Criteria:

  1. Cron Job restart backend process (fedora/scholar-workers/solr)
  2. Check encoding text
  3. With the recent issue with IR will add restart to all backend processes
mbstacy commented 3 years ago

Just a follow-up on the investigation of recent problems within CU Scholar: The SOLR index can only accept character encoding of UTF-8. I was trying to figure out what the offending characters and encoding issues were part of the abstract. I attempted to copy from Teams message(above) and paste it into Word. Word crashed every time that I tried to save the abstract. So, Samvera tries to convert to UTF-8, but the Abstract text was corrupted or did not have the appropriate encoding. I use Python to encode strings, and that is how I added the new item with the correct/clean Abstract. If multiple CU Scholar submissions have this problem, we can work to set up a workaround. If this is a rare occurrence where the Edit metadata is different from the Display Page, please send it to me, and I can check if the Abstract needs to be adjusted. We can have a further discussion at the upcoming meeting.

mbstacy commented 3 years ago

@andrewjohnson314 @ryancaillet I have updated this issue to reflect last week's issue with the scholar backend workers. The new acceptance criteria are to perform a restart of all backend processes, not just Fedora.

mbstacy commented 3 years ago

Backend IR modules all restart on Sunday at 11 PM (0 23 0). Deployment cronjobs tested in the test cluster and production cluster.