Changes

Jump to navigation Jump to search
no edit summary
{{Project|Has project output=Data|Has sponsor=McNair ProjectsCenter
|Has title=Patent Data Restructure
|Has owner=Marcela Interiano, Sonia Zhang,
|Has start date=201701
|Has deadline=201705
||Has keywords=Patent,Data|Has project status=ActiveSubsume|Does subsume=Patent Data (Wiki Page), Patent Data Cleanup - June 2016, Patent Data Extraction Scripts (Tool), USPTO Bulk Data Processing,
}}
In order to restructure the current patent dataset, the data requires rigorous cleaning. The primary areas for improvement are:
==Data Cleanup Progress==
 
The tables that currently comprise the assignment data are as follows.
 
Table "public.ptoassignment"
Column | Type | Modifiers
-------------------------+------------------------+-----------
reelno | integer |
frameno | integer |
last_update_date | date |
purge_indicator | character varying(2) |
recorded_date | date |
correspondent_name | character varying(500) |
correspondent_address_1 | character varying(500) |
correspondent_address_2 | character varying(500) |
correspondent_address_3 | character varying(500) |
correspondent_address_4 | character varying(500) |
conveyance_text | character varying(500) |
 
Table "public.ptoassignee"
Column | Type | Modifiers
-----------+------------------------+-----------
reelno | integer |
frameno | integer |
name | character varying(500) |
addrline1 | character varying(500) |
addrline2 | character varying(500) |
city | character varying(500) |
state | character varying(500) |
country | character varying(500) |
postcode | character varying(80) |
 
Table "public.ptoassignor"
Column | Type | Modifiers
----------------+------------------------+-----------
reel_no | integer |
frame_no | integer |
assignor_name | character varying(500) |
execution_date | date |
 
Table "public.ptoproperty"
Column | Type | Modifiers
-----------------+------------------------+-----------
reelno | integer |
frameno | integer |
documentid | character varying(20) |
country | character varying(500) |
kind | character varying(3) |
filingdate | date |
invention_title | character varying(500) |
 
Table "public.ptopatentfile"
Column | Type | Modifiers
------------------------+-----------------------+-----------
reel_no | integer |
frame_no | integer |
action_key_code | character varying(10) |
uspto_transaction_date | date |
uspto_date_produced | date |
version | numeric |
 
This section explains the series of steps that were taken to clean and to take note of problems in the data. Additionally, this section includes the codes for new tables that combine patent properties from different tables in the original assignment data.
 
===Table Cleanup===
 
The five original assignment tables contain duplicates that were deleted. Five new tables were made and used as templates for building new tables.
 
Ptoassignmentnd Table:
 
SELECT COUNT(*) FROM ptoassignment;
--8676322
 
DROP ptoassignmentnd;
CREATE TABLE ptoassignmentnd AS
SELECT reelno, frameno, max(last_update_date) as last_update_date, purge_indicator, recorded_date, correspondent_name,
correspondent_address_1, correspondent_address_2, correspondent_address_3, correspondent_address_4, conveyance_text
FROM ptoassignment GROUP BY reelno, frameno, purge_indicator, recorded_date, correspondent_name, correspondent_address_1,
correspondent_address_2, correspondent_address_3, correspondent_address_4, conveyance_text;
--6988575
 
Ptoassigneend Table:
 
SELECT COUNT(*) FROM ptoassignee;
--8983280
 
DROP ptoassigneend;
CREATE TABLE ptoassigneend AS
SELECT DISTINCT reelno, frameno, name, addrline1, addrline2, city, state, country, postcode FROM ptoassignee;
--7234001
 
Ptoassignornd Table:
 
SELECT COUNT(*) FROM ptoassignor;
--20062463
 
DROP ptoassignornd;
CREATE TABLE ptoassinornd AS
SELECT DISTINCT reel_no, frame_no, assignor_name, execution_date FROM ptoassignor;
--16126903
 
Ptoproperty_cleaned Table:
 
SELECT COUNT(*) FROM ptoproperty;
--65214396
 
