Mismatch artificial applications due to claimed priorities

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

ndbac41
Posts: 6
Joined: Mon May 07, 2007 6:18 pm

Mismatch artificial applications due to claimed priorities

Post by ndbac41 » Wed Dec 11, 2013 3:54 pm

I'm checking artificial application records due to claimed priorities (applications claiming a priority that cannot be found in DocDB).

According to the PATSTAT documentation (PATSTAT October 2013), these artificial application records can be identified by APPLN_ID (range 900000001 to 930000000).

There are 7,099,488 such records in table APPLN.

However, looking at PRIOR_APPLN_ID in table APPLN_PRIOR, only 5,502,793 distinct PRIOR_APPLN_ID's fall in that range.

With other words, 1,596,695 artificial application records due to claimed priorities are not present in table APPLN_PRIOR, which means they are not claimed as priority.

Why are these artificial application records due to claimed priority present in table APPLN if they are not claimed as priority?

Regards,
Tom Magerman


nico.rasters
Posts: 140
Joined: Wed Jul 08, 2009 5:51 pm
Contact:

Re: Mismatch artificial applications due to claimed prioriti

Post by nico.rasters » Wed Dec 11, 2013 9:33 pm

Hi Tom, I am probably misreading your post or the documentation, but...
Isn't this the range for priorities applications, in other words for priorities?
Priorities are not present in APPLN_PRIOR.
________________________________________
Nico Doranov
Data Manager

Daigu Academic Services & Data Stewardship
http://www.daigu.nl/


ndbac41
Posts: 6
Joined: Mon May 07, 2007 6:18 pm

Re: Mismatch artificial applications due to claimed prioriti

Post by ndbac41 » Thu Dec 12, 2013 3:02 pm

Thank you Nico for your quick response. However, I'm confused now, APPLN_PRIOR does not contain priority claims? What does it contain according to you?

I thought table APPLN_PRIOR contains the ID's of all claimed priorities (PRIOR_APPLN_ID) for a given application (defined by APPLN_ID). Hence, all artificial application records added to table APPLN because of priority claims missing in DocDB, must be present in field PRIOR_APPLN_ID in table APPLN_PRIOR. But they are not, many artificial applications due to unmatchable claimed priorities are not present in table APPLN_PRIOR, so why are they present in table APPLN?

Regards,
Tom


nico.rasters
Posts: 140
Joined: Wed Jul 08, 2009 5:51 pm
Contact:

Re: Mismatch artificial applications due to claimed prioriti

Post by nico.rasters » Thu Dec 12, 2013 3:27 pm

Sorry, just reread your post and yes, one would expect to find all APPLN_IDs in the range 900000001 to 930000000 to be present in the field `PRIOR_APPLN_ID` in TLS204_APPLN_PRIOR.
Somehow I misread that you could not find these applications in (`APPLN_ID` in) TLS204.

Could they be in TLS216_CONTN instead?
I'm in the process of installing October 2013 so I can not check it myself at the moment.
________________________________________
Nico Doranov
Data Manager

Daigu Academic Services & Data Stewardship
http://www.daigu.nl/


mkracker
Posts: 114
Joined: Wed Sep 04, 2013 6:17 am
Location: Vienna

Re: Mismatch artificial applications due to claimed prioriti

Post by mkracker » Wed Dec 18, 2013 4:36 pm

Hi Tom,
By “priority” in PATSTAT we mean not only “Paris Convention priority”, but also other types of priorities which link one application to a, “prior” application. The various types of priorities are stored in separate tables:

• TLS201_APPLN
An PCT application in its regional/national phase contains in its attribute INTERNAT_APPLN_ID the APPLN_ID of its original PCT application.

• TLS204_APPLN_PRIOR
contains Paris Convention priorities

• TLS205_TECH_REL
contains links between technically equivalent applications

• TLS216_APPLN_CONTN
contains various relations like continuations, divisional applications, ...

For verification, I used this query which - as expected - returns 0 rows.

select *
from tls201_appln
where appln_id between 900000001 and 930000000
and appln_id not in (select internat_appln_id from tls201_appln)
and appln_id not in (select prior_appln_id from tls204_appln_prior)
and appln_id not in (select tech_rel_appln_id from tls205_tech_rel)
and appln_id not in (select parent_appln_id from tls216_appln_contn)

Thanks for raising this questions. I will improve the explanatio in the next version of the Data Catalog to make it clearer.

Best regards,
Martin Kracker
EPO - PATSTAT
-------------------------------------------
Martin Kracker / EPO


Post Reply