Same applicant name but different PSN ID

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

Tyna
Posts: 5
Joined: Tue Jun 13, 2017 7:21 pm

Same applicant name but different PSN ID

Post by Tyna » Tue Sep 05, 2017 10:57 pm

Hey,
Can you tell me please why sometimes I find same applicant name and adress but different PSN_ID. Does it mean that it's not the same applicant? if it's the same applicant how can I deal with that when I count patents by applicant.

Exemple
7022504 ESSILOR INTERNATIONAL Compagnie Générale d'Optique 147, rue de Paris,94220 Charenton Le Pont
7022524 ESSILOR INTERNATIONAL (COMPAGNIE GENERAL D'OPTIQUE) 147 RUE DE PARIS F-94220 CHARENTON-LE -PONT FR147 RUE DE PARIS F-94220 CHARENTON-LE -PONT FR
7022533 ESSILOR INTERNATIONAL (COMPAGNIE GENERALE D'OPTIQUE) 147, RUE DE PARIS, F-94220 CHARENTON- LE -PONT, FR147, RUE DE PARIS, F-94220 CHARENTON- LE -PONT, FRANCEANCE
7022601 ESSILOR INTERNATIONAL, CIE GENERALE D'OPITQUE 147, rue de Paris,94227 Charenton-Le-Pont



Thank you.
Tyna


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

Re: Same applicant name but different PSN ID

Post by Geert Boedt » Thu Oct 05, 2017 5:28 pm

Hello Tyna,
the methodolgy to group the names is based on a 2 step approach, one automatic one followed by a manual check of a limited group of applicants.
The manual check exist out of checking the top applicants for each IPC subclass as well as the fact that they need to have at least 5 applications.

This results in some companies not being included for further manual checking because they end up lower on the list. You also have to keep in mind that your data sample largly affects the result. If you limit your sample to for example only EP applications, then you will have much less variations because of a better quality at source. Take the query below and add the appln_auth = 'EP' limitation and you will see what I mean.

Code: Select all

select  psn_id, psn_name, count(*)
from tls206_person join tls207_pers_appln on 
	tls206_person.person_id = tls207_pers_appln.person_id
join tls201_appln on tls207_pers_appln.appln_id = tls201_appln.appln_id
where person_name like '%ESSILOR INTERNATIONAL%' and applt_seq_nr > 0
 --and appln_auth = 'ep'
group by psn_id, psn_name
order by count(*)  desc
Bottom line is that the method is not perfect, but it increases the quality dramatically.
In this case, I will ask the suppliers to take an extra look at this applicant so that a better quality will be available for the coming releases.
Best regards,

Geert Boedt
PATSTAT support
Business Use of Patent Information
EPO Vienna


Post Reply