More DOIs fail to push to s3
Background
Fixed similar issue with #896 (closed),
More general fix needed for the scheduled pusher required for DOIs with other characters in their name. While the S3 API claims it can accept any valid UTF-8 in the metadata, the DOI 10.2741/Ortéga
(citation id 27277865) was causing problems.
Observed behavior
Errors in Sentry and logs related to bad DOI
Expected behavior
Skip bad DOIs that cause trouble in metadata for S3 puts.
How urgent
Definition of ready
-
Product owner: @ppolischuk1 -
Tech lead: @myalter / @dtkaczyk -
Service:: label applied -
Definition of done updated -
Acceptance testing plan: -
Weight applied
Definition of done
-
Unit tests identified, implemented, and passing -
Code reviewed -
Available for acceptance testing via a staging URL, or otherwise -
Consider any impacts to current or future architecture/infrastructure, and update specifications and documentation as needed -
Knowledge base reviewed and updated -
Acceptance criteria met -
Doi with citation id 27277865 pushed to S3 -
no more S3Exceptions in log/sentry due to clob pushes
-
-
Acceptance testing passed -
Deployed to production
Notes
Edited by Patrick Polischuk