Patrons lose cards/they get destroyed. We also do card campaigns and they want to replace their cards for fun. They need to be able to keep their patron account features and information without relying on it being attached to a card barcode that can easily be lost.

Or maybe it's a difference between Polaris and Sierra? We're a Polaris library and Vega is using the barcode, not the patron ID (primary key) from the Polaris database.

Ours is definitely based on barcode not pnnumber like some have suggested. We just tested it. So are there different releases operating differently on this issue?

I believe Vega accounts are tied to the pnumber. I tried to transfer one of my staff cards that had been used to create showcases early on by swapping out the barcode and it didn't work since the content was tied to the pnumber, not the barcode - which is good for the reasons noted in these comments!

I just tested this (in case I was remembering this wrong). I added a new barcode to an existing patron record. When I signed in to vega with the new barcode, I had access to previously created lists and still had showcase permissions.

We've also experienced a potential bug regarding misaligned patron barcodes from Polaris to LX starter which causes patrons to not receive outgoing notices. It would be excellent to see Polaris and Vega sync by Patron ID rather than barcode.

I agree with everything that's been said.

This is a vital service, for all the reasons already shared!

Any patron information shouldn't be attached to the barcode, but to the patron id number. That way it will move with the patron's account within our consortium, regardless of whether the patron moves or needs to replace a lost card.

Patrons lose or replace their cards all the time. We also give the patrons the option to get a new card when theirs wears out. Lists and other data should transfer with the patron without any staff involvement.