MobileRead Forums - View Single Post

davidfor · 03-01-2017, 06:33 PM

The problem is the column type you are fetching the collections into. The column you are using is probably a text column. When collections are created from these, the value in the column is used as the collection name. What you probably want to use is a tag-like column. These are displayed as a comma separated list. The collection management treats each of these as separate values and creates a collection for each.

The fix for this is to create a tag-like custom column. Then use search and replace in calibre to copy the values from your existing column to the new column. I'm pretty sure this will split the values at the commas. Then change the driver configuration to use the new column. After this, the next time you connect the device, the driver will redo the collections using this column and they should be how you want them.

03-01-2017, 06:33 PM	#275
davidfor Grand Sorcerer Posts: 24,907 Karma: 47303748 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	The problem is the column type you are fetching the collections into. The column you are using is probably a text column. When collections are created from these, the value in the column is used as the collection name. What you probably want to use is a tag-like column. These are displayed as a comma separated list. The collection management treats each of these as separate values and creates a collection for each. The fix for this is to create a tag-like custom column. Then use search and replace in calibre to copy the values from your existing column to the new column. I'm pretty sure this will split the values at the commas. Then change the driver configuration to use the new column. After this, the next time you connect the device, the driver will redo the collections using this column and they should be how you want them.