View Single Post
Old 07-12-2024, 02:07 PM   #4
meghane_e
Zealot
meghane_e juggles running chainsaws for a bit of light exercisemeghane_e juggles running chainsaws for a bit of light exercisemeghane_e juggles running chainsaws for a bit of light exercisemeghane_e juggles running chainsaws for a bit of light exercisemeghane_e juggles running chainsaws for a bit of light exercisemeghane_e juggles running chainsaws for a bit of light exercisemeghane_e juggles running chainsaws for a bit of light exercisemeghane_e juggles running chainsaws for a bit of light exercisemeghane_e juggles running chainsaws for a bit of light exercisemeghane_e juggles running chainsaws for a bit of light exercisemeghane_e juggles running chainsaws for a bit of light exercise
 
Posts: 116
Karma: 38500
Join Date: Sep 2016
Location: San Jose, CA
Device: Kindle moving to Kobo or Boox
Quote:
Originally Posted by Comfy.n View Post
Last Modified may be helpful
This is awesome to know about going forward, but for the old libraries, especially pre-2020, this plugin requires "that you must add at least one custom date column to be able to use this plugin". So anything I do now will automatically change the default last_modified column, which would defeat the goal.

For the short term, I'm going to start by making a complete CSV file for each library that contains all the preexisting data, then add a #custom_last_modified column to each library. At that point, I'll have to probably write a script to to fill in the #custom_last_modified data using calibredb and the CSV file data. If I get really ambitious, I might add some other columns like #last_merged and #last_library that get filled in by a Template function. Considering the number of old libraries and backups, maybe a small database to track data changes would be more useful. Getting into the project-creep at this point.

Otherwise, thanks for the pointers!!
meghane_e is offline   Reply With Quote