PATSTAT 2016 Spring edition now available for purchase.

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

Geert Boedt
Posts: 176
Joined: Tue Oct 19, 2004 10:36 am
Location: Vienna

PATSTAT 2016 Spring edition now available for purchase.

Post by Geert Boedt » Wed Jun 01, 2016 12:51 pm

PATSTAT 2016 Spring edition now available for purchase.
Currently we have PATSTAT Raw data; in a couple of weeks PATSTAT Online will also become available.

PATSTAT 2016 Spring edition developments:
We added and renamed a couple of attributes to improve readability and linking to other data sources. This means that you will need to have a look at the PATSTAT(and Register for PATSTAT) Data Catalogs (section “History of major changes to tables and attributes”) to see what attributes in the tables have been changed. As with previous editions, we provide our scripts which we use at the EPO to create the database, tables and indexes on a MS SQL Server 2012 platform. You probably have to adapt them to suit your database platform or they can serve as an example if you need to create your own. We also applaud the initiative of users who share their scripts with the PATSTAT community via the forum patstat/.

a) TLS_201_APPLN: 4 extra attributes have been added to the PATSTAT main table.
The attribute: APPLN_NR_ORIGINAL contains the application number as provided to the EPO by the supplier. It is assumed that the number is the application number as printed on the respective publications (INID 21)., but we have observed that this attribute may at times contain other numbers (like the original PUBLICATION number or the originating PCT application number). The purpose of this attribute is to enable PATSTAT users to link the data to other data sources where the original application number is used as a key. We cannot guarantee that it will always match, but some users have requested it and we hope it will improve the interoperability of PATSTAT with other data sources.
INT_PHASE, REG_PHASE and NAT_PHASE are 3 attributes that help PATSTAT users to quickly identify the route of the respective patent application. These attributes are based on the possible combinations of APPLN_KIND, APPLN_AUTH, PUBLN_KIND and INTERNAT_APPLN_ID. Also here a word of warning: we are aware that not all applications have the INTERNAT_APPLN_ID (link to the earlier PCT application) as we expect them to have, therefore the above attributes should be used with caution.

b) TLS206_PERSON, TLS906_PERSON: the EPO has entered into a new contract with the Leuven ECOOM team to provide harmonised applicant names. The attributes are added to the tables TLS206_PERSON and TLS906_PERSON. They are labelled PSN.... (PATSTAT Harmonised Name), generally corresponding to the HRM attributes of the EEE-PPAT table.

c) Table TLS211_PAT_PUBLN: a new attribute PUBLN_NR_ORIGINAL has been added to the table. Similar to the APPLN_NR_ORIGINAL, we have added the original publication number to the publication records so that PATSTAT can be linked to other data sets where the publication number is used. The coverage of this attribute is rather limited and we advise you to check before using it.

d) Table TLS212_CITATION: NPL_PUBLN_ID has been renamed to CITED_NPL_PUBLN_ID.

e) Table TLS214_NPL_PUBLN: NPL citations that had the value “none” or “see also references...” have been removed from the data. In anticipation of richer citation data becoming available in the future, the attribute NPL_TYPE has been added. This attribute shows the type of citation for example: books, databases, publications,...

f) Table TLS226_PERSON_ORIG: the attributes ADDRESS_1, ADDRESS_2 and ADDRESS_3 are now also used for address information originating from the USPTO.

g) TLS229_APPLN_NACE2: small updates in the IPC_NACE2 concordance table have resulted in some minor changes.

EPO Register for PATSTAT

A number of changes have been implemented in the Register database. The logical model has been optimized and we have removed and/or regrouped some tables in order to make the database more compact and easier to work with. (Less joins are needed when writing SQL queries.)

a) Table REG204_PRCDRL_STEP_AFFECTED_STATES and REG205_PRCDRL_STEP_RESULT have been removed from the database and the data has been integrated in REG201_PROC_STEP. The original attribute names have been adapted to the new table names so that it becomes more logical to place the attributes with regards to their source tables.

b) Table REG301_EVENT_DATA is now linked to REG402_EVENT_TEXT via the existing EVENT_CODE attribute. Therefore the EVENT_TEXT_ID could be removed from the both tables.

c) Table REG114_DATES: the attribute DATE has been renamed to EVENT_DATE because the word DATE is a reserved word in many data management systems.


PATSTAT Online on PISE (Patent Information Services for Experts)
PATSTAT Online is now available as a separate subscription product. Depending on the subscriptions you have, PATSTAT Online may also include the TLS221_INPADOC_PRS data as well as the EPO Register for PATSTAT data base.


If you need any further information, please have a look at the PATSTAT webpage:
http://www.epo.org/patstat
or contact us via patstat @ epo.org
Best regards,

Geert Boedt
PATSTAT support
Business Use of Patent Information
EPO Vienna


Post Reply