Claw Dee Puss
Posts: 213
Joined: 3/11/2014
From: Portugal (via England)
Status: offline
|
(With Eric's permission, I'm posting this)
CellarTracker is basically a wine database with a lot of reporting and summarising options.
However, I found a while back that there were a number of things I wanted to do that I simply couldn't. Most (possibly all) of these were pretty "me" specific, so were unlikely to ever get into the software - I like to see charts, I like to associate a "future drink date" to schedule (more or less) the next time to think about drinking a wine (and didn't want to abuse the on-site drink dates), I wanted a "weekly" summary of what I'd drunk, to export data in a manner suitable for subsequent import to Memento on my Android for offline use, to "classify" wines, to save selections of wine to my google drive for picking out when down in the cellar, etc etc
This is what the "Home Page" for a wine looks like (it's always a work in progress)...
Of course, there are many 3rd party databases out there, and for any many years I've used FileMaker for this kind of thing. Seeing as how you can export the data from CT to an XML file (see Exporting from CT) - so that ought to, I thought, have been an easy thing.
But it transpired to not be quite so easy as I thought - in order for FileMaker to "understand" the XML, it needs a separate file called an XLST StyleSheet. So I set about writing one of those, which is what I'm making public now ...
http://www.mediafire.com/file/3h9ige43agujjyy/CT_XML_StyleSheet.xslt
https://www.4shared.com/file/jXCsfVnxca/CT_XML_StyleSheet.html
(These are the same file in 2 different places)
What this allows you to do is import CTs exported XML files into FileMaker - and it's wicked fast - so fast that, once a week when I update my database from the Ct site, I simply delete all existing records and re-import the whole lot. Since my "additional" fields are in separate tables, linked by the unique WineID, PurchaseID etc etc, nothing I've added myself is deleted. Once the data is there the full power of FileMaker is at your disposal.
Interestingly, if you start with an empty FileMaker database, and import to a "New Table", all the fields in that XML will be created within a new table - a great way to get going.
This has worked for me for a number of years now - on a Macintosh running OSX.
XML is XML, and XLST is XSLT, so it ought to work on a PC too, but I have no way to verify that.
Note: The instructions for exporting on the CT are correct, but a small "gotcha" is that, if you're exporting from outside a browser in which you're logged in to CT, for example from within FileMaker itself, when you put in "UserHandle" if it contains spaces you need to encode them...
https://www.cellartracker.com/xlquery.asp?User=your_handle&Password=your_password&Format=xml&Table=Notes
becomes...
https://www.cellartracker.com/xlquery.asp?User=Claw%20Dee%20Puss&Password=your_password&Format=xml&Table=Notes
|
Printable Version
Importing CellarTracker XML to FileMaker - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread