Hello Valentin, looking at your query; it is a bit difficult to understand exactly what you would like to do with regards to the fractional counting. Can you explain in a couple of sentences, what you would like to do and how you expect the results to look like ? If your methodology is to be used on...

Hello Polina, your analysis - reason 1 is correct. In PATSTAT we have aggregated applicant and inventor names at application level via the tls207 table. This means that (generally spoken) we take the names from the latest publication instance from that application. So when a change of ownership happ...

The queries are all variations on the same theme; in the WHERE part of the SQL query, you specify what "group" of patents the final result list should look like. The "AND tls201_appln.appln_id in (select.....)" defines intersections of samples of patents. So here is a query that ...

Hello Isabel, here is a simple query that selects all EP patents (labelled "Chemistry") having at least 1 German University as applicant and nothing else. (Some patents have more then 1 German applicant that is labelled as a university: https://worldwide.espacenet.com/patent/search/family/...

The reason is because your SQL query is build as such that the condition of "university" and "being German" is split in 2 different branches. So each of the patents will have a university (maybe not German) and a German applicant (maybe a university). It's only a matter of buildi...

You can easily adapt one of the queries in this post to your needs: https://forums.epo.org/sql-queries-to-create-simple-applicant-year-based-table-10588 For example add: and psn_name in ('volkswagen' , 'renault' , 'audi' , 'VOLVO CAR CORPORATION' , 'PEUGEOT CITROEN AUTOMOBILES' , 'DAIMLER') in the W...

Hello Rmudie96, the reason why your query does not return results is the missing spaces in the IPC codes. There should always be 8 characters before the position of the slash (which is position 9) The query below will give you data. However, keep in mind that a) addresses for physical persons have b...

Hello Leonardo, thank you for pointing out the missing data. We have added it, but it will of course take until the next PATSTAT release before it comes available. At this link you can find an overview on coverage and missing data: https://forums.epo.org/mapping-data-completeness-of-patstat-global-a...

Hello Adnan, here is the script that works fine on our MS SQL server to create the table: (from the scripts in the documentation): USE [patstat2021a] GO SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO CREATE TABLE [dbo].[tls206_person]( [person_id] [int] NOT NULL DEFAULT ('0'), [person_name] [nvarc...

Hello Eduardo, Indeed, the column is not included in tls231_inpadoc_legal_event in PATSTAT (but that is normal). You can link to tls803_legal_event_code via a join using the event_auth AND the event_code. Below is an example on how to do this. SELECT top 10 * from tls231_inpadoc_legal_event join tls...