Turn off duplicate detection for patron emails (PAPI)

Polaris
1

Hello!

I am working on a script to import a bunch of patron records into Polaris. We allow patrons to use duplicate emails across records and this is tripping up my script - I can’t bypass duplicate detection with the API as far as I know. Does anyone know if there is a setting to turn off email duplicate detection?

Thanks!

-Somalia Jamall, Jacksonville Public Library System Admin

2

That is a configuration option, you can find out more here: Polaris Staff Client Help

Don’t forget you might have to restart your PAPI service after making the change as it might need to pickup that setting.

3

Hi Wes!

Thanks for all your advice! We tried that and are still running into the same issue even, after resetting things. This is what our settings look like, can you tell if we’re missing anything?

Settings Screenshot 1
Settings Screenshot 2

4

The patron duplicate detection criteria settings are found under Parameters > Patron Services > Duplicate Detection Options. There you can indicate that email address should be checked or not.

Saying that, though, through discussion with Polaris recently and testing we found out that during an API patron registration the dupe detection won’t check for duplicate email addresses, even if the dupe detect options indicate to check it. So I’m curious about what error you’re seeing (or if others have a different experience with it working)…

5

I would also say that you should verify at the branch and library levels and system level what the settings are to see if they are different and that might be why is appears PAPI isn’t “picking them up.”

6

Hello Jason!

That is wild, because it’s definitely blocking when the email address is the same as an existing patron. We are using this endpoint: PatronRegistrationUpdate Version 2

We are getting the below response. It’s complaining about the name being a duplicate but even if we change the name it says the same thing. The only way to get it to work with the API is if we change the email too, which of course is not a reasonable solution.

<PatronRegistrationCreateResult xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
  <PAPIErrorCode>-3528</PAPIErrorCode>
  <ErrorMessage>Duplicate patron name is specified</ErrorMessage>
  <Barcode>
  </Barcode>
  <PatronID>0</PatronID>
  <StatisticalClassID>0</StatisticalClassID>
</PatronRegistrationCreateResult>

Thank you everyone for all your input! It is much appreciated.

7

Sounds like it is time to open up a support ticket to submit it as a potential bug.

I would also see if you can get someone to try it in Leap, and the Desktop Client to see if the behavior is the same.

1 Like
8

I would love to know the resolution to this when/if there is one!

Aaron