Dear HZ, PATSTAT Online and its 3rd party components unfortunately is not free of bugs. In certain complex queries (e.g. nested queries with aliases) it detects syntax errors where there are none. Often there is a workaround by slightly re-writing the query, like - what I did below - to replace "SEL...

Thank you, Rudi, for this proposal. I will consider in in the next version. The SHA-1 you mentioned is created automatically by our Bulk Data Platform from which you can download EPO data. But generally, SHA-1 is used less and less. So for additional check sums we will utilize the more future-proof ...

Dear Rudi, Thanks for your suggestion. Please find in the attached file the requested check sum data. SHA512_for_PATSTAT_files.zip BTW: I personally use the free 7zip tool (with command line interface) a lot to unzip archives.. Like WinZip, it sometimes has issues, but in some cases it is useful to ...

Hi Stefana, Interesting question, so I had a look and tried it myself. You will find my code below. My thoughts: I assume you did not consider that the technical field table TLS901_TECHN_FIELD_IPC contains multiple entries for each technical field number. There is one record for each technical field...

Hi Stefana, This line in your nested SELECT is causing the error: "SELECT distinct reg110_title. id , reg107_parties. id , reg107_parties.country " The result of this SELECT is a (virtual) table containing 2 columns named "id" which is never allowed because they cannot be referred to unambiguously. ...

Hi Elisa,

Make sure you imported the data as UTF-8. A Chinese character is typically encoded by 3 bytes.

The result of your query should look like in the attached screenshot.

Best regards,
Martin

Hi Tim, Only some of the Identifiers in PATSTAT data are "stable", meaning they identify the same records across editions of PATSTAT. For details please see the Data Catalog or PATSTAT Global, section 4.3.2. While PERSON_ID is such as stable identifier, PSN_NAME (the PATSTAT Standardised Name) is no...

This product is a free bulk data set consisting of XML-tagged titles, abstracts, descriptions, claims and search reports covering all EP publications, designed to facilitate natural language processing work. It can be used alone, but is best if combined with bibliographic patent data, like it is ava...

The location of this data set on Google Cloud has changed. It is now available in bucket “epo-public”. After signing into Google you may access the bucket via https://console.cloud.google.com/storage/browser/epo-public/ . For downloading larger volumes it is recommended to use the CLI "gsutil" from ...

The update for the data set "Linked open EP data" will be delayed due to EPO's office closure during the holidays. The planned schedule is: The update for week 52/2019 will take place Friday, 2020-01-03 afternoon. The update for week 01/2020 will take place Monday, 2020-01-06 morning. I apologize fo...