Thanks for the feedback Aaron, I will try and make it flexible, keeping it mind your need :) Le ven. 22 nov. 2019 à 00:47, asakovich@hmcpl.org <asakovich@hmcpl.org> a écrit :
Jonathan,
First of, wow, thank you SO much for taking on this task!
Option 1 looks really good to me. One thing, however: we’re starting to get into demographic analysis, so having a zipcode in the borrowers_anonymized table would be hugely beneficial. We’re generating choropleth maps, and borrower.zipcode provides just the right level of detail for our needs. I don’t know how well that would mesh with the overarching GDPR requirements, however (my guess: not well).
Here’s a sample map that we can get right now; however, this requires us to pull card numbers, then extract the borrowers.zipcode, and then report the data out without the card number. Painful.
Again, thanks for taking on this task! Aaron -- Aaron Sakovich Internet and Technology Services Manager
Huntsville-Madison County Public Library 915 Monroe Street | Huntsville, Alabama 35801 | https://hmcpl.org/