Oddity

[Gunnerp245]

Inserted an empty book added the Author and Title. With the ISBN, downloaded metadata and cover. Also have a custom column entitled "Comments". In 'comments' entered 'Get Book' as a reminder.

Problem:
With data in the custom column the metadata does not show in the "Book Details" panel. Removing data from the custom column and the metadata is displayed.

[kovidgoyal]

the book details panel is completely blank? What version of calibre is this?

[Gunnerp245]

Originally Posted by kovidgoyal

the book details panel is completely blank? What version of calibre is this?

Vista Home Premium SP2
calibre 0.7.28

Custom column:
Lookup name - comments
Column heading - Comments
Column type - Text, column shown in the tag browser

Calibre_Oddity_Before.jpg - No comment; metadata visible
Calibre_Oddity_After.jpg - Comment - Get Book!; metadata not visible

Only change was to put data in the comments column. Removing the data allows the metadata to be displayed again. It does the same whether an empty book or not.

EDIT: The missing metadata is the summary of the book, which when inspecting the metadata through Edit Metadata; Edit Metadata Individually;
is contained in an area titled Comments. Hmmm...

Custom column:
Lookup name - rem
Column heading - Remarks
Column type - Text, column shown in the tag browser

Calibre_Oddity_FoundIt.jpg - Remarks - Get Book!; metadata visible

FOUND IT: I just added a custom column titled 'Remarks'. Entering data in remarks does 'not' make the metadata disappear. The 'Comments' must be a pseudo reserved keyword...

[itimpi]

Comments is a standard field in a books metadata. Sounds as if somehow you got a custom column with the same name is a built-in one. I would not have thought that should have been allowed?

[Gunnerp245]

Originally Posted by itimpi

Comments is a standard field in a books metadata. Sounds as if somehow you got a custom column with the same name is a built-in one. I would not have thought that should have been allowed?

My thoughts as well.

[kovidgoyal]

Well, if you create a custom column named comments, calibre assumes you want it to override the builtin comments for display. Otherwise, why name it the same as the builtin column?

[Gunnerp245]

Originally Posted by kovidgoyal

Well, if you create a custom column named comments, calibre assumes you want it to override the builtin comments for display. Otherwise, why name it the same as the builtin column?

Until I responded earlier, I had no idea 'Comments' already existed. Otherwise I would not have done it...

Would seem to make sense that 'built-in' commands should be reserved aka protected against user over ride...

[kovidgoyal]

The "override" is only for the display area. User defined column names are always prefixed by #, so they cannot override a built-in column name in any other context.

[Lady Fitzgerald]

Originally Posted by kovidgoyal

The "override" is only for the display area. User defined column names are always prefixed by #, so they cannot override a built-in column name in any other context.

Curious. When I tried to name a custom column "Series" (I wanted a series column that didn't number the series), calibre slapped me on the wrist and said, "No, no, no!" How humiliating! (All seriousness aside, I got around it by naming the column " Series" with a space in front of the word; it displays close enough to the original to pass for it).