View Single Post
Old 12-24-2015, 11:28 AM   #36
DaltonST
Deviser
DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.
 
DaltonST's Avatar
 
Posts: 2,265
Karma: 2090983
Join Date: Aug 2013
Location: Texas
Device: none
Composite Custom Columns in CALM

Quote:
Originally Posted by Terisa de morgan View Post
When I change to CALM library or I refresh the library view, I get the following message:

Attachment 144872

And these are the details:

Spoiler:

File "site-packages\calibre\gui2\library\models.py", line 536, in current_changed
File "site-packages\calibre\gui2\library\models.py", line 519, in get_book_display_info
File "site-packages\calibre\db\legacy.py", line 583, in get_metadata
File "site-packages\calibre\db\cache.py", line 611, in get_metadata
File "site-packages\calibre\db\cache.py", line 311, in _get_metadata
File "site-packages\calibre\db\cache.py", line 425, in composite_for
File "site-packages\calibre\db\fields.py", line 273, in _render_composite_with_cache
File "site-packages\calibre\db\fields.py", line 259, in __render_composite
KeyError: u'composite_template'


So, calibre doesn't change properly to the library.

I'm merging two libraries, and I have one selected custom column and each of them, which is text with fixed values.

You need to read this recent post: Composite Custom Columns in CALM Version 2.0.5.

Quote:
@rolandt99:

Version 2.0.5 Answer to your Questions #1 and #2:

You are probably getting Template Errors when you switch to the CALM Target Library that you just Generated. I assume that is what you mean by "generation fails". Composite Custom Columns are problematic because of their Templates. Working on that issue for the next release of CALM is on my to-do list.

2 Possible Immediate Work-Around Solutions to choose from:

[Choice #1] There is a pushbutton on the "Source Custom Columns" tab named "Mass Deactive All Composite Custom Columns (Only)". You need to click that prior to Generating. Then, manually create the desired Composite Custom Columns directly in the CALM Target Library. Since they are "columns built from other columns", their underlying real data will already be there.

[Choice #2] Manually change the templates for all of the Generated Composite Custom Columns directly in the CALM Target Library. I suggest you do this AFTER Generation BUT BEFORE Consolidation. You will get few-to-no error messages about Template Errors, since there will be no "books" in the CALM Target Library to cause them. Then, run a Consolidation.
DaltonST
DaltonST is offline   Reply With Quote