ECONOMIADELLARICERCA.INFO

rawpatentdata.blogspot.com

Rawpatentdata: June 2015

http://rawpatentdata.blogspot.com/2015_06_01_archive.html

Sunday, June 21, 2015. Patstat 2015a upload scripts for mysql. As from EPO cover letter 2015a ediction of patstat brings a lot of changes. (you may find here. Https:/ dl.dropboxusercontent.com/u/3004945/rawpatentdata/patstat2015amysql.zip. It's possible to download my scripts for mysql allowing to upload the majority of tables from ediction 2015a of patstat;. Please note I uploaded the new TLS906 in TLS206 in order to make smoother the db steps that follow the import of patstat data. Sunday, June 14, 2015.

rawpatentdata.blogspot.com

Rawpatentdata: May 2015

http://rawpatentdata.blogspot.com/2015_05_01_archive.html

Sunday, May 10, 2015. Patstat Count of applications by application authority (on 2014b version). A quick statistic allowing to understand the coverage of patstat allover the 173 application authorities listed in the DB. Counts also show the first and last applciation year (some have to be taken with some caveat, FI 1904 for DD that had been created in 1946.). Counts exclude D1 and D2 application kind and those with applciation year 9999. Http:/ www.stevemorse.org/jcal/countries.html. Formerly Zaire now CD.

rawpatentdata.blogspot.com

Rawpatentdata: January 2014

http://rawpatentdata.blogspot.com/2014_01_01_archive.html

Friday, January 31, 2014. IPCs missing in october 2013 ediction. This year patstat ediction came with some deficiency in table TLS209. EPO itself send a letter to all users. Dear PATSTAT users,. If you do not use IPC codes for your analyses, then you don’t need to take any action. We have looked at various options to solve the observed problem, and offer the following remedies:. The script needs be adapted to your own environment, e.g. by changing the data base name and/or table names. 2) User who do not...

rawpatentdata.blogspot.com

Rawpatentdata: Patstat CPCs counts by patent office

http://rawpatentdata.blogspot.com/2015/07/patstat-cpcs-counts-by-patent-office.html

Wednesday, July 8, 2015. Patstat CPCs counts by patent office. Recently I had to try to understand how good is the coverage of patstat in terms of CPCs for some of the most relevant application authorities. Obviously there is no benchmark data available, thus the main concept I used was a comparison of average number of Cpcs by application authority/year in order to display whether the baseline had some discontinuities. I also dropped data where the number of applications was below 10k. CPC VALUE gives i...

rawpatentdata.blogspot.com

Rawpatentdata: February 2014

http://rawpatentdata.blogspot.com/2014_02_01_archive.html

Friday, February 28, 2014. Patent counts by ipc35 and nace. Just a couple of table, adding up and comparing patents counts (fractionals) by NACE rev 1.1 and IPC35 reclassification for october 2012 and 2013 patstat ediction, for EP, PCT and USPTO application authorities. Subscribe to: Posts (Atom). Is licensed under a Creative Commons Attribuzione-Non commerciale-Condividi allo stesso modo 3.0 Unported License. Contacts: gianluca.tarasconi@gmail.com. Patent counts by ipc35 and nace.

rawpatentdata.blogspot.com

Rawpatentdata: October 2014

http://rawpatentdata.blogspot.com/2014_10_01_archive.html

Monday, October 13, 2014. Differences of inventors within the same docdb family (part II). Continues from previous post. As previously stated, 95% of docdb families contain applications with the same number of inventors;. Obviously it may also happen that part of inventors change among the applications. Thus we must check how deep is the variance of person ids within the same docdb family. Here we see the results (sql code appended in the end of this post):. Two results are interesting:. Select t18.D...

rawpatentdata.blogspot.com

Rawpatentdata: April 2015

http://rawpatentdata.blogspot.com/2015_04_01_archive.html

Monday, April 27, 2015. Allow me a post of self advertisment:. Just to announce PATSTAT revisited, IDE Discussion Papers No.527,. Http:/ www.ide.go.jp/English/Publish/Download/Dp/527.html. Written by me and Byeongwoo Kang. PATSTAT, patent data analysis, innovation studies. O39, Y20, Z00. Thursday, April 2, 2015. Presentations from Information tools for IP and Intelligence Meeting. Some interesting topics have been developed @ Information tools for IP and Intelligence Meeting last 26 and 27 march, like:.

rawpatentdata.blogspot.com

Rawpatentdata: March 2015

http://rawpatentdata.blogspot.com/2015_03_01_archive.html

Monday, March 16, 2015. Who owns this patent? Following other previous posts, I return on the issue of ownership changes in Patstat. The goal is to understand what applicant is available, given a change of ownership. I'll refer from here onward only to EPO patents. We may find such applications when looking into inpadoc legal data (TLS221 prs code="RAP1" or prs code="RAP2") . For the example I'll use appln id 216544 that is patent EP1197791. T11APPLN ID, t11.PUBLN NR, t11.PUBLN KIND,. T27applt seq nr 0;.

rawpatentdata.blogspot.com

Rawpatentdata: May 2014

http://rawpatentdata.blogspot.com/2014_05_01_archive.html

Thursday, May 8, 2014. Patenting in the south: an analisys of BRICS country patent offices data. I share this presentation whose goal is to analyze EPO PATSTAT as data source for BRICS countries and its advantages and disadvantages. Inm appendix sql code for extracting the data I presented. Patenting in the south. Labels: national patents data. Subscribe to: Posts (Atom). Is licensed under a Creative Commons Attribuzione-Non commerciale-Condividi allo stesso modo 3.0 Unported License.

rawpatentdata.blogspot.com

Rawpatentdata: April 2014

http://rawpatentdata.blogspot.com/2014_04_01_archive.html

Wednesday, April 30, 2014. Fixing 'see applicant' issue in patstat TLS207. Among the gift brought from EPO with oct. 2013 version, there is a change that is quite a worstening of data quality, since for a big number of applications (140.700: all of them at EP application authority) instead of the correct reference to the inventor person id TLS207 lists person id 96 whose name (see applicant) do not let us presume it is a valid entry. Fixes for SEE APPLICANT (person id 96) on TLS207. Back up old TLS207.