appln_auth in PATSTAT2017b versus PATSTAT2018a

Here you can post your opinions, ask questions and share experiences on the PATSTAT product line. Please always indicate the PATSTAT edition (e.g. 2015 Autumn Edition) and the database (e.g. PATSTAT Online, MySQL, MS SQL Server, ...) you are using.
Post Reply

EPO / PATSTAT Support
Posts: 87
Joined: Thu Feb 22, 2007 5:33 pm

appln_auth in PATSTAT2017b versus PATSTAT2018a

Post by EPO / PATSTAT Support » Tue May 15, 2018 9:20 am

Keep in mind that the domain of the appln_auth attribute has changed.
PCT applications will have "WO" in combination with a value in the receiving_office in PATSTAT2018a.

This can lead to un-expected results when using "old queries". You might need to adapt them.
Take the following query:

Code: Select all

SELECT distinct appln_id, appln_auth, appln_nr, appln_kind, appln_filing_date
  FROM tls201_appln 
where appln_filing_year = 2012 
and appln_auth = 'NL'
order by appln_id
Will result in 3268 results for 2017b but only 2279 records for PATSTAT 2018a. The PCT applications are excluded !

To obtain the same result as before, one could use a query such as this:

Code: Select all

SELECT distinct appln_id, appln_auth, appln_nr, appln_kind, appln_filing_date
  FROM tls201_appln 
where appln_filing_year = 2012 
and (appln_auth = 'NL' or receiving_office ='NL')
order by appln_id
PATSTAT Support Team
EPO - Vienna
patstat @ epo.org


Post Reply