Daniel's Law Registry Matching and Redaction
Description
Daniels law requires DEP to mask personal information of judges, law enforcement offices, etc. from the public. May require numerous changes to multiple data systems to address law.
Project Justification
This is a requirement from the Daniel's Law legislation
Attachments
Activity
Show:
Active
Add watchers
Details
Sponsoring Leadership Area
Div. of Information Technology
Sponsoring Leadership Area's Priority
None
Program Area Lead(s)
Matt Coefer
DOIT technical lead(s)
Mike Matsko, Julie Lin
All Involved Leadership Areas
Div. of Information Technology
Created: 7 October 2021, 21:10
Updated:
17 October 2023, 15:14
UAT ended 10/16/2023. >20,000 DCA records loaded (NJEMSDev). 350 exact matches found and auto redacted, 3,000 partial matches being reviewed by Matt C.. Production deployment Package being put together by CGI, deploy to JEMR first.
NJEMS tables with person/address data have been identified, queries to match DCA list names/addresses have been developed and tested, and are being run by Matt Coefer to use for redaction purposes.
Initial DOIT Internal meetings held 1/10/2023 and 1/19/2023. Follow-up meeting set for 2/14/2023
Pete asked during the DOIT manager’s meeting 10/26 about any actions. Only Angela has been involved through the NJOIT pulling of parcel info. Angela maintains an internally available layer for staff use. Other governments had an issue with the loss of the publicly available sets.
There is an active tool https://danielslaw.nj.gov/Default.aspx?ReturnUrl=%2f for people to sign up to have the info redacted. Thousands have signed up. Agencies will soon be getting and must figure out how to find and redact all the records for those signed up (Phase 2). A series of meetings on phase 2 to commence and expecting to include OPRA leads. DOIT probably wants a representative there to hear the issues.
Could be a lot of sources to be scoured including Dataminer reports, Highview images. We will need to keep our original data and mask it to the public.
Kurt suggests a x-ref database of IDs tied to people info, and then check this DB and block those with th hit when serving info.