[Wactclc-alma] ctcLink users sync job failing - possible reasons

[Guidry, Wade]

I just responded to Dan directly about this. Here's that response, with any uer ID numbers retracted:

====================

Dan,

The parsing error in your patron load is happening because there is some corrupt data in the current load file.

I did some analysis, and found corrupted data in the following fields for the following users:

???????? - last name
???????? - last name
???????? - middle name

Some just needs to go into ctcLink and update these fields for these users. Basically, just delete the current values and type them back in again. That should fix the issue.

Meanwhile, I edited the file manually and reloaded into Alma, so you'd have fresh data in Alma to work with while you get those corrupted data points fixed.

I can't tell you how or why the data got corrupted.

Also, the error about a user being included in the load file twice just means just that... the reported users appear in the load file twice for some reason. When that happens, the first instance of the record loads, and the second one does not.

I'm guessing that what happens is that when the nightly copy from ctcLink (the production data) to datalink (the reporting data) happens, some users are being copied to datalink twice. So they end up in the Alma load twice.

I compared the duplicate records in the Alma load file being created, and they are identical. So, those duplicate occurrences aren't really causing any problems in Alma. I think it's more a symptom of some oddness in the way data is being copied to datalink.




Wade Guidry
Library Consortium Services Manager, WACTCLC
wadeg at bigbend.edu<mailto:wadeg at bigbend.edu>
(509) 760-4474
http://www.wactclc.org<http://www.wactclc.org/>

From: Wactclc-alma <wactclc-alma-bounces at lists.ctc.edu> On Behalf Of Martin, Melinda
Sent: Tuesday, September 21, 2021 12:38 PM
To: WACTCLC Alma Discussion <wactclc-alma at lists.ctc.edu>
Subject: Re: [Wactclc-alma] ctcLink users sync job failing - possible reasons

CAUTION: Originated outside our network. Do not click links or open attachments unless you validate the sender.


You probably have already looked at this, so disregard if I am duplicating...

Generally speaking, the "ERROR_MESSAGE=Invalid byte 2 of 3-byte UTF-8 sequence" occurs when the exported .xml document is not in UTF-8 and the receiving system (ALMA) is anticipating UTF-8.  Is it possible that there was a change in the export file?

The patron record error: ERROR_MESSAGE=The primary identifier is already taken by another user in this feed
                Is it possible that there are duplicates in the output file and that only one of them failed?

-Melinda


From: Wactclc-alma <wactclc-alma-bounces at lists.ctc.edu<mailto:wactclc-alma-bounces at lists.ctc.edu>> On Behalf Of Daniel Moore
Sent: Tuesday, September 21, 2021 11:21 AM
To: WACTCLC Alma Discussion <wactclc-alma at lists.ctc.edu<mailto:wactclc-alma at lists.ctc.edu>>
Subject: [Wactclc-alma] ctcLink users sync job failing - possible reasons

Hey all,

I'm working with one of the folks on our data team here at the college, and we're going through a few options, but I wanted to share this here in case anyone else has encountered it.

Since 9/16, our sync job for users from ctcLink has failed. The error logs are always the same. I've redacted some user information for privacy and am sharing a sample of the errors here: https://docs.google.com/spreadsheets/d/1TCA2J1l_Hnu6_XY1wU3-p465r9kgb8KeYOy-DxK5g5M/edit?usp=sharing<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fspreadsheets%2Fd%2F1TCA2J1l_Hnu6_XY1wU3-p465r9kgb8KeYOy-DxK5g5M%2Fedit%3Fusp%3Dsharing&data=04%7C01%7Cmelinda.martin%40scc.spokane.edu%7Cd2ba5622b44448517cea08d97d2cba4b%7C4dedfefa6bd04442a06c98aed0b4b8da%7C1%7C1%7C637678453332772330%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=RkIykwzRtYVIsNW%2F5E%2FMmuoIzZHAzJRZ8AYNCVFep1Y%3D&reserved=0>

First, my colleague discovered two errant commas in the output file and it was a strong candidate for the cause of this validation error. However, the job today ran and still failed after the changes were made. I think there might be something with those user records too - it's the same two user IDs that are rejected for each job, though it's unclear if that's the cause or another consequence of the failure in the source file.

Because this job is failing, our circulation manager is manually updating all student/faculty records in the moment the loan is processed or after a loan report is delivered (we're circing technology and receiving outputs on circs from that team periodically).

Does anyone have any other ideas or suggestions that I should investigate, or things I should forward on to my IT liaison to investigate?

All the best,

Dan Moore
Systems and Collections Librarian
Edmonds College Library
(425) 640-1526
Pronouns: he, him, his
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ctc.edu/pipermail/wactclc-alma_lists.ctc.edu/attachments/20210921/678a79de/attachment-0002.html>