TLS218_DOCDB_FAM
Posted: Sat Jan 04, 2014 7:02 pm
The TLS218_DOCDB_FAM table in PATSTAT October 2013 seems to be a bit off.
The documentation states that: "Generally speaking, if two applications claim exactly the same prior applications as priorities (these can be Paris Convention priorities or just technical relation priorities), then
they are defined by the EPO as belonging to the same DOCDB simple family."
However, I found 4317547 families in which at least one of the members was also a priority. In other words, there's a family with members A and B, where A is the priority of B. See also below for a real example.
There are also cases where the priorities do not match. See below for an example.
I will write a script later to count how many families are affected by this.
Caveat: the problem could be with TLS204 and/or TLS205 instead.
The documentation states that: "Generally speaking, if two applications claim exactly the same prior applications as priorities (these can be Paris Convention priorities or just technical relation priorities), then
they are defined by the EPO as belonging to the same DOCDB simple family."
However, I found 4317547 families in which at least one of the members was also a priority. In other words, there's a family with members A and B, where A is the priority of B. See also below for a real example.
Code: Select all
mysql> SELECT * FROM `tls218_docdb_fam` WHERE `docdb_family_id`=22576;
+----------+-----------------+
| appln_id | docdb_family_id |
+----------+-----------------+
| 2968193 | 22576 |
| 2977272 | 22576 |
+----------+-----------------+
2 rows in set (0.00 sec)
mysql> SELECT * FROM `tls204_appln_prior` WHERE `appln_id` IN (2968193, 2977272);
+----------+----------------+--------------------+
| appln_id | prior_appln_id | prior_appln_seq_nr |
+----------+----------------+--------------------+
| 2977272 | 2968193 | 1 |
+----------+----------------+--------------------+
1 row in set (0.00 sec)
mysql> SELECT * FROM `tls205_tech_rel` WHERE `appln_id` IN (2968193, 2977272);
Empty set (0.03 sec)
I will write a script later to count how many families are affected by this.
Code: Select all
mysql> SELECT *
-> FROM `tls218_docdb_fam`
-> LEFT OUTER JOIN `tls204_appln_prior` ON `tls218_docdb_fam`.`appln_id` = `tls204_appln_prior`.`appln_id`
-> LEFT OUTER JOIN `tls205_tech_rel` ON `tls218_docdb_fam`.`appln_id` = `tls205_tech_rel`.`appln_id`
-> WHERE `docdb_family_id` =9834;
+----------+-----------------+----------+----------------+--------------------+----------+-------------------+
| appln_id | docdb_family_id | appln_id | prior_appln_id | prior_appln_seq_nr | appln_id | tech_rel_appln_id |
+----------+-----------------+----------+----------------+--------------------+----------+-------------------+
| 2416995 | 9834 | NULL | NULL | NULL | NULL | NULL |
| 14298974 | 9834 | NULL | NULL | NULL | NULL | NULL |
| 14298975 | 9834 | 14298975 | 5668479 | 1 | NULL | NULL |
| 36709412 | 9834 | NULL | NULL | NULL | NULL | NULL |
+----------+-----------------+----------+----------------+--------------------+----------+-------------------+
4 rows in set (0.00 sec)