Plugboard, template, and custom composite column recipes

[thiago.eec]

Originally Posted by BetterRed

The only reason I can imagine one would want to select multiple authors in Manage authors would be to attach the same note to multiple authors, but a subsequent change or delete in one author would not ripple through to other authors.


Works for me, viz:

Attachment 211728

BR

The reason I wanted to select multiple books would be to use th GR Notes Plugin.

And the error only happens with calibre preview. @chaley already fixed it.

[ownedbycats]

Originally Posted by BetterRed

Works for me, viz:

Attachment 211728

BR

Are you on 7.20 or 7.20.100? The change was made between the two (#2085152).

[BetterRed]

Originally Posted by thiago.eec

The reason I wanted to select multiple books would be to use th GR Notes Plugin.

Ah-ha - I don't use that plugin or anything like it.

Originally Posted by ownedbycats

Are you on 7.20 or 7.20.100? The change was made between the two (#2085152).

I use the current installable version - so 7.20.

I install the portable version of preview releases so that I can see what's coming but I don't use it 'in anger', and I would only refer to it here if I had a problem with it.

BR

[ownedbycats]

program:

	arguments(date, colourA, colourB, colourC);
	now = format_date(today(), 'yyyy-MM-dd');

	if days_between(now,date) <#1 then colourA
	elif days_between(now,date) <=#7 then colourB
	elif days_between(now,date) <=#30 then colourC 
	fi

A shortcut template I use for column colouring, like such:

colours_daysbetween($#lastread, '#00aaff', '#69cfff', '#9bdeff')

[ownedbycats]

From chaley is this template which can be used to search for series with more than one book:

Originally Posted by chaley

This template search should be fast enough to use in a VL. You probably want to make it a stored template.

python:
def evaluate(book, context):
	# Return True ('yes') if the value in 'field' is used by more than 'test_count' books.
	# This template only works with single value fields such as Series, Publisher, and enumerations
	field = 'series'
	test_count = 1

	db = context.db.new_api
	id_map = context.globals.get('id_map')
	if id_map is None:
		context.globals['id_map'] = id_map = db.get_item_name_map(field)
		context.globals['item_book_count'] = db.get_usage_count_by_id(field)
	item_book_count = context.globals['item_book_count']

	item_id = id_map.get(book.get(field))
	if item_id is None or item_book_count.get(item_id, 0) <= test_count:
		return ''
	return 'yes'

[ownedbycats]

Originally Posted by chaley

There is no existing built-in way to get the cover size. It can be done in a python template but that requires opening the cover to compute its size, which could be too slow to use. What is "too slow" is up to you.

The template returns the cover size as "width by height". You can play with the formatting.

python:
def evaluate(book, context):
	db = context.db.new_api
	cover = db.cover(book.id, as_image=True)
	width = cover.width()
	height = cover.height()
	if width and height:
		return f'{str(width)} by {str(height)}'
	return '--'

Also attached is an Action Chain (instructions to install) will writes the template output to a #coversize column with less performance issues.

[Magic815]

Hi all - so I've been using the following metadata plugboard for a while to edit book titles on my Kindle for proper sorting:

{series}{series_index:0>2s| #| – }{title}

However, I recently sent the books from the Stormlight Archive to my Kindle, and realized the #2.5 and #3.5 books in that series don't sort in the ideal order.

What it currently does:

The Stormlight Archive #01 - Title
The Stormlight Archive #2.5 - Title
The Stormlight Archive #02 - Title
The Stormlight Archive #3.5 - Title
The Stormlight Archive #03 - Title
The Stormlight Archive #04 - Title
The Stormlight Archive #05 - Title

Is there a modification I can make to that plugboard that will instead add leading zeroes to the #.5 entries, so that it would do the following?

The Stormlight Archive #01 - Title
The Stormlight Archive #02 - Title
The Stormlight Archive #02.5 - Title
The Stormlight Archive #03 - Title
The Stormlight Archive #03.5 - Title
The Stormlight Archive #04 - Title
The Stormlight Archive #05 - Title

[theducks]

This is mine

{series_index:0>5.2f|| - }{title}

What is says is all index numbers will be xx.xx (5 long includes the decimal and 2 fractional)

[Magic815]

Originally Posted by theducks

This is mine

{series_index:0>5.2f|| - }{title}

What is says is all index numbers will be xx.xx (5 long includes the decimal and 2 fractional)

That is certainly an option! Although I'm not in love with all those extra leading and trailing zeros for 99% of my series that just do standard 1, 2, 3, etc.

I did end up giving the following a try:

program:no_decimal = template('{series}{series_index:0>2s| #| - }{title}');has_decimal = template('{series}{series_index:0>4.1f| #| - }{title}');contains(field('series_index'),'\.',has _decimal,no_decimal)

(Stolen from this post, with the addition of the "#" character.)

It gets me exactly what I was hoping for with leading zeroes for better title matching:

The Stormlight Archive #01 - Title
The Stormlight Archive #02 - Title
The Stormlight Archive #02.5 - Title
The Stormlight Archive #03 - Title
The Stormlight Archive #03.5 - Title
The Stormlight Archive #04 - Title
The Stormlight Archive #05 - Title

But the Kindle still sorts it like this:

The Stormlight Archive #01 - Title
The Stormlight Archive #02.5 - Title
The Stormlight Archive #02 - Title
The Stormlight Archive #03.5 - Title
The Stormlight Archive #03 - Title
The Stormlight Archive #04 - Title
The Stormlight Archive #05 - Title

As noted in that other post, I wonder if there is some overarching issue with how the Kindle device sorts that? If I had to choose between the above latest view I'm getting vs all my series being 01.00, 02.00, etc. - I think I can live with the 0X.5 entries being slightly out of place fo the very small handful of times they even exist.

But if anyone knows of a way to present the above titles as I've got them (without extraneous trailing zeros) - with proper sorting on Kindle - definitely let me know!

[chaley]

Originally Posted by Magic815

But the Kindle still sorts it like this:

As noted in that other post, I wonder if there is some overarching issue with how the Kindle device sorts that? If I had to choose between the above latest view I'm getting vs all my series being 01.00, 02.00, etc. - I think I can live with the 0X.5 entries being slightly out of place fo the very small handful of times they even exist.

It appears that the kindle is doing some kind of numeric sorting, but ignoring the decimal point and later digits. In other words, it is sorting whole numbers, not fractional numbers. This is implied by the example in your post and your example in post 1042 where the list is sorted by whole number, ignoring leading zeros.

But if anyone knows of a way to present the above titles as I've got them (without extraneous trailing zeros) - with proper sorting on Kindle - definitely let me know!

I don't have a kindle and can't test this, but it could be that if you put a decimal point after the whole numbered indices then they would sort correctly. By that I mean:

The Stormlight Archive #01. - Title
The Stormlight Archive #02. - Title
The Stormlight Archive #02.5 - Title
The Stormlight Archive #03. - Title
The Stormlight Archive #03.5 - Title
The Stormlight Archive #04. - Title
The Stormlight Archive #05. - Title

This template gives you the above:

program:
	if '\.' in $series_index then
		template('{series}{series_index:0>4.1f| #| - }{title}')
	else
		template('{series}{series_index:0>2d| #|. - }{title}')
	fi

Note the addition of the period in the suffix used for series indices that are whole numbers.

Your example cited above implies that this might work as well:

The Stormlight Archive #1. - Title
The Stormlight Archive #2. - Title
The Stormlight Archive #2.5 - Title
The Stormlight Archive #3. - Title
The Stormlight Archive #3.5 - Title
The Stormlight Archive #4. - Title
The Stormlight Archive #5. - Title

This template gives you that:

program:
	if '\.' in $series_index then
		template('{series}{series_index:.1f| #| - }{title}')
	else
		template('{series}{series_index:d| #|. - }{title}')
	fi

[Magic815]

So I tried this one:

program:
	if '\.' in $series_index then
		template('{series}{series_index:0>4.1f| #| - }{title}')
	else
		template('{series}{series_index:0>2d| #|. - }{title}')
	fi

But it looks like it still sorts like this on my Kindle:

The Stormlight Archive #01. - Title
The Stormlight Archive #02.5 - Title
The Stormlight Archive #02. - Title
The Stormlight Archive #03.5 - Title
The Stormlight Archive #03. - Title
The Stormlight Archive #04. - Title
The Stormlight Archive #05. - Title

Appreciate you giving it a shot! I think I can live with x.5 being slightly out of order for the couple series I have where there even exists books with a decimal place.

[chaley]

The attached exported stored template, comments_to_plain_text(), converts a comments field to plain text. This can be useful when whatever is processing the comments cannot handle HTML, for example the Generate Cover plugin. See the stored template's documenation for details.

[idiom6]

Metadata: Put series into the title, using either initials or a shortened form. Strip leading articles from the series name (any) (inspired by Gary_M_Mugford)

Could someone help me fix my plugboard? I've got the columns, I've got the plugboard recipe, I've got it set to Any Format/Any Device, but regardless of whether it's Send To Kindle, transfer over USB, or wirelessly Send to Device via Koreader, they all have the same result: just the title and author, per the Device Configuration.

[Reader4106]

(Translated from German using Google Translate)

I hope I'm in the right place with my question.

I have two custom columns in Calibre. Both are hierarchically structured.
The first column has the following labels:
Lookup name: #genre.
Column heading: Genre.
Normally, only one (comma-separated) value appears. However, there are a few cases with more than one entry.
The first/top level consists of a "sort character" such as _, §, °, ≡, etc., followed by several sublevels, which are separated by "." as usual.

The contents of the second column have the following labels:
Lookup name: #genre_rg.
Column heading: Genre (ReadingGoal).

This should now be created in a "flattened" form from the values ​​of the first column.
By "flattened," I mean the following:
- The sorting level should be filtered out.
- The second and third hierarchy levels should remain.
- The remaining levels should be ignored.
Here are some examples:
_.Belletristik.Roman.Spannung.Krimi.+nl → Belletristik.Roman
§.Sachbuch.Geschichte.Weltgeschichte.Menschheit → Sachbuch.Geschichte
#.Zeitschrift.Geschichte.Kultur.Menschliche → Zeitschrift.Geschichte
≡.Essayistisches.Kurzgeschichten.Reiseessays → Essayistisches.Kurzgeschichten
_.Belletristik.Roman.Cli-Fi, _.Belletristik.Roman.Dystopisch → Belletristik.Roman, Belletristik.Roman
§.Sachbuch.Gesundheit.Lebenshilfe.Beziehung.Sexual ität, Sachbuch.Wissen.Evolution.Mensch/Tier → Sachbuch.Gesundheit, Sachbuch.Wissen

[chaley]

Originally Posted by Reader4106

(Translated from German using Google Translate)

I hope I'm in the right place with my question.

I have two custom columns in Calibre. Both are hierarchically structured.
The first column has the following labels:
Lookup name: #genre.
Column heading: Genre.
Normally, only one (comma-separated) value appears. However, there are a few cases with more than one entry.
The first/top level consists of a "sort character" such as _, §, °, ≡, etc., followed by several sublevels, which are separated by "." as usual.

The contents of the second column have the following labels:
Lookup name: #genre_rg.
Column heading: Genre (ReadingGoal).

This should now be created in a "flattened" form from the values ​​of the first column.
By "flattened," I mean the following:
- The sorting level should be filtered out.
- The second and third hierarchy levels should remain.
- The remaining levels should be ignored.
Here are some examples:
_.Belletristik.Roman.Spannung.Krimi.+nl → Belletristik.Roman
§.Sachbuch.Geschichte.Weltgeschichte.Menschheit → Sachbuch.Geschichte
#.Zeitschrift.Geschichte.Kultur.Menschliche → Zeitschrift.Geschichte
≡.Essayistisches.Kurzgeschichten.Reiseessays → Essayistisches.Kurzgeschichten
_.Belletristik.Roman.Cli-Fi, _.Belletristik.Roman.Dystopisch → Belletristik.Roman, Belletristik.Roman
§.Sachbuch.Gesundheit.Lebenshilfe.Beziehung.Sexual ität, Sachbuch.Wissen.Evolution.Mensch/Tier → Sachbuch.Gesundheit, Sachbuch.Wissen

What are you actually asking for? If the custom column #genre_rg is a "Column like tags" then you fill it in yourself, perhaps using the Action Chains plugin "Single Field Edit" to calculate the value using a template.

If #genre_rg is a "column built from other columns then you fill it in using "subitems()" function in a template to select the second and third values from a hierarchy.