MobileRead Forums - View Single Post - using re() and shorten() for custom comments column?

rebl · 09-07-2014, 04:58 AM

chaley and eschwartz - Thank you guys, very much! You are awesome.
You've put me on the right track and from now on I think I can manage.
Of course a little trial and error can't hurt

I don't have that many non-empty comments fields and I doubt many of them would contain "un-ampersanded" > or < characters... (> is a html entity right?)
I need the comments filed because that was the only field I could think of, to store the "version" of a book, when reading metadata from the file name

Code:

john milton - paradise lost from guttenberg v1.1.rtf

I'm using a modified regex from "quick preferences" plugin:

Code:

^(?P<author>((?!\s-\s).)+)\s-\s(?:(?:\[\s*)?(?P<series>[^\[\]\(\)\d]+)(?:\s*\])?\s?(?P<series_index>[\d\.]+)(?:\s*\])?\s-\s)?(?P<title>.+)\s?v\.?(?P<comments>[^\[\]\(\)]+)(?:\s*\]\))?$

to get the version number and put it in the comments field.
The regex above puts 1.1 in the comments field.
Than I just need to display a part of the comments field in a custom column, in order to be able to sort and see which "comment" contain a version number.
But the fact that comments is a html field complicates things.
Since I am not allowed to use custom fields such as #vers I needed to use a built-in one.
But I guess it'd be simpler to use a different predefined filed that I have no use (initially) for temporary storing the "version number" - for example publisher... it doesn't matter which, 'cos I will anyway have to use "search replace" in metadata....

That is assuming I am definitely not allowed to use something like ?P<#version> when adding books...

09-07-2014, 04:58 AM	#9
rebl r.eads e.njoys b.ooks lol Posts: 76 Karma: 580748 Join Date: Mar 2010 Location: It's time to get this Book a Rest Device: Kindle 4 NT	chaley and eschwartz - Thank you guys, very much! You are awesome. You've put me on the right track and from now on I think I can manage. Of course a little trial and error can't hurt I don't have that many non-empty comments fields and I doubt many of them would contain "un-ampersanded" > or < characters... (> is a html entity right?) I need the comments filed because that was the only field I could think of, to store the "version" of a book, when reading metadata from the file name Code: john milton - paradise lost from guttenberg v1.1.rtf I'm using a modified regex from "quick preferences" plugin: Code: ^(?P<author>((?!\s-\s).)+)\s-\s(?:(?:\[\s)?(?P<series>[^\[\]\(\)\d]+)(?:\s\])?\s?(?P<series_index>[\d\.]+)(?:\s\])?\s-\s)?(?P<title>.+)\s?v\.?(?P<comments>[^\[\]\(\)]+)(?:\s\]\))?$ to get the version number and put it in the comments field. The regex above puts 1.1 in the comments field. Than I just need to display a part of the comments field in a custom column, in order to be able to sort and see which "comment" contain a version number. But the fact that comments is a html field complicates things. Since I am not allowed to use custom fields such as #vers I needed to use a built-in one. But I guess it'd be simpler to use a different predefined filed that I have no use (initially) for temporary storing the "version number" - for example publisher... it doesn't matter which, 'cos I will anyway have to use "search replace" in metadata.... That is assuming I am definitely not allowed to use something like ?P<#version> when adding books... Last edited by rebl; 09-07-2014 at 05:05 AM.