search

mattyschell / cscl-subaddress-matched

Creative Commons Zero v1.0 Universal
0 stars 0 forks source link

Find out plans for new subaddress columns #3

Closed mattyschell closed 3 years ago

mattyschell commented 3 years ago

Let's consolidate new and planned columns under this issue. These trickle down (verbally?) from some sort of CSCL governance body of experts.

Specifically, this repository needs to know if it is in the business of populating these columns, and if so, what is the timeline? Also, if so, what are the legal values?

See issue #2 for general discussion of handoff from this repository to CSCL.

  1. VALIDATION_DATE (date): "this will be used to indicate the last date the subaddress record was validated."
  2. UPDATE_SOURCE (text (50)): "current update source is only USPS Melissa data, but anticipated NG911 workflows may include other update sources."
  3. "House number" : "This column will be populated from the Melissa data. "
mattyschell commented 3 years ago

Final answers:

VALIDATION_DATE (date): will be the date that the CSCL manager performs updates in CSCL. We will ignore it in this repository.

UPDATE_SOURCE (varchar (50)): "USPS Melissa data" for everything output by this repository

USPS_HNUM (varchar(15)): Populate with HNUM from the melissa data. There is also a "corrected_house_number" in the geocoded data but it is either null or exactly identical to HNUM, it does not look useful