Match of PATSTAT data (2019 spring) and PatentsView (jan 2019) is
discussed here, with focus on how this match can help to enrich PATSTAT
data with information not contained in USPTO patents (and the other way
round).
academic patenting
(4)
algorithms
(2)
anvur
(1)
APE-INV
(3)
applicants
(10)
applications
(11)
ascii
(1)
bibliometrics
(7)
bocconi
(2)
bug
(1)
china
(2)
citations
(11)
claims
(3)
concordance
(7)
conference
(8)
CPCs
(2)
curiosities
(1)
data quality
(12)
data recovery
(1)
database
(26)
datamining
(5)
disk
(1)
download
(1)
dump
(1)
ecla
(1)
entity resolution
(4)
EP register
(7)
epo
(15)
equivalents
(1)
espacenet
(2)
ethnicity
(2)
examination
(3)
excel
(3)
free
(2)
function
(1)
GDPR
(1)
gender
(1)
geocoding
(6)
github
(1)
icons
(1)
indicators
(1)
inpadoc
(9)
inventors
(21)
IPC
(21)
IPC35
(4)
job offers
(1)
KITeS
(3)
legal status
(16)
levenshtein
(1)
line breaks
(1)
linked open data
(1)
match
(1)
mobility
(1)
mysql
(23)
nace
(2)
national patents data
(6)
NBER
(1)
news
(1)
NPL
(7)
NUTS3
(6)
OHIM
(1)
openoffice
(1)
orbis
(1)
orcid
(1)
OS
(1)
OST
(2)
password recover
(1)
patent attorneys
(1)
patent data
(2)
patent family
(17)
patent ownership
(3)
patent status
(3)
patent value
(1)
patents
(49)
patentsview
(3)
patstat
(145)
person_id
(13)
priorities
(5)
python
(2)
reclassification
(8)
renewals
(1)
replace
(2)
scientific articles
(2)
scopus
(1)
semantic analysis
(2)
sipo
(3)
sql
(6)
strings
(4)
tool
(9)
trademarks
(2)
triadic patents
(2)
UDF
(1)
USPC
(1)
USPTO
(12)
VBA
(1)
vista
(1)
VM
(1)
webscraping
(2)
WIPO
(10)
workshops
(1)
Wos
(1)
xp
(1)
Monday, October 7, 2019
Monday, September 30, 2019
Patents applicants: how to create the full time series
I share a presentation I made @ EPo & KUL summer school in Vienna last september!
hope it's useful to someone else.
Patents change applicants data within time;
Main reason for change are ownership change, name/address change, M&A …
Applicant’s names contained in TLS206 is the ‘last available’ data;
PATSTAT Global + EP Register make available several sources to build a chain of names
and a timeline for patents contained;
hope it's useful to someone else.
Patents change applicants data within time;
Main reason for change are ownership change, name/address change, M&A …
Applicant’s names contained in TLS206 is the ‘last available’ data;
PATSTAT Global + EP Register make available several sources to build a chain of names
and a timeline for patents contained;
Thursday, July 18, 2019
Patents citations from Pubmed Scientific publications
A recently released dataset from Marx, Matt; Aaron Fuegi contains citations from USPTO patents granted 1947-2018 to articles captured by the MS Academic Graph (ID) from 1800-2018.
Files, tab-separated, are available at link : https://zenodo.org/record/3338601
The main file, pcs.tsv, contains the resolved citations matching patent number, MAG ID, the original citation from the patent, an indicator for whether the citation was supplied by the applicant, examiner, or unknown, and a confidence score (1-10) indicating how likely this match is correct.
There is also a PubMed-specific match in pcs-pubmed.tsv.
Authors also made availabel source code for generating the patent citations to science in pcs.tsv is available at https://github.com/mattmarx/reliance_on_science. Source code for generating jif.zip and jcif.zip (Journal Impact Factor and Journal Commercial Impact Factor) is at https://github.com/mattmarx/jcif.
Scripts and programs are mainly for stata & linux (DO files and sh scripts).
Monday, July 8, 2019
PATSTAT - patentsview concordance update 2019
PatentsView is a platform built on data
derived from USPTO bulk data files.
This dataset complements perfectly PATSTAT since the former has an native disambiguation of inventors and applicants and a geocoding system applied to inventors and applicants, while the latter links US data to other offices, allowing to calculate knowledge spillovers, family data etc.
At this link is possible to download a table of concordance between patent_id (Patentsview main key) and appln_id (from PATSTAT).
Overlapping of the two datasets is not perfect since Patentsview contains only granted patents after 1975, where PATSTAT has also application (ungranted) and timeframe covers also pre-1975 data.
On the other hand PATSTAT misses design patents before 2001, plants before 2001 and 'statutory invention registration' type of patent.
Data are from PATSTAT spring 2019 and Patentsview march 2019, thus also 2019 data in PW are partially missing in PATSTAT.
This dataset complements perfectly PATSTAT since the former has an native disambiguation of inventors and applicants and a geocoding system applied to inventors and applicants, while the latter links US data to other offices, allowing to calculate knowledge spillovers, family data etc.
At this link is possible to download a table of concordance between patent_id (Patentsview main key) and appln_id (from PATSTAT).
Overlapping of the two datasets is not perfect since Patentsview contains only granted patents after 1975, where PATSTAT has also application (ungranted) and timeframe covers also pre-1975 data.
On the other hand PATSTAT misses design patents before 2001, plants before 2001 and 'statutory invention registration' type of patent.
Data are from PATSTAT spring 2019 and Patentsview march 2019, thus also 2019 data in PW are partially missing in PATSTAT.
Thursday, June 6, 2019
Patent familiarity calc scripts
I made available on Github a set of MySQL and python scripts to create familiarity indicator by IPC class, on NBER patents dataset.
https://github.com/gtarasconi/NBER-familiarity-indicators
Inventor’s familiarity with components of the invention measured by the (a) recent and (b) frequent usage of focal patent’s classes across all US patents. Thus, we calculate a measure of familiarity for each separate class of a focal patent. Therefore, the more recently and frequently a class has been used, its individual measure will be higher.
Based on Fleming 2001
https://funginstitute.berkeley.edu/wp-content/uploads/2012/10/Recombinant-Uncertainty-in-Technological-Search.pdf
https://github.com/gtarasconi/NBER-familiarity-indicators
Inventor’s familiarity with components of the invention measured by the (a) recent and (b) frequent usage of focal patent’s classes across all US patents. Thus, we calculate a measure of familiarity for each separate class of a focal patent. Therefore, the more recently and frequently a class has been used, its individual measure will be higher.
Based on Fleming 2001
https://funginstitute.berkeley.edu/wp-content/uploads/2012/10/Recombinant-Uncertainty-in-Technological-Search.pdf
Wednesday, May 22, 2019
PATSTAT 2019a analysis of changes
As Stated in EPO documents new version of PATSTAT comes with 2 mayor changes:
Person names in the original language (PERSON_NAME_ORIG_LG)
Field added in tables TLS206, 226, 906. This creates an inflation of records and lack of retrocompatibility with old personwise data.
“RELEVANT_CLAIM” attribute in the TLS215_CITN_CATEG table
A new attribute “RELEVANT_CLAIM” has been added to the TLS215_CITN_CATEG table. This attribute contains a single number referring to the claim to which the citation refers to.
About first change you can find below, for offices with more than 100.000 person_ids, how are they most affected, where the last column shows inflation rate
About the latter, number of records in TLS215 are more than doubled since for each category (now categories can be multiple as AD, AX ...) one line for relevant claim is created.
Person names in the original language (PERSON_NAME_ORIG_LG)
Field added in tables TLS206, 226, 906. This creates an inflation of records and lack of retrocompatibility with old personwise data.
“RELEVANT_CLAIM” attribute in the TLS215_CITN_CATEG table
A new attribute “RELEVANT_CLAIM” has been added to the TLS215_CITN_CATEG table. This attribute contains a single number referring to the claim to which the citation refers to.
About first change you can find below, for offices with more than 100.000 person_ids, how are they most affected, where the last column shows inflation rate
| APPLN_AUTH | Count_person_id_2018b | Count_person_id_2019a | ratio |
| AR | 150688 | 182005 | 121% |
| AT | 1142798 | 1232406 | 108% |
| AU | 1870980 | 2008555 | 107% |
| BE | 196598 | 204115 | 104% |
| BR | 1223470 | 1315337 | 108% |
| CA | 2524565 | 2675965 | 106% |
| CH | 650912 | 664626 | 102% |
| CN | 6192040 | 9956730 | 161% |
| CS | 166131 | 178125 | 107% |
| CZ | 130967 | 233777 | 179% |
| DD | 226783 | 234141 | 103% |
| DE | 5095800 | 5258606 | 103% |
| DK | 624763 | 687156 | 110% |
| EP | 6624815 | 6625117 | 100.005% |
| ES | 1291041 | 1389533 | 108% |
| FI | 365453 | 384041 | 105% |
| FR | 1471641 | 1588271 | 108% |
| GB | 1757273 | 1797304 | 102% |
| GR | 134008 | 173190 | 129% |
| HK | 300604 | 426287 | 142% |
| HU | 234866 | 303144 | 129% |
| IL | 128159 | 167805 | 131% |
| IN | 190763 | 213962 | 112% |
| IT | 661777 | 719438 | 109% |
| JP | 2802730 | 3787058 | 135% |
| KR | 1906273 | 3031637 | 159% |
| MX | 524748 | 620385 | 118% |
| MY | 121991 | 158129 | 130% |
| NL | 144408 | 155950 | 108% |
| NO | 370993 | 444431 | 120% |
| NZ | 261084 | 329085 | 126% |
| PL | 370207 | 492642 | 133% |
| PT | 218054 | 249693 | 115% |
| RO | 131598 | 152849 | 116% |
| RU | 979629 | 1831707 | 187% |
| SE | 406973 | 420885 | 103% |
| SG | 277368 | 363149 | 131% |
| SU | 1536615 | 1718307 | 112% |
| TW | 1004135 | 1143685 | 114% |
| UA | 164487 | 339271 | 206% |
| US | 12270415 | 12630422 | 103% |
| WO | 4119901 | 4756241 | 115% |
| ZA | 511180 | 621550 | 122% |
About the latter, number of records in TLS215 are more than doubled since for each category (now categories can be multiple as AD, AX ...) one line for relevant claim is created.
Sunday, May 19, 2019
PATSTAT 2019a MySQL upload scripts
At this link are available my new scripts for MySQL to upload PATSTAT 2019a data.
New features in this ediction:
Person names in the original language (PERSON_NAME_ORIG_LG)
Field added in tables TLS206, 226, 906. This creates an inflation of records and lack of retrocompatibility with old personwise data.
“RELEVANT_CLAIM” attribute in the TLS215_CITN_CATEG table
A new attribute “RELEVANT_CLAIM” has been added to the TLS215_CITN_CATEG table. This attribute contains a single number referring to the claim to which the citation refers to.
Subscribe to:
Posts (Atom)