DROP TABLE ptoproperty_cleaned;
CREATE TABLE ptoproperty_cleaned AS
SELECT DISTINCT reelno, frameno, documentid, country, kind, filingdate, invention_title
FROM ptoproperty;
--8696149
 
Ptopatentfilend Table:
 
SELECT COUNT(*) FROM ptopatentfile;
--8676317
 
DROP ptopatentfilend;
CREATE TABLE ptopatentfilend AS
SELECT DISTINCT reel_no, frame_no, action_key_code, uspto_transaction_date, uspto_date_produced, version FROM ptopatentfile;
--7159725
===Patent Number Cleanup===
The goal is to only have assignment records on utility patents. The patents in ptoproperty include alphanumerics , which represent reissue and design patents as well as mistakes in the data input. Additionally, the documentids include application numbers or ids and publication numbers. The ptoproperty table stores the patent ids as character strings.
First the duplicates were dropped from the ptoproperty table creating ptoproperty_cleaned.
SELECT COUNT(*) FROM ptoproperty WHERE documentid LIKE 'D%';
--1128247
 
Finally, all letters were removed from the data, resulting in the final version of ptoproperty_cleaned.
 
The ptoproperty_cleaned table contains application numbers, publication numbers, and patent numbers. The patents may also have two distinct publication numbers based on the year in which it was published. Based on length of documentid, the three types of id numbers were separated into three separate tables.
 
DROP TABLE ptoproperty_patent;
CREATE TABLE ptoproperty_patent AS
SELECT * FROM ptoproperty_cleaned WHERE length(documentid) = 7;
--8696149
ALTER TABLE ptoproperty_patent RENAME COLUMN documentid TO patentno;
 
DROP TABLE ptoproperty_app;
CREATE TABLE ptoproperty_app AS
SELECT * FROM ptopropertynd WHERE length(documentid) = 8;
--11577028
ALTER TABLE ptoproperty_app RENAME COLUMN documentid TO appno;
 
DROP TABLE ptoproperty_pub;
CREATE TABLE ptoproperty_pub AS
SELECT * FROM ptopropertynd WHERE length(documentid) = 11;
--6217864
ALTER TABLE ptoproperty_pub RENAME COLUMN documentid TO pubno;
 
All three tables contain the following information and differ only on the type of patent id.
 
Table "public.ptoproperty_patent"
Column | Type | Modifiers
-----------------+------------------------+-----------
reelno | integer |
frameno | integer |
documentid | character varying(20) |
country | character varying(500) |
kind | character varying(3) |
filingdate | date |
invention_title | character varying(500) |
===Ptotracking Tables===
 
The purpose of the ptotracking tables is to track the ownership of patents based on the update date and filing dates of the assignment. These tables can be used to add missing information or track further refined tables such as ptoproperty_patent.
 
Ptotracking takes the reelno, frameno, and documentid key from the ptoproperty_cleaned table and joins the update dates and recorded dates corresponding to the transactions.
 
DROP TABLE ptotracking;
CREATE TABLE ptotracking AS
SELECT M1.reelno, M1.frameno, M1.documentid, M2.last_update_date, M2.recorded_date
FROM ptoproperty_cleaned M1, ptoassignmentnd M2
WHERE (M1.reelno = M2.reelno) AND (M1.frameno = M2.frameno);
--8699074
 
In making the ptotracking table, it is important to note that the classification of documentids as B1 and B2 causes duplicates in the entries. B1 and B2 classifications mean that the patent was granted with and without a published application.
 
Ptotracking2 adds the assignee to the transaction, allowing the user to track ownership of the entity and of the patent.
 
DROP TABLE ptotracking2;
CREATE TABLE ptotracking2 AS
SELECT M1.reelno, M1.frameno, M1.documentid, M2.name, M1.last_update_date, M1.recorded_date
FROM ptotracking M1, ptoassigneend M2
WHERE (M1.reelno = M2.reelno) AND (M1.frameno = M2.frameno);
--9613927
 
The document ids in the PTO assignment data had not yet been verified as matching to the main patent table in our database (psql patent). The document ids in the PTO assignment data are stored as character strings whereas the patents in the patent table are stored as integers. Unlike the ptoprpoperty_cleaned table, all patent numbers in the patent table are unique.
 
