Quote:
Originally Posted by Starson17
As an aside (that you probably already know), at about that time there was a similar issue with Automerge on when combined with Copy to Library with deletion from the source library. Changes were made to the CTL code at that time.
|
I didn't know that.
Quote:
Originally Posted by Starson17
I was able to replicate this when the Save to Disk template includes only the {authors} and {title} fields. In that case, it's trying to create two books with identical names. I think it should probably be fixed to produce an error message, and/or offer to modify the names to make them unique. I'd suggest adding a bug report to at least make a record of the issue.
|
I'll do a bug report when I have time and figure out how to do one, since I've never done one before. Oops, I should have specified my Save Template in original post, but you're right, that
is the sort of template I'd been using. I hadn't thought of it as the culprit, but it makes sense in hindsight now that you pointed it out. Here's the exact template I was using:
Code:
{author_sort}/{title}/{title} - {authors}
Quote:
Originally Posted by Starson17
[re: Copy To Library not having this behavior] Correct (mostly). If Automerge is off, it will see this as a Duplicate and ask if you want to add the duplicate book. If Automerge is on, it will obey the options for Automerge (one of which is to silently ignore the duplicate).
|
Good to know, though normally I don't use Automerge at all.
Quote:
Originally Posted by Starson17
[re: not necessarily a bug] It should probably at least give a warning.
|
I agree, since I believe that is the default Save template after install, which most users are using.
Quote:
Originally Posted by Starson17
Another workaround would be to make sure your save template has a unique field for the name or folder. You could add a column for version number, only populate that field when you have multiple versions, and use a save template that ignores that field unless it's populated.
|
Good idea, except I prefer to put version and edition info in parentheses after title, to minimize the number of custom columns.
Quote:
Originally Posted by chaley
You could also add {id} to the template. This adds calibre's internal ID to the path (a number), which is guaranteed to be unique for a given library.
|
Great idea, since that doesn't need an extra column. So I just did that, using double parentheses around the {id} to enable easy handling later with a new Add from filename regex if necessary. That should completely solve the problem. Anyway, my new save template is:
Code:
{author_sort}/{title}/{title} - {authors} - (({id}))
Thank you both.