MobileRead Forums - View Single Post - How to edit the entries in the details view?

DaltonST · 06-25-2016, 12:22 AM

Kovid,

The root cause of this brouhaha is that the Calibre Custom Columns functionality does not support a datatype of "non-normalized simple text".

Putting textual data into a normalized textual field makes sense for data such as Author or Tags or Series that are shared among many books simultaneously. That is what normalization is meant to do.

Putting textual data into a normalized textual field does not make sense for textual data that is unique to every book. That would be akin to making a datetime field normalized. Or a float field. Or making ISBN a standard tag-like column instead of an Identifier.

Datatype=comments is the closest thing to a datatype of "non-normalized simple text", since datatype=comments is non-normalized and textual.

Comments may be html, but certainly do not have to be html. Comments may be simple text. Indeed, 'Edit Metadata' for a single book offers a "clear formatting" option to convert the html to simple text.

Since @excaliber and the rest of the Zotero-Calibre user community will not be getting labels for comments in the detail view for their 27+ datatype=comments custom columns that are not html (and would be corrupt if they were), and since Calibre apparently will not be getting a datatype of "non-normalized simple text", then they will have to live with 27+ datatype=composite custom columns, each with a template that points to the appropriate member of the 27+ datatype=comments custom columns. They can hide the datatype=comments custom columns from the details view in Preferences, and show the datatype=composite custom columns instead (with labels). Ugly, and Calibre will load more slowly, but better than nothing.

Thanks for at least considering @excaliber's request.

DaltonST

Special Note to @excaliber and the rest of the Zotero-Calibre user community:

Don't worry, I will automate the creation of the 27+ datatype=composite custom columns via calibredb. I will also look at automating the updating of Preferences > Look & Feel > Book Details to hide or show the appropriate custom columns. However, you should install the View Manager plug-in to control which custom columns you see in the Library View of the GUI. You do not want to see the datatype=composite custom columns in the Library View, only in the book details.

06-25-2016, 12:22 AM	#8
DaltonST Deviser Posts: 2,265 Karma: 2090983 Join Date: Aug 2013 Location: Texas Device: none	Custom Column Datatype of "non-normalized simple text" Kovid, The root cause of this brouhaha is that the Calibre Custom Columns functionality does not support a datatype of "non-normalized simple text". Putting textual data into a normalized textual field makes sense for data such as Author or Tags or Series that are shared among many books simultaneously. That is what normalization is meant to do. Putting textual data into a normalized textual field does not make sense for textual data that is unique to every book. That would be akin to making a datetime field normalized. Or a float field. Or making ISBN a standard tag-like column instead of an Identifier. Datatype=comments is the closest thing to a datatype of "non-normalized simple text", since datatype=comments is non-normalized and textual. Comments may be html, but certainly do not have to be html. Comments may be simple text. Indeed, 'Edit Metadata' for a single book offers a "clear formatting" option to convert the html to simple text. Since @excaliber and the rest of the Zotero-Calibre user community will not be getting labels for comments in the detail view for their 27+ datatype=comments custom columns that are not html (and would be corrupt if they were), and since Calibre apparently will not be getting a datatype of "non-normalized simple text", then they will have to live with 27+ datatype=composite custom columns, each with a template that points to the appropriate member of the 27+ datatype=comments custom columns. They can hide the datatype=comments custom columns from the details view in Preferences, and show the datatype=composite custom columns instead (with labels). Ugly, and Calibre will load more slowly, but better than nothing. Thanks for at least considering @excaliber's request. DaltonST Special Note to @excaliber and the rest of the Zotero-Calibre user community: Don't worry, I will automate the creation of the 27+ datatype=composite custom columns via calibredb. I will also look at automating the updating of Preferences > Look & Feel > Book Details to hide or show the appropriate custom columns. However, you should install the View Manager plug-in to control which custom columns you see in the Library View of the GUI. You do not want to see the datatype=composite custom columns in the Library View, only in the book details.