The following two tables were made in order to verify that the documentids in the ptoproperty_cleaned table match to the patent table.
 
DROP TABLE edcheck;
CREATE TABLE edcheck AS
SELECT CAST (documentid AS INT) FROM ptotracking2;
 
SELECT COUNT(DISTINCT documentid) FROM edcheck;
--2343765
 
DROP TABLE edcheck2;
CREATE TABLE edcheck2 AS
SELECT M1.documentid, M2.patent
FROM edcheck M1, patent M2
WHERE (M1.documentid = M2.patent);
--2238305
 
DROP TABLE edcheck;
CREATE TABLE edcheck AS
SELECT DISTINCT documentid FROM ptotracking2;
--2343765
 
DROP TABLE edcheck2;
CREATE TABLE edcheck2 AS
SELECT CAST(documentid AS INT)FROM edcheck;
--2343765
 
DROP TABLE edcheck3;
CREATE TABLE edcheck3 AS
SELECT M1.documentid, M2.patent FROM edcheck2 M1, patent M2 WHERE M1.documentid = M2.patent;
--2238305
 
Based on the iterations of these tables, we could conclude that our original patent data forms the majority of the patents undergoing reassignments or transactions.
 
===US ONLY Patent Assignee Table===
 
Note: Table made for Julia by [[Marcela Interiano]]
 
Table made in the patent database using the USPTO assignment data.
 
The first step was to include the last_update_date in with the data from the ptoproperty table. The ptoproperty table contains only the filing date, which is not useful as we are looking for the current patent holders. The table ptoproperty_patent was used for the patent numbers as this table was cleaned to include only patent numbers, no application or publication numbers.
 
DROP TABLE ptoproperty_patent_update;
CREATE TABLE ptoproperty_patent_update AS
SELECT M1.reelno, M1.frameno, M1.patentno, M2.last_update_date
FROM ptoproperty_patent M1, ptotracking2 M2
WHERE (M1.reelno = M2.reelno) AND (M1.frameno = M2.frameno) AND (M1.patentno = M2.documentid);
 
Next, the minimum update date was taken, dropping any repetitions or later dates for the same patent assignee.
 
DROP TABLE ptoproperty_patent_minupdate;
CREATE TABLE ptoproperty_patent_minupdate AS
SELECT reelno, frameno, patentno, min(last_update_date) FROM ptoproperty_patent_update GROUP BY reelno, frameno, patentno, last_update_date;
 
The US only assignee table was used to construct the final table.
 
DROP TABLE ptoassignee_us_patent;
CREATE TABLE ptoassignee_us_patent AS
SELECT M1.reelno, M1.frameno, M2.name, M1.patentno, M1.last_update_date
FROM ptoproperty_patent_minupdate M1, ptoassigneend_us_cleaned M2
WHERE (M1.reelno = M2.reelno) AND (M1.frameno = M2.frameno);
 
The table below was made to join through using Sonia's zip codes for the ptoassignee data to get patent numbers from reelno and frameno.
 
DROP TABLE ptoassignee_us_distinct;
CREATE TABLE ptoassignee_us_distinct AS
SELECT DISTINCT reelno, frameno, patentno
FROM ptoassignee_us_patent
GROUP BY reelno, frameno, patentno;
--5391413
 
The total number of distinct patent numbers in the ptoassignee data for only US assignees is 2345763.
 
SELECT COUNT(*) FROM (SELECT DISTINCT patentno FROM ptoassignee_us_patent) AS P;
--2345763
 
===Current Assignee using Recorded Date===
 
Each assignment has three dates: filingdate, recorded_date, last_update_date. The filingdate corresponds to the filing of the assignment with the USPTO. The recorded_date is the date the transaction was recorded. The last_update_date is the date the USPTO verifies that the assignment still holds. In the ptoassignee_us_patent table, the last_update_date is used to find the current assignee.
 
Prior to Sonia's work with the ptoassignee table address data, the table ptoassignee_current was made using the most recent recorded_date. This method though is flawed given that additional transactions could have current previously that are still in effect as patents can have multiple assignees. These codes can be used for constructing similar tables using the address data Sonia has cleaned in the following sections of this project.
 
