MobileRead Forums - View Single Post - Since Kobo update, series information doesn't transfer to device

davidfor · 11-17-2021, 10:57 PM

At this point you have to decide how you want to define collections. Is there existing metadata in the library that you want to base the collections on? If so, use that column. This is why the tags column is mentioned so often with respect to collections. It is an obvious way to arrange the books. Or using Genre. And why Series was so popular. I have mentioned the types of columns I use for collections.

Or, you could just use your collections column. This has the way you have manually done it, so it might be the way to do it going forwards. That works especially if your collections are fairly ad hoc.

Having said that, I probably wouldn't use this column. I would probably create another, and copy the current values to it (using the search-and-replace). Then use one as a backup that you can restore from later if you don't like how whatever you were doing. Or at least have something to refer back to and see what you might be missing.

So basically, the next step it is choose the columns you want to use and set them as the collection columns in the driver. Then connect the device. You can always change later and the driver will update the collections the next time you connect.

11-17-2021, 10:57 PM	#35
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	At this point you have to decide how you want to define collections. Is there existing metadata in the library that you want to base the collections on? If so, use that column. This is why the tags column is mentioned so often with respect to collections. It is an obvious way to arrange the books. Or using Genre. And why Series was so popular. I have mentioned the types of columns I use for collections. Or, you could just use your collections column. This has the way you have manually done it, so it might be the way to do it going forwards. That works especially if your collections are fairly ad hoc. Having said that, I probably wouldn't use this column. I would probably create another, and copy the current values to it (using the search-and-replace). Then use one as a backup that you can restore from later if you don't like how whatever you were doing. Or at least have something to refer back to and see what you might be missing. So basically, the next step it is choose the columns you want to use and set them as the collection columns in the driver. Then connect the device. You can always change later and the driver will update the collections the next time you connect.