Plugin to trasform database to upper case

[JimmXinu]

I'd forgotten that searches are case insensitive, so the regexp search doesn't work, sorry.

Getting and setting custom column values is pretty easy:

existing=db.get_custom(book_id,label=label,index_is_id=True)

db.set_custom(book_id, value, label=label, commit=True)

Where label is the # name, like #wordcount, or whatever you set it to.

(added) And, of course, you can use the custom column for the search instead of the regexps.

[Xwang]

Originally Posted by JimmXinu

I'd forgotten that searches are case insensitive, so the regexp search doesn't work, sorry.

Getting and setting custom column values is pretty easy:

existing=db.get_custom(book_id,label=label,index_is_id=True)

db.set_custom(book_id, value, label=label, commit=True)

Where label is the # name, like #wordcount, or whatever you set it to.

(added) And, of course, you can use the custom column for the search instead of the regexps.

I've done as you suggested and also this problem seem solved.
I attach the latest version just in case it is useful to someone else (in the next few days I will try on windows and on my huge collection of about 1000 books).
Xwang

[Xwang]

I attach the newer version in which I use the string "_T[##]" as a prefix before title and author name, instead of using it at their end (I've thought that since under Windows the folder and file name can be cut with respect to the title inside metadata, it is possible that the special string is washed out creating issues).
This version works well, but their still a problem with the mixed use of linux and windows.
The problem is originated by the 256 character windows limit on complete path length.
I've discovered that using the plugin under linux, it creates a lot of book with an excessively long path.
So I wonder if it is possible to modify the plugin so that to limit the length of file and directory name maintaining the full title in the metadata.
Thank you,
Xwang

[JimmXinu]

Originally Posted by Xwang

The problem is originated by the 256 character windows limit on complete path length.
I've discovered that using the plugin under linux, it creates a lot of book with an excessively long path.
So I wonder if it is possible to modify the plugin so that to limit the length of file and directory name maintaining the full title in the metadata.

No, there isn't, calibre doesn't allow you to control the file names directly.

But since you're already changing the title/authors, you can do other things. Replace common words/phrases with abbreviations: 'Federal Aviation Administration' with 'FAA', etc.

mi.title = mi.title.replace('Federal Aviation Administration','FAA')

You can also force them to be no more than a max length something like so:

mi.title = mi.title.replace('Federal Aviation Administration','FAA')
mi.title = mi.title[:-5][:100]

Jim

[Xwang]

Originally Posted by JimmXinu

No, there isn't, calibre doesn't allow you to control the file names directly.

But since you're already changing the title/authors, you can do other things. Replace common words/phrases with abbreviations: 'Federal Aviation Administration' with 'FAA', etc.

mi.title = mi.title.replace('Federal Aviation Administration','FAA')

You can also force them to be no more than a max length something like so:

mi.title = mi.title.replace('Federal Aviation Administration','FAA')
mi.title = mi.title[:-5][:100]

Jim

Maybe I can add field to my db to maintain the entire title in case the original one is too long (so that to not waste info maybe useful in the future).
The check on the length of the title should be run every time the "OK" button is pushed on the metadata GUI, so that to avoid the long filename is created at all.
Is it possible to link a plugin function to such an action?
Otherwise I can create a plugin to scan for the entire library in a manner similar to this one to cut the title if necessary by saving the entire title in the additional db field.
Xwang

[Xwang]

Sorry if I reopen this thread but I've discovered that the plugin is loaded in the newer Calibre version, but there is no possibility to add the button that is needed to run it. I'm missing something?

[JimmXinu]

Your plugin hasn't been through the conversion to Qt5 from several years back. Here's a contemporary thread about it.