To begin with, the ptoproperty_patent table was cleaned to drop all duplicates. Then the table was matched with the assignee table.
 
DROP TABLE ptoassigneev1;
CREATE TABLE ptoassigneev1 AS
SELECT M1.reelno, M1.frameno, M1.documentid, M1.country, M1.filingdate, M2.last_update_date,
M2.recorded_date
FROM ptoproperty_patent2 M1, ptoassignmentnd M2
WHERE (M1.reelno = M2.reelno) AND (M1.frameno = M2.frameno);
 
DROP TABLE ptoassigneev2;
CREATE TABLE ptoassigneev2 AS
SELECT M1.reelno, M1.frameno, M1.documentid, M2.name, M1.country, M1.last_update_date, M1.recorded_date,
M2.addrline1, M2.addrline2, M2.city, M2.state, M2.postcode
FROM ptoassigneev1 M1, ptoassigneend M2
WHERE (M1.reelno = M2.reelno) AND (M1.frameno = M2.frameno);
--9634942
 
Once all the location and address fields from the ptoassignee table have been added to the ptoproperty_patent fields, the max recorded_date was identified from the ptoassignee_patent table and from ptoassigneev2 for comparison.
 
DROP TABLE datecheck;
CREATE TABLE datecheck AS
SELECT documentid, max(recorded_date) as recorded_date FROM ptoassignee_patent GROUP BY documentid;
--2343765
 
DROP TABLE datecheck;
CREATE TABLE datecheck AS
SELECT documentid, max(recorded_date) as recorded_date FROM ptoassigneev2 GROUP BY documentid;
--4374885
 
DROP TABLE ptoassignee_patent;
CREATE TABLE ptoassignee_patent AS
SELECT M1.reelno, M1.frameno, M1.documentid, M1.name, M1.last_update_date, M1.recorded_date, M2.addrline1,
M2.addrline2, M2.city, M2.state, M2.country, M2.postcode
FROM ptotracking2 M1, ptoassigneend M2 WHERE (M1.reelno = M2.reelno) AND (M1.frameno = M2.frameno);
--16581236
 
DROP TABLE ptoassignee_current;
CREATE TABLE ptoassignee_current AS
SELECT M1.reelno, M1.frameno, M2.documentid, M2.recorded_date FROM ptoassignee_patent M1, datecheck M2
WHERE (M1.documentid = M2.documentid)
AND (M1.recorded_date = M2.recorded_date);
--6729698
 
A final version of the ptoassignee_current table was made using ptoassigneev2 given the larger pool of documentids included in the table by matching using documentid and recorded dates from datecheck.
 
DROP TABLE ptoassignee_current;
CREATE TABLE ptoassignee_current AS
SELECT M1.reelno, M1.frameno, M2.documentid, M1.name, M1.last_update_date, M2.recorded_date, M1.addrline1,
M1.addrline2, M1.country, M1.city, M1.state, M1.postcode
FROM ptoassigneev2 M1, datecheck M2
WHERE (M1.documentid = M2.documentid) AND (M1.recorded_date = M2.recorded_date);
--4994869
 
These codes should be used to recreate this table using Sonia's updated address information.
 
===Matching Application and Publication Numbers===
The ptoproperty_cleaned documentids to verify the kind of different patents as specified in the ptoproperty tables.
 
First the table ptopropertynd was made, including only the distinct documentids in ptoproperty_cleaned.
 
DROP ptopropertynd;
CREATE TABLE ptopropertynd AS
SELECT DISTINCT * FROM ptoproperty;
--27266638
 
By creating this table, I also address the duplications caused by the kind XO.
 
===Final Table (name TBD)===
 
