I had a #kobopath composite used to categorize my books at the top level. The full save path is:
Here's the template I was using for the column itself:
For fanfics, I used Fanfiction/Fandom entries to sort them into subfolders. This worked perfectly fine when it was a composite column.
However, I turned the column into a text column because it was impacting performance too much and I only needed it for books I want on the device. In the unlikely case this matters, I created #kobopath2, used search & replace to copy everything over, deleted the original column and then removed the 2 from the lookup key.
I still use the template to update the column with Action Chains.
It has the same Fanfiction/Fandom as before, but now Calibre turns the slashes into underscores and breaks the subfoldering:
Attachment 189345
I tried inverting the slash, but that didn't work.
Any idea what I should do? I figure it's deliberate, but I'm not sure why it only affect non-composite columns.
My fallback plan would be to just entirely drop the second part. I'd rather not do this. Sending all those fanfics to device again would be a hassle.
Code:
{#kobopath}/{author_sort:sublist(0,1,&)}/{title} - {authors}Code:
program:
# Returns 'Fanfiction/Fandom' for fanfics
if $$#fanficcat then
re(sublist($tags, 0, 1, ','), '\.', '/')
# Returns 'PDF' for PDFs
elif $formats == 'PDF' then
'PDF'
# Returns 'Loans' for Loans
elif $#kobostatus == 'On Loan' then
'Loans'
# Returns blank for paperbooks
# This bit isn't needed anymore
# elif $formats == 'PAPERBOOK' then
# ''
# Returns topmost tag for all other books
else
re(sublist($tags, 0, 1, ','), '^(.*?)($|\..*$)', '\1')
fiFor fanfics, I used Fanfiction/Fandom entries to sort them into subfolders. This worked perfectly fine when it was a composite column.
However, I turned the column into a text column because it was impacting performance too much and I only needed it for books I want on the device. In the unlikely case this matters, I created #kobopath2, used search & replace to copy everything over, deleted the original column and then removed the 2 from the lookup key.
I still use the template to update the column with Action Chains.
It has the same Fanfiction/Fandom as before, but now Calibre turns the slashes into underscores and breaks the subfoldering:
Attachment 189345
I tried inverting the slash, but that didn't work.
Any idea what I should do? I figure it's deliberate, but I'm not sure why it only affect non-composite columns.
My fallback plan would be to just entirely drop the second part. I'd rather not do this. Sending all those fanfics to device again would be a hassle.