Quote:
Originally Posted by PeterT
Why not just make one new library in the GUI and save it as a template?
Then possibly all you need to do is to create a new directory and copy the template metadata.db into the new directory?
|
PeterT, but...
That's what I do now mate.
When I change library specific preferences or create a new VL or something like that, then I need to create a new template; but in the 'heat of the moment' I often forget to do that. Also I don't want the templates to be visible in Calibre until I really need them to effect a repair, so after creating fresh templates I then remove them from Calibre. I then I have to explain to those who look over my shoulder why I just did that
So what I want to do is to automate the creation of fresh templates as part of my end-of-day process. I don't care if they are the same as yesterday's, at least when tomorrow comes I will know they are up to date as at the end of the new yesterday
.
If I have a disaster I want to be able to rebuild the Calibre libraries from the raw materials that I keep on my FTP server space. The templates are a part of that raw material inventory. And Calibre is a fraction of the data I would want to to rebuild in the event of disaster.
I should have stated what I was trying to do in the first instance, but given the responses I got to a 17 word sentence, I suspect another couple of sentences would only added to the confusion.
Cheers BR