CREATE TABLE patpub AS
(SELECT ptoproperty_patent.reelno, ptoproperty_patent.frameno, ptoproperty_patent.invention_title,
ptoproperty_patent.patentno, ptoproperty_pub.pubno FROM ptoproperty_patent LEFT JOIN ptoproperty_pub
ON
(ptoproperty_patent.reelno = ptoproperty_pub.reelno) AND (ptoproperty_patent.frameno =
ptoproperty_pub.frameno)
AND (ptoproperty_patent.invention_title = ptoproperty_pub.invention_title)
UNION
SELECT ptoproperty_pub.reelno, ptoproperty_pub.frameno, ptoproperty_pub.invention_title,
ptoproperty_patent.patentno, ptoproperty_pub.pubno FROM ptoproperty_patent RIGHT JOIN ptoproperty_pub
ON
(ptoproperty_patent.reelno = ptoproperty_pub.reelno) AND (ptoproperty_patent.frameno =
ptoproperty_pub.frameno)
AND (ptoproperty_patent.invention_title = ptoproperty_pub.invention_title));
 
CREATE TABLE patapp AS
(SELECT ptoproperty_patent.reelno, ptoproperty_patent.frameno, ptoproperty_patent.invention_title,
ptoproperty_patent.patentno, ptoproperty_app.appno FROM ptoproperty_patent LEFT JOIN ptoproperty_app
ON
(ptoproperty_patent.reelno = ptoproperty_app.reelno) AND (ptoproperty_patent.frameno =
ptoproperty_app.frameno)
AND (ptoproperty_patent.invention_title = ptoproperty_app.invention_title)
UNION
SELECT ptoproperty_app.reelno, ptoproperty_app.frameno, ptoproperty_app.invention_title,
ptoproperty_patent.patentno, ptoproperty_app.appno FROM ptoproperty_patent RIGHT JOIN ptoproperty_app
ON
(ptoproperty_patent.reelno = ptoproperty_app.reelno) AND (ptoproperty_patent.frameno =
ptoproperty_app.frameno)
AND (ptoproperty_patent.invention_title = ptoproperty_app.invention_title));
==Restructure Address Information (First Stage)==
SQL code and other things are in:
E:/McNair/Projects/PatentAddress/RestructureAddressInfo(First Stage).sql
IO files are on the dbase server in:
Z:/PatentAddress
 
===To do===
 
