ADVERTORIAL FEATURE
TRADEMARK DATABASES: AN INSIDER’S VIEW
Having made 42 online trademark databases, 12 of which were built in 2011, available to the industry on the search management tool Inspiro and its website, Avantiq has proved its experience and high capacity in the trademark database fi eld. Larissa Best explains.
Forty-two trademark databases mean 38
million trademark documents, with more than 15 million logos. All of that data makes up 716 gigabytes of data on Avantiq’s servers. In order to maintain the data fresh and ready to use, we process 4,500 updates per year.
With the growing number of trademark
applications worldwide, the task of updating the data has become increasingly time-consuming. In 2011 alone, we updated 13 million trademarks.
To be effi cient, we need a strong and eff ective team. For all of this data, we have just six people who do all the work: three IT experts dedicated to database developments and improvements; two operators in charge of updating and maintaining the databases and one offi cer who constantly checks and improves our data quality.
48
The usual development process for a database
1. Acquisition: It is important to fi nd the right partner in order to get the highest standard of quality. T e local patent and trademark offi ce (PTO) would be the fi rst point of contact but may not have any data in an electronic format or may not be interested in selling the data. T e second instance is getting in contact with local service providers and local law fi rms. Aſt er having found the possible partners, you need to exchange data in order to analyse the data quality as well as the data structure. If the samples are adequate and the quality is good, the contract negotiations begin and a provider is chosen. Timeframe: 1 to 6 months
Trademarks Brands and the Internet Volume 1, Issue 3
2. Development: When the data is received, the IT expert will run the fi rst quality checks on the complete set of data. He or she will do a complete analysis of the data and then start the conversion process into the internally used format. A second check is done aſt er the conversion to make sure that none of the quality was lost. Timeframe: 1 to 6 months
3. Testing: The database now becomes available internally to the operations department who will run cross-checks between the official PTO data (if available), the data gathered from local agents and the data available from other service providers (if available). Timeframe: 2 weeks to 1 month
4. Integration: When the database has passed all the checks and verifi cations, the data is made publically available on our web platform
www.worldipreview.com
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56