Page Comparison

...

In-Flight Requests: Identify and address any in-flight requests associated with the virtual patron before deletion.
Data Retention Policy: Establish a clear data retention policy to determine how long virtual patron records should be retained before deletion.
Backup and Recovery Strategy: Develop a robust backup and recovery strategy to minimise data loss risks associated with deletion.
Testing and Pilot: Implement a phased approach with rigorous testing and a pilot program to evaluate the feasibility and impact of virtual patron deletion.

Outstanding questions:

How can we ensure that the correct UniqueId is used from the list of UniqueId's that DCB stores to find the virtual patron? I.e., the UniqueId stored on the virtual patron record matches the one DCB chooses to search by.
Are local patron IDs reused in Polaris? If so, could this lead to matching the wrong patron?
Which field in the patron record would be best suited for storing our chosen unique identifier? Is the PATNL field a valid option? Which is currently in use.
If multiple virtual patrons are found, what criteria should we use to identify the correct one?
What cross-checking criteria can we apply to minimise the risk of false positives?