In no particular order:
*Remove city, state, zip, country from addrline1 & addrline2 to get clean addrlines.
*Maybe concatenate addrline1 and addrline to make addrline
*Identify clean data (e.g. City that is a city, zip that is a zip, state that is a state)
**By pattern, length, match to list
*Try some more patterns, perhaps with a slightly higher false positive rate, on the remaining uncleaned data
**Iterate!
===Introduction===
SQL code is in:
E:/McNair/Projects/PatentAddress/FunctionsRestructureAddressInfo(First Stage).sql
====State====
SQL code is in:
E:/McNair/Projects/PatentAddress/FunctionsRestructureAddressInfo(First Stage).sql
====City====
SQL code is in:
E:/McNair/Projects/PatentAddress/FunctionsRestructureAddressInfo(First Stage).sql
====Output (Tables)====
SQL code is in:
E:/McNair/Projects/PatentAddress/FunctionsRestructureAddressInfo(First Stage).sql
===Clean Address Info (Master Table)===
SQL code is in:
E:/McNair/Projects/PatentAddress/FunctionsRestructureAddressInfo(First Stage).sql
For records of which 'addrline1', 'addrline2' and 'city' don't contain postcode info, just clean the 'postcode' as the 'postcode_cleaned'
SQL code is in:
E:/McNair/Projects/PatentAddress/FunctionsRestructureAddressInfo(First Stage).sql
All the cleaned states for U.S. patents are stored in ptoassigneend_us_cleaned (see feature state_cleaned).
SQL code is in:
E:/McNair/Projects/PatentAddress/FunctionsRestructureAddressInfo(First Stage).sql
All the cleaned cities for U.S. patents are stored in ptoassigneend_us_cleaned. (see feature city_cleaned)
All the SQL is in:
E:/McNair/Projects/PatentAddress/FunctionsRestructureAddressInfo(First Stage).sql
==== Cleaning ====
SQL code and other things are in:
E:/McNair/Projects/PatentAddress/Cleaning_Step2RestructureAddressInfo(Second Stage).sql
IO files are on the dbase server in:
=== Identify Clean Data ===
As mentioned, the ptoassigneend_us_extracted is cleaned. This section works on the remaining records which are stored in ptoassigneend_us_temp.==== Output: ptoassigneend_us_identify0 ====
First, filter out records with city that is a city, zip that is a zipAs mentioned in Section 3, state that the ptoassigneend_us_extracted is a stateclean. Note: The consistency between city and state or city and postcode is not checked Copy all the records in this sectionptoassigneend_us_extracted to ptoassigneend_us_identify0.
====zip that is a zip====Store remaining records in ptoassigneend_us_temp.
Match the pattern 5-4 or 5 digits.==== Output: ptoassigneend_us_identify1 ====
====The following section works on ptoassigneend_us_temp. Filter out records with city that is a city, zip that is a zip, state that is a state.  Note: The consistency between city and state or city and postcode is not checked in this section. * ptoassigneend_us_citylist  Copy clean city records in ptoassigneend_us_extracted to ptoassigneend_us_citylist (775).  Since the city list is not long, I briefly cleaned the list by hand, and updated the ptoassigneend_us_citylist (730). * zip that is a zip Match the pattern 5d-4d or 5 digits. *state that is a state====
Select distinct state records with
The output shows that all the records not null or not spaces are valid state names.
====*city that is a city==== Select distinct city records in ptoassigneend_us_extracted and store them in ptoassigneend_us_citylist (775).  Since the city list is not long, I briefly cleaned the list by hand, and still stored in ptoassigneend_us_citylist (730).
The safest One method to identify clean city is to find city records with feature city in that match ptoassigneend_us_citylist.
SQL Code:
-- SELECT 2603422
==== Output ==== * The table ptoassigneend_us_identify1 This table stores records that meet all the requirements above: zip with 5-4 or 5 digits, state not null or and not spaces, and city in ptoasigneend_us_citylist.
SQL Code:
SELECT 2511356
* Store remaining records in ptoassigneend_us_temp2. ==== Output: ptoassigneend_us_identify2 ==== Part of 'city' contains punctuationcomma at the end. Remove punctuation markscomma, and then match 'city' with ptoassigneend_us_citylist.
CREATE TABLE ptoassigneend_us_temp3 AS
SELECT *, replace(city, ',', '') clean_city
FROM ptoassigneend_us_temp2;
# SELECT 1055874
Output: The output is ptoassigneend_us_identify2.
SQL code:
CREATE TABLE ptoassigneend_us_identify2 AS
SELECT *
postcode ~* '\d{5}';
# SELECT 14508
 
Store remaining data (excluding data in ptoassigneend_us_identify0, ptoassigneend_us_identify1 & ptoassigneend_us_identify2) in ptoassigneend_us_temp3.
=== Clean Address: more patterns ===
 
Table: ptoassigneend_us_temp3
 
