Author Archives: Ulla

Project diary

October 25th, 2006
Hans Henning Gabriel from 101tec starts working on the new Thinglink site by studying the system architecture. (Photo: Hans on the left and Bissi on the right)



November 1st
Tekes accepts funding to Social Objects project, part of which includes improving the existing Thinglink service.



December, 4.-8., 2006
Jyri, Matt and I meet in London to spec the wireframes for the new service. We spend two days at Moo Cards office and two days at LSE and got a rough idea of what we want.

December 9th, 2006
I contact with Alex Dechamps-Sonsino to agree about her involvement in improving the wireframes and screen designs.



December 14th, 2006
Sami Koskela from a Finnish web design company Valve starts working on the graphic layout.



December 19th, 2006
Juha Törönen from Jaiku starts working on the HTMLs.



December 21st
Graphic layout is ready.

January 3rd, 2007
James Cowan starts working on the backend with Stefan and Hans.

March 1st
The first version of the new service is online. Bug fixing starts. At the same time, Hans is working to finish his thesis.

April 20th
Three things still missing: load tests, URLs and RSS feeds. Hanks will submit his thesis on 27th. After that we should get things ready.

Read More

Porting the old database to the new version

We’re currently porting the thinglink-1.0 database to version 2.0, which means that the server is down for a couple of hours. Expecting to be back soon!

Read More

Thinglink White Paper

Here’s the current version of the Thinglink White Paper that Matt and I wrote during the summer. The purpose of this White Paper is to describe what Thinglink is and how thinglinks can be used. The document is targeted to users and developers of the service as well as any other interested parties. All feedback is most welcome!

Read More

Thinglink on Wikipedia

Now there is also a Wikipedia definition of Thinglink.

Read More

Thinglinks at Helsinki Design Week

To increase the visibility of Finnish design on the Internet, Design Partners encourages people to blog about products at the ongoing Helsinki Design Week exhibition. In collaboration with Design Partners we chose ten young designers and thinglinked their products. We also created “object cards” for these products to give out at the exhibition. An object card contains a unique thinglink code and a web address that points to a specific product. The purpose of this experiment is to:
– create unique identity for unknown design objects on the Internet
– encourage people to discuss about new design ideas and new products on their blogs
– make it easier for bloggers to point at objects
– make it easier for people to learn about objects and their makers
– present objects and designers in relation to other objects and designers presented at the same exhibition.

Featured products at the Design Partners exhibition:

1. Blackbird chair
by Terhi Tuominen

2. Evil lamp
by Markus Viiperi

3. Hobbyhorse lamp
by Jaakko Veijola and Melaja Ltd.

4. 5MM lounge chair
by Mikael Mantila

5. mOrris table
by Kirsi Gullichsen

6. Ash slate
by Kirsi Kivivirta

7. Ikaros carpet
by Ten Twelve

8. Rytmi rocking chair
by Ari Kanerva

9. Blue Jeans & Flax lamps
by Irina Pått

10. Taika veal with paint and pearlescent glaze
by Pentagon Design & Tikkurila

Read More

Using thinglinks in Google Base

Patrick Plaggenborg has written two good posts on Thinglink and Google base. On the representation of things he says:

“The objects (or items as Google refers to them) all need a unique identifier, and that’s where Thinglink appears: the public alternative to the commercial EPC (Electronic Product Code). At the moment Thinglink is doing great, but what they are doing right now is a double job. They provide unique identifiers: the actual thinglinks. But they also allow their users to create a descriptive layer around these things. At that point, Google is doing the same, but better, and gives people more flexibility to create a much more detailed digital representation of the ‘item’ concerned.Thinglink’s job is to provide unique identifiers: Thinglinks. Its website could give a nice overview of thinglinked objects, just like it does now, and it does a great job at that. The descriptive information about things though, belongs in Google Base, because we have more than just thinglinked objects.”

Patrick had also tried to thingtag his thesis on Google Base. This turned out to be not so simple.

“The first problem I came across was the addition of the attribute ‘Thinglink’. Google did not approve this attribute name. After contacting Google about this, they approved it for my particular item, but I’m still unable to add more items and provide them with thinglinks. The second problem is the layout of the actual thinglink. Google Base attributes do not allow colons in them. So it’s impossible to use an attribute name of ‘Thinglink’ (which should be possible as soon as Google approves this attribute for new items) with the value of ‘thing:189THS’.

