Changes

9,009 bytes added , 13:41, 21 September 2020

no edit summary

{{Project|Has project output=Data|Has sponsor=McNair ~~Projects~~Center

|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=~~Active~~Subsume|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:

Column | Type | Modifiers

-----------------+-----------------------+-----------

Currently the pto tables contain varying identifiers for one invention title that is involved in a reassignment. The purpose of the table is to have each identifier for an invention title listed in a single row, making it easy to track the invention through various transactions. The Match By column will inform the user which identifier should be used to match to other tables in the patent database.

==Data Cleanup Progress==

The tables that currently comprise the assignment data are as follows.

Column | Type | Modifiers

-------------------------+------------------------+-----------

Table "public.ptoassignee"

Column | Type | Modifiers

-----------+------------------------+-----------

Table "public.ptoassignor"

Column | Type | Modifiers

----------------+------------------------+-----------

Table "public.ptoproperty"

Column | Type | Modifiers

-----------------+------------------------+-----------

Table "public.ptopatentfile"

Column | Type | Modifiers

------------------------+-----------------------+-----------

~~==Data Cleanup Progress==~~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===

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.

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===

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)===

SQL code and other things are in:

E:/McNair/Projects/PatentAddress/RestructureAddressInfo(First Stage).sql

IO files are on the dbase server in:

SQL code is in: