Since Calibre keeps track of the unique hardware ID of individual devices (in a
driveinfo.calibre file on each device - e.g.
Quote:
|
{"device_store_uuid": "305c6bb2-676a-4c31-a65a-e0d7c838812e", "prefix": "/media/disk/", "device_name": "Kobo Reader", "calibre_version": "0.7.50", "location_code": "A", "last_library_uuid": "096e45b3-d298-44d1-9393-63f22fe9eb58", "date_last_connected": "2011-03-18T22:02:59.604058+00:00"}
|
and
Quote:
|
{"device_store_uuid": "948b1d5d-7415-40f7-bf23-15fd7d0100a0", "prefix": "/media/disk/", "device_name": "Kobo Reader", "calibre_version": "0.7.50", "location_code": "A", "last_library_uuid": null, "date_last_connected": "2011-03-25T19:39:57.104684+00:00"}
|
and
Quote:
|
{"device_store_uuid": "c2a830cb-cb36-4ec9-abfd-033103b58e54", "prefix": "/media/KOBOeReader/", "device_name": "Kobo Reader", "calibre_version": "0.7.50", "location_code": "main", "last_library_uuid": null, "date_last_connected": "2011-03-25T19:39:57.093929+00:00"}
|
)
as well as whether the device is the reader itself or a card (see location_code, above), would it be possible to read in that device_store_uuid and use it to reference a new field (perhaps named something like "OnMedia"), ideally with the option of letting the user (re)define the actual contents of the new field (i.e. "SD-A", "Card01", "4G_Card", etc)?
Failing that, could that ID be exposed via the template system so a user could point it at a custom column?
If I were familiar with Python, I'd have a go at doing it myself, but...