For us this is very useful discussion, because we’re about to redesign the thinglink service and improve the searchability of things accross the web. Although we strongly encourage using the “thing:” prefix in front of the actual code, we’ve noticed that the code seems to work also without the prefix (see for example 265CII). Still, the search is not fully accurate this way.

Read More

Laser-etched thinglinks

Eric Wilheim from Instructables brought a laser cutter to Foo Camp. It can etch any digital image on metal, plastic or wood. The cutter ran almost uninterrupted through the weekend as campers etched images on their laptops and mobile phones.

Chris Heathcote eched a moomin character on his MacBook (thing:025NNI)

I thinglinked my laptop (thing:686DLP):

Jyri etched a speech bubble on his Powerbook that says ‘Hi! I’m thing:754QFF Check me out on’

The fact that the cutter was so popular suggests people want to personalize and identify objects they own. Specifically, it’s objects like laptops, iPods, phones, bikes, and cars that both express our personality and have a market value.

Read More

Labeling with thinglinks

Ways of labeling objects with thinglinks in physical world:
1) Writing/scratching/burning a thinglink directly on a physical object
2) Attaching a printed thinglink sticker/fabric label/swing ticket to an object or to the package/wrapper of an object
3) Ordering pre-allocated labels with thinglink codes and using them to identify objects

Ways of labeling objects with thinglinks on the Web:
1) Hyperlinking text, images, and other content on the web with thinglink URLs (see thing:636RPE)
2) Using thinglinks as tags on services like Flickr, Delicious, and (example: tag “thing:561BZJ” on this Flickr photo)
3) Annotating objects in photos with thinglink bubbles


Read More

DIY thinglink fabric labels

Printing out thinglink labels on paper is easy. With a little crafting, it’s also possible to make fabric labels. Here’s how I made the labels for Ville’s beanies.

1. I turned an excel file of all thinglinked items into a word file of thinglink labels. The label said: “Hi, I’m thing:123ABC”. Check me out on!”


2. Then I saved the Word file as PDF and flipped it into a mirror image in Photoshop

3. I printed them on iron-on transparencies.

4. I ironed the sheets on a white cotton fabric.

5. I removed the paper on the back.

4. Now the labels were ready for cutting and sewing.

Read More

The Thinglink data model

This post describes the data model on the kinds of information that the site knows about, their fields, and the relationships between them.

Let’s start with a diagram:

You could also read A URL design for, published previously on this blog, to get an idea of how this data model translates onto the website.

Each of the boxes in that diagram is represented in the thinglink database with a number of fields and relationships:


The thinglink is the core of the data model. As can be seen from the diagram, all other data on references a thinglink. A thinglink has the following fields:


  • code (e.g. 123ABC)

  • title

  • description

  • createDate

  • viewCount (incremented every time someone views the thinglink’s webpage)

  • photo (ID, url, thumbnail URL and title)

  • linker (the user who created this thinglink)

  • maker (one or more people who made the thing that this thinglink represents)


In order to comment or to create or edit a thinglink, users must be logged into the site. User records have the following fields:


  • name

  • password

  • email

  • bio

  • homepage

  • flickr ID and username


Thinglink tags are the same concept as flickr tags: a folksonomy made up of text strings attached to thinglinks.

Unlike flickr, tags may only be added, edited or deleted from a thinglink by the user who created the thinglink. Tags are presented on thinglink pages, and in a list on the homepage showing the most popular tags.


The labeling area of is currently under development and no label data is stored in the database.

flickr picture

A picture from the user’s flickr account can be associated with a thinglink. The data about this association is stored in the thinglink table as described above. The flickr picture is displayed with the thinglink in thumbnail or fullsize form wherever appropriate.


A thinglink may have the country of its origin listed. Countries are chosen from a controlled list in a dropdown on when the thinglink is created or edited. A list of popular countries is displayed on the homepage.


A thinglink may have the year of its making stated when the thinglink is created or edited. A list of popular years is displayed on the homepage.

Read More
1 8 9 10 11 12 14