Dear Simone, If you can live with the "family based" forward citations, then simply take the nb_citing_docdb_fam attribute. "Application based" data would involve using the tls211 and tls212 tables and then "grouping" the data at application level. This is quasi impossi...

Dear John123, Distinguishing in PATSTAT between applicant and inventor is fairly easy by means of the tls207 (for applications) or tls227 (for publications) in combination with the tls206_person table. PATSTAT users have the full freedom to direct their search to only consider applicants, inventors ...

Many users are asking how to create NUTS 2 based tables -similar to what Eurostat used to do-. NUTS based data at the lower levels (2-3) can only be created for persons (applicants and inventors) where there is good address data available. In the person table you will find the most granular NUTS cod...

Hello Faery, I assume you mean something like this (to be adapted by you): select tls206_person.person_ctry_code Applt_CTRY, count(distinct(case when per.person_ctry_code = 'CN' and tls206_person.person_ctry_code <> 'CN' then tls201_appln.appln_id end)) as 'CN', count(distinct(case when per.person_c...

Dear Vanessa, CPC classifications are assigned at family level and you will not find duplicates. (CPC is also not -yet-published on the published patent document.) IPC is a bit different, they are published and can change between the publication instances. We group them and de-duplicate them at appl...

Hello, Generally spoken: PATSTAT is produced 2 times per year, in Spring and Autumn. Those releases are based on data extractions carried out in January and July (mostly). So any publication or data being added to our databases between January 2020 and now will not be available in the current PATSTA...

Dear Katharina, your query is fine, and it is indeed good practice to question results when they do not seem to fit the expected pattern. In this case, the applicant "Microsoft Corp" is being phased out - and replaced by "MICROSOFT TECHNOLOGY LICENSING" as the main applicant name...

Hello Lennart, there were a couple of brackets missing in your WHERE clause. SELECT DISTINCT tls201_appln.docdb_family_id, earliest_filing_year, tls206_person.person_ctry_code, CPC.CPCgrouped FROM tls201_appln JOIN TLS203_APPLN_ABSTR ON tls201_appln.appln_id = TLS203_APPLN_ABSTR.appln_id JOIN tls207...

Hello Lennart, your analysis is correct; family members can have different spellings in the applicant name, the number of applicants can be different (that is why we took MAX); it could in principle even be different companies, and also the presence of a country code will lead to "different per...

1) If you remove the "and (invt_seq_nr = 0)", you will get all the applicants back. It basically excludes many of the "natural persons" from the applicant list, namely the ones that are applicants. 2) CPC codes can be assigned by multiple offices and that can create duplicates. D...