The following information is used to troubleshoot issues with the BOOMi patron feed to FOLIO. Errors will be received via email to selected users. 

• The CIT Integration team created a self-service form to enable or disable various categories of users. Normally we want to exclude Sponsored NetIDs (“sponsored w/Exception”), per Michelle Hubbell, since they normally don't have CUL privileges, but we want them included during the summer when School of Critical Theory students are taking classes. To enable / disable, use applet at:
  Folio Integration or FOLIO Users Synchronization Integration 
• If an email comes in from CIT / Dell Boomi: "[error] Error in Sync Folio Users Data (main)"
  • Common scenario is a duplicate user record; either the barcode or the NetID is already assigned to someone else or is bad for some other reason. This error halts processing of the import and must be resolved for CIT to kick off the job again. The email says something like this (bio-demo details sanitized): 
    • An error has occured:
      Child Synchronous Process Call: Maintain Folio Users [execution-2560e664-f574-4a41-aa06-123984e0bbfe-2021.09.08(shape51)] call ended in error: com.boomi.process.ProcessException: Process terminating -- some documents reached an exception which is set to halt all documents: 422 Error message received from Http Server, Code 422: Unprocessable Entity, Request: { "username" : "abc123", "externalSystemId" : "004807333", "barcode" : "25510004807333", "active" : true, "personal" : { "lastName" : "Johnson", "firstName" : "Steph", "preferredFirstName" : "Steph", "email" : "abc123@cornell.edu", "addresses" : [ { "countryId" : "USA", "addressLine1" : "Hasbrouck Rd", "city" : "Ithaca", "region" : "NY", "postalCode" : "14850", "addressTypeId" : "93d3d88d-499b-45d0-9bc7-ac73c3a19880", "primaryAddress" : false } ], "preferredContactTypeId" : "002" } }, Response: { "errors" : [ { "message" : "This barcode has already been taken", "type" : "1", "code" : "-1", "parameters" : [ { "key" : "barcode", "value" : "25510004807333" } ] } ] } ; Caused by: Process terminating -- some documents reached an exception which is set to halt all documents: 422 Error message received from Http Server, Code 422: Unprocessable Entity, Request: { "username" : "abc123", "externalSystemId" : "004807333", "barcode" : "25510004807333", "active" : true, "personal" : { "lastName" : "Johnson", "firstName" : "Steph", "preferredFirstName" : "Steph", "email" : "abc123@cornell.edu", "addresses" : [ { "countryId" : "USA", "addressLine1" : "Hasbrouck Rd", "city" : "Ithaca", "region" : "NY", "postalCode" : "14850", "addressTypeId" : "93d3d88d-499b-45d0-9bc7-ac73c3a19880", "primaryAddress" : false } ], "preferredContactTypeId" : "002" } }, Response: { "errors" : [ { "message" : "This barcode has already been taken", "type" : "1", "code" : "-1", "parameters" : [ { "key" : "barcode", "value" : "25510004807333" } ] } ] }
    • To resolve: usually the wrong FOLIO Username (NetID) is assigned (sometimes their old Voyager user ID is mistakenly in the Username field). Verify the NetID in the CU Directory, then update it in FOLIO.
    • If that NetID has already been assigned to some other User record, it's possible this is a duplicate record for the same person. Deactivate the inactive record, change its NetID and barcode to something bogus (like adding "-delme") after the value, then correct the active record.
      • Ditto if the barcode has already been assigned to some other User record.
    • Try to re-execute the user FOLIO integration by clicking the User Management Integration Execution Control "Launch Applet" link on the Folio Integration page (CIT's). Notify CIT if there are further problems (per contact info on this page's parent page).
• Background / documentation on the patron data being supplied:

  • CIT relies on the CU_PERSON_DATA database which pulls data from multiple sources, in some instances, they have to rely on views of Peoplesoft used to feed Salesforce. Some columns in CU_PERSON_DATA (see synonym) view are clearly marked "WD_" but are not being used.

    Table documentation : https://cf.integrations.cornell.edu/Oracle%20Schema%20Docs/BOOMIPRDA%20(BOOMISEP)/schemas/BOOMI_FOLIO/tables1.html

    The actual updates come from this table after the compare between what Cornell has and what FOLIO has: https://cf.integrations.cornell.edu/Oracle%20Schema%20Docs/BOOMIPRDA%20(BOOMISEP)/schemas/BOOMI_FOLIO/tables/FOLIO_USERS_DELTAS.html

    Some questions can be answered by examining the source for CUPerson: https://cf.integrations.cornell.edu/Oracle%20Schema%20Docs/BOOMIPRDA%20(BOOMISEP)/schemas/BOOMI_FOLIO/views/CUPERSON.html

    The population of most of the reference tables is not included here. Basically, when investigating anomalies, they start with CUPerson and work backwards.