SQL code is in E:\McNair\Projects\PatentAddress\RestructureAddressInfo(Second Stage).sql
====Clean Postcode====
Identifying five-digit postcode is risky because of the existence of P.O. BOX #, SUITE #, etc.  One option is to identify state and postcode together with the following SQL codefunction: (take 'addrline1' as an example)
CREATE OR REPLACE FUNCTION ExtractPostcode2(adr text) RETURNS text AS $$ SELECT addrline1 FROM ptoassigneend_us_temp2 WHERE CASE WHEN (addrline1 adr ~* '([,]|[.])\s\w{2,}\s{0,}\w{0,}\s{1,}\d{5}' OR addrline1 adr ~* '(^|\s)\w{2}\s{1}\d{5}') AND NOT (addrline1 adr ~* 'BO' OR addrline1 adr ~* 'P[.]O') AND NOT (addrline1 adr ~* 'SUITE\s\d{5}') THEN SUBSTRING(adr, '\d{5}') ELSE NULL END AS result; # SELECT 3601$$ LANGUAGE SQL;
Examples:
767 FIFTH AVE., NEW YORK, NY 10153 | 10153
Even excluding the P.O. BOX # and SUITE #, noise Noise still exists.
After extracting postcode, the following function is used to get clean postcode.  The priority is 'postcode' if it is '\d{5}', postcode_addr1, postcode_addr2, postcode_city  CREATE OR REPLACE FUNCTION PostcodeClean2 (text,text,text,text) RETURNS text AS $$ $pri1=$_[0]; $pri2=$_[1]; $pri3=$_[2]; $postcode=$_[3]; if ($postcode) {return $postcode;} if ($pri1) {return $pri1;} if ($pri2) {return $pri2;} if ($pri3) {return $pri3;} return undef; $$ LANGUAGE plperl; The details and SQL function are in E:\McNair\Projects\PatentAddress\Cleang_Step2RestructureAddressInfo(Second Stage).sql
The output is table ptoassigneend_us_postex which include a new feature 'postcode_extracted'.
====Clean 'city'==== 'city' is cleaned using following patterns. *Pattern 1: 'city' ~ 'city name, state ID' *Pattern 2: 'city' ~ 'city name, state postcode (5 digits)' *Pattern 3: 'city' ~ 'city name,'
The SQL function is: CREATE OR REPLACE FUNCTION ExtractCity2(adr text) RETURNS text AS $$ SELECT CASE WHEN adr ~* '[,]\s{1,}\w{2}(\s{1,}|$|[.]|[,])' OR adr ~*Pattern '[,]\s{1: }\w{1}[.]\w{1}[.]' THEN REPLACE(SUBSTRING(adr, '.*[,]'),',','') WHEN adr ~* '[,].*\d{5}$' THEN REPLACE(SUBSTRING(adr, '.*[,]'),',','') WHEN adr ~* '.*[,]$'city THEN REPLACE(adr, ' is like ,'city name, state ID'') ELSE adr END AS result; $$ LANGUAGE SQL;
Extract city The details and state info with SQL codefunction are in E:\McNair\Projects\PatentAddress\RestructureAddressInfo(Second Stage).sql The output is table ptoassigneend_us_postex2 which include a new feature 'city_extracted' and 'postcode_extracted'.  CREATE TABLE ptoassigneend_us_postex2 AS SELECT REPLACE*, ExtractCity2(SUBSTRINGcity) city_extracted FROM ptoassigneend_us_postex; ===Identify Clean Data (Round Two)===A new list of clean city, 'is extracted in Section 4.3.2.*[This list,]combined with '),ptoassigneend_us_citylist',creates a new city list ',ptoassigneend_us_citylist2'') city_candid,which can be used to identify clean data.  REPLACE(SUBSTRING(Since the citylist is not long, '[I briefly cleaned it by hand,]and stored it in ptoassigneend_us_citylist2. *')Actually, we can find a full list of U.S. cities online: https://www.uscitieslist.org/. ====Output: ptoassigneend_us_identify3==== Similar to Section 4.2,'identify clean data that meets all the requirements: postcode_extracted with 5-4 or 5 digits,'state not null and not spaces,'') state_candidand city_extracted in ptoasigneend_us_citylist2. SQL Code: CREATE TABLE ptoassigneend_us_identify3 AS SELECT * FROM ptoassigneend_us_temp3ptoassigneend_us_postex2 WHERE city ~* city_extracted IN ( SELECT citylist FROM ptoassigneend_us_citylist2) AND state IS NOT NULL AND state != '[,]\s{1,}\w{2}' OR city AND postcode_extracted ~* '[,]\s{1,}\w{1}[.]\wd{15}[.]' ; #SELECT 1254
*Pattern 3: 'city' is like 'city name, state postcode (5 digits)' SELECT 664524
Extract city and state info with SQL code* Output table: SELECTseSEL REPLACE(SUBSTRING(city, '.*[,]'),',','') city_candid, REPLACE(REPLACE(SUBSTRING(city, '[,].*\d{5}$'),',',''), '\d{5}', '') state_candid FROM ptoassigneend_us_temp3 WHERE city ~* '[,].*\d{5}$'; #SELECT 624ptoassigneend_us_identify3
*Feature Table "public.ptoassigneend_us_identify3" Column | Type | Modifiers -------------------|------------------------|----------- reelno | integer | frameno | integer | name | character varying(500) | addrline1 | character varying(500) | addrline2 | character varying(500) | city is null or spaces | character varying(500) | state | character varying(500) | country | character varying(500) | postcode | character varying(Not Clean80) | postcode_extracted | text | city_extracted | text |
-- SELECT 51050Remaining records are in table ptoassigneend_us_temp4.
====Output: ptoassigneend_us_identify4====
Some of the city records contain dots. Remove dots, and match 'city' with ptoassigneend_us_citylist2.
SQL Code:
CREATE TABLE ptoassigneend_us_identify4 AS
SELECT *
FROM ptoassigneend_us_temp5
WHERE city_extracted2 IN (
SELECT citylist
FROM ptoassigneend_us_citylist2) AND
state IS NOT NULL AND state != '' AND
postcode_extracted ~* '\d{5}';
SELECT 38
The remaining records are stored in ptoassigneend_us_temp5.
===Summary===
Table Name | Records #
----------------------------------------------------|-------------
ptoassigneend_allus | 3572605
----------------------------------------------------|-------------
ptoassigneend_us_identify0 | 5343
ptoassigneend_us_temp | 3567261
ptoassigneend_us_identify1 | 2511356
ptoassigneend_us_temp2 | 1055874
ptoassigneend_us_identify2 | 14508
ptoassigneend_us_temp3 | 1041366
ptoassigneend_us_identify3 | 664524
ptoassigneend_us_temp4 | 376835
ptoassigneend_us_identify4 | 38
ptoassigneend_us_temp5 | 376797
----------------------------------------------------|-------------
ptoassigneend_us_identify_subtotal | 3195769
----------------------------------------------------|-------------
ptoassigneend_us_candid1 (city and state are clean) | 136958
ptoassigneend_us_candid2 (postcode is clean) | 184123
SELECT 847====Output: ptoassigneend_us_identify_subtotal====
* Union ptoassigneend_us_identify(0-4) to generate ptoassigneend_us_identify_subtotal with clean city, state and postcode(. This table contains 89.5% of all the records in ptoassigneend_allus. 10.5)% left in ptoassigneend_us_temp5.
Table "public.ptoassigneend_us_identify_subtotal" Column | Type | Modifiers -----------------|------------------------|----------- reelno | integer | frameno | integer | name | character varying(500) | addrline1 | character varying(500) | addrline2 | character varying(500) | city_cleaned | text | state_cleaned | text | country | character varying(500) | '.*[,].*\d{5}'postcode_cleaned | text |
====Output: ptoassigneend_us_candid1====
* city, state codeOne problem of records in ptoassigneend_us_temp5 is that the postcode is missing.
'ptoassigneend_us_candid1 is a subset of ptoassigneend_us_temp5.*[It contains clean city and state info,]\s{0,}\w{2}$'but postcode is missing.
-- 284SQL code: CREATE TABLE ptoassigneend_us_candid1 AS SELECT * FROM ptoassigneend_us_temp5 WHERE city_extracted2 IN ( SELECT citylist FROM ptoassigneend_us_citylist2) AND state IS NOT NULL AND state != ''; SELECT 136958
* city, state codeRemaining records are in table ptoassigneend_us_temp6 (SELECT 239837).
'====Output: ptoassigneend_us_candid2====ptoassigneend_us_candid2 is also a subset of ptoassigneend_us_temp5.*[It contains clean postcode info,]\s{0,}\w{2}\s'but city and state are not identified.
* IS NOT NULL AND I randomly checked the city_extracted in ptoassigneend_us_candid2, and it is quite clean. Some city != \records are misspelt, such as '\Oklahama City' AND . We may identify clean city !~* '([,]|[based on the length of records.])'
ProblemNote: can't identify citiesAbout 60 records are missing. For example, the # of records in ptoassigneend_us_temp + # of records in ptoassigneend_us_identify0 != # ptoassigneend_allus.
-- 23501====To do====* Remove city, state, zip, country from addrline1 & addrline2 to get clean addrlines.* Maybe concatenate addrline1 and addrline to make addrline

Navigation menu