I'm in the middle of uploading the latest PATSTAT version, and I encounter a problem I already reported years ago: the suggested primary key for table PERS_APPLN is not valid, i.e. the combination of fields PERSON_ID and APPLN_ID is not unique. First of all, the suggested primary key is not the logi...

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 a...

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). Th...

Thank you for your efforts to answer my question, but I'm afraid you miss my point. I do understand the issue of artificial applications and hence the fact you might find duplicate records for the same APPLN_ID, hence those 3,514 duplicate results for DE, all having 'D2' as kind code. That can be so...

After years of working with the 2009 version of PATSTAT, I recently switched to the latest one. By looking at the documentation of the new version, I feel a bit uncomfortable on how to count distinct patent applications - and I see I'm not the only one having this question. In previous versions, I r...