In order to identify items/services within Makerlab’s context we use ids. These are printed as a QR code that is then placed on each item it refers to, making possible the automation and process simplification mentioned in other components (see wiki or mobile-app).

This implies the existence of labels, and although for the platform itself the simple QR code would suffice, we had to cope with requirements imposed by Makerlab’s technical manager and support labels with different designs and with much more content than the simple code.

Some of the limitations/requirements we had to address include:

• The printer in the room (a special purpose printer to print labels) doesn’t have network connection;
• The computer the printer connects to runs Windows;
• The technical manager already had template labels prepared;
• The labels the technical manager wanted to print do not follow a static structure (i.e. some include a set of fields, others include different fields).

The solution

In order to simplify the issuing of each item’s label, and taking into consideration the arguments made above, we developed a simple application that takes a template label and manipulates the ZPL code (code resembling assembly that the printer understands) so that each label generated actually includes the correct QR code. Then, it sends these labels for printing.

A screenshot of the application follows:

We kept its looks simple and minimalistic since this is not considered a killing feature nor something that will be frequently used. The technical manager said himself he will be using this around once per new batch of items he receives, thus he doesn’t need something really eye-catching.