Auto-add imported folder to collection with same name

[truth1ness]

Is this possible? Whenever I import a folder I usually manually create a collection for those books as they often are a logical collection of books and also so I can keep track of where they came from. It'd be cool if it could pull in the name of the folder and auto-group the imported books into a collection.

[theducks]

Originally Posted by truth1ness

Is this possible? Whenever I import a folder I usually manually create a collection for those books as they often are a logical collection of books and also so I can keep track of where they came from. It'd be cool if it could pull in the name of the folder and auto-group the imported books into a collection.

Calibre add is PATH unaware.
Saying another way: No metadata from anything but the filename (filename mode)

A (normal ?) ADD CAN apply a TAG. Preferences: Adding Books

[BetterRed]

@truth1ness - for this situation, I have used a renamer to tack the path onto the end of the file name, which I write to the publisher column, and from their I've used Bulk S&R to stick it elsewhere. Usually they're all from the same publisher so while I'm there I 'correct' it in Bulk Metadata Edit (Basic).

And I do all this in my "NewBooks' library as mentoined here When I import and duplicates are detected how do I delete the old copy?

This is another instance where the ability to populate a custom column with the 'path' of the original import would be useful. It has come up quite often, eschwartz has a solution of some sort.

BR

[eschwartz]

BR -- it is very custom, unfortunately.

It relies on bash, so it won't work on Windows, and uses hardcoded assumptions about what a filename must look like. I'd like to fix that, but I don't know how to deal with named capturing groups purely in bash+universal utilities.

It shouldn't be too hard though, to simply chain together calibredb add $file ==> $added_book_id ==> calibredb set_metadata -f "field1:contents1" $added_bookid
The trick is to extract the right information from the path, and especially what to do if some of it is optional.

[BetterRed]

Originally Posted by eschwartz

BR -- it is very custom, unfortunately.

It relies on bash, so it won't work on Windows, and uses hardcoded assumptions about what a filename must look like. I'd like to fix that, but I don't know how to deal with named capturing groups purely in bash+universal utilities.

It shouldn't be too hard though, to simply chain together calibredb add $file ==> $added_book_id ==> calibredb set_metadata -f "field1:contents1" $added_bookid
The trick is to extract the right information from the path, and especially what to do if some of it is optional.

@eschwartz - yes, I sort of knew that, but better to let the horse speak for itself.

My method is likewise bespoke, enscapulated in saved rename & saved S&R, I don't need it often enough to make it better'n that.

BR