Many of the PATSTAT Raw Data users work on MySQL. Recently I was in contact with Simone Mainardi ( http://www.simonemainardi.com/ ), who created a handy tool to upload the PATSTAT Raw Data files into MySQL. Simone is happy to share his effort with the community and recently upgraded it to be compati...

Just my observations and hints: Searching in long texts with wild cards,which you do heavily in your query, is costly in PATSTAT Online. A relational database is not the ideal tool for searching text. In your query there is no need to put a wild card on the left side of the IPC symbol, like ipc_clas...

You guessed correctly. If APPLT_SEQ_NR and INVT_SEQ_NR are > 0 in the table TLS207_PERS_APPLN or table TLS227_PERS_PUBLN, then an applicant is also an inventor for that application. As you mentioned, this is quite often the case. As usual, there are several ways to model data. The PATSTAT model was ...

Daniel, This is the classical division-by-zero error, because you compute "SUM(1/(nb_applicants*1.00))". It will help if you include in your statement "AND nb_applicants > 0"; then your query will run fine. Still, I do not fully understand the situation. In principle, there exist applications in PAT...

I'm sorry to hear that you have had troubles loading the data into your database. Among the many tests we do before shipping the disks, we load the csv files again in our DBMS (we are using MS SQL Server v2008). For 2015b we did not encounter any problems. To better understand your problem, could yo...

You are right, the easiest way to do this is with the OFFSET ... FETCH clause, which is new in version 2012. Luckily PATSTAT Online is running on MS SQL Server 2012. An ORDER BY clause is mandatory for the OFFSET ... FETCH. So to conform to the syntax, you must append to your query these lines to sk...

Inventor address data is not available in PATSTAT Online. To facilitate the analysis on a micro-regional level despite missing addresses, we are currently investigating the possibilities of extending PATSTAT data with NUTS3/TL3 and other related information. In the meantime, you could have a look at...

Dear Jos, Due to a flaw in our source data files (DOCDB backfile of Jan 2015) the abstract text may contain one or more of these strange strings "#CMT#". They do not have any business relevance. I would simply ignore them or - if your research requires it - delete them in your database, e.g. with RE...

Fixed again. Sorry for the inconvenience.

To report the non-working of features of PATSTAT Online, it is best to write directly to epal@epo.org. Posts in the forum might go unnoticed for some time.

Sorry for responding rather late. Thanks for reporting this issue, which has been fixed the following day. So you should have been able to download the retrieved data since then.