32539715;32539715;OKAMOTO, DAISUKE;OKAMOTO, DAISUKE;;JP
32539715;64987642;OKAMOTO, Daisuke;岡元 大輔;;JP
32539715;66933187;OKAMOTO, DAISUKE;岡本 大輔;;JP
32539715;67305457;OKAMOTO, Daisuke;ИСИБАСИ Масаюки;;JP
32539715;67895261;OKAMOTO, DAISUKE;岡本 大典;;JP
In the file at this link you will find a mapping table between old records and new records.
The file is 1.3 GB large and is available untill mid-June from this link:
http://webserv.epo.org/download.nsf/0/8 ... enDocument
The file is provided as a one-off exercise for name harmonisation work in the transition between PATSTAT 2018b (Autumn) and the new PATSTAT 2019a (Spring) releases.
Actually, you can (re-)create this file with the query below:
Code: Select all
-- In 2019a some person records of 2018b are split into multiple person records if these
-- person also do have a name in original language (asian, cyrillic or arab character).
-- This query provided a mapping between the PERSON_IDs of 2018b and 2019b.
-- Note that PERSON_IDs do not change in case there is no name in original language.
-- Run time about 15 minutes on a PATSTAT notebook.
-- Indexes on the PERSON_NAMES are a must, otherwise run time is never-ending.
SELECT old.person_id as person_id_2018b, new.person_id as person_id_2019a,
new.person_name, new.person_name_orig_lg, new.person_address, new.person_ctry_code
FROM db_old..tls206_person old
JOIN db_new..tls206_person new on old.person_name = new.person_name
WHERE old.person_address = new.person_address
AND old.person_ctry_code = new.person_ctry_code
ORDER BY person_id_2018b, person_id_2019a
-- Other examples:
-- 48917246 (--> 5 records)
-- 4891735, 48916988 (--> 4 records)
-- 48917410, 48917304 (--> 3 records)