Displaying ISBN column in the main GUI

[tilleydog]

I know that the ISBN field is standard in the sqllite database but for some reason I can't get it to display in the Main GUI with the other standard columns. I tried to add it as a custom field but it adds it as a totally new blank column even thought the icon for the ISBN column shows up. Is there any way to add the ISBN field to the main GUI.

[kovidgoyal]

No, there isn't.

[Lady Fitzgerald]

A workaround might be to make a custom column for the ISBN then copy and paste it from the ISBN field of the first page of the edit menu into the custom column field. Granted, it would be tedious.

[Starson17]

Originally Posted by Lady Fitzgerald

A workaround might be to make a custom column for the ISBN then copy and paste it from the ISBN field of the first page of the edit menu into the custom column field. Granted, it would be tedious.

I suspect you could use SQLiteSpy to do this with SQL commands in the metadata.db file.

[kovidgoyal]

the question is why do you want the isbn ina a column. Its pointless sorting it and looking at isbn numbers doesn't give you any useful information either.

[tilleydog]

The main reason is that you can edit at the Main Gui page instead of opening each book entry up to add the ISBN. Currently I have a couple of thousand PDF files imported for which I have the ISBN numbers in an excel spreadsheet. I can sort the files in Calibre by their series type and would be able to add the isbn much quicker than opening each record. Its still time consuming but it goes faster than opening each record. I tried to update the metadata.db using sql queries but calibre wouldn't read it afterwords. It was a good thing I made a copy before starting.

[Lady Fitzgerald]

Originally Posted by tilleydog

The main reason is that you can edit at the Main Gui page instead of opening each book entry up to add the ISBN. Currently I have a couple of thousand PDF files imported for which I have the ISBN numbers in an excel spreadsheet. I can sort the files in Calibre by their series type and would be able to add the isbn much quicker than opening each record. Its still time consuming but it goes faster than opening each record. I tried to update the metadata.db using sql queries but calibre wouldn't read it afterwords. It was a good thing I made a copy before starting.

Let me guess; you scanned all your books to PDF. I'm doing the same thing and I'm having to put my ISBN in manually as I put each book into Calibre. Since I'm in the process of scanning my books and put each one into calibre as I complete the scanning process, it doesn't seem like such a chore since, after downloading the metadata, I usually have to do a few tweaks while I'm in the edit window anyway.

[kovidgoyal]

yeah that sucks, however, adding a column for this sort of one time use is too much work, in my opinion.

[theducks]

Originally Posted by tilleydog

The main reason is that you can edit at the Main Gui page instead of opening each book entry up to add the ISBN. Currently I have a couple of thousand PDF files imported for which I have the ISBN numbers in an excel spreadsheet. I can sort the files in Calibre by their series type and would be able to add the isbn much quicker than opening each record. Its still time consuming but it goes faster than opening each record. I tried to update the metadata.db using sql queries but calibre wouldn't read it afterwords. It was a good thing I made a copy before starting.

When I perform big, bulk add's, I then select the "new" group in the the GUI,
Right click the grouping and select "Edit Meta-Data Individually"
That presents the Edit window for each book in the list, sequentially.
Fill in the datas and click OK

The next title appears.. Repeat until done

[Lady Fitzgerald]

Originally Posted by kovidgoyal

yeah that sucks, however, adding a column for this sort of one time use is too much work, in my opinion.

In my case, I don't need a column displaying the ISBN. Considering all calibre can do, I don't mind copying and pasting the ISBN into the metadata window since I have to edit the downloaded metadata anyway (whoever compiles it at ISBNdb seems to have a sporadic aversion to uppercase letters, sorta like a certain developer I know of ).

[tilleydog]

I got it to work using the sql lite solution. I dumped my books table to CSV. Sorted it appropriately then cut and pasted from the other spreadsheet. Then deleted my old books table, imported the new one, (making sure to make the fields were properly defined) and started up calibre.

Saved my self a couple of hours possibly days.

[Starson17]

Originally Posted by tilleydog

I got it to work using the sql lite solution. I dumped my books table to CSV. Sorted it appropriately then cut and pasted from the other spreadsheet. Then deleted my old books table, imported the new one, (making sure to make the fields were properly defined) and started up calibre.

Saved my self a couple of hours possibly days.

Great. Did the triggers cause you any trouble?

[tilleydog]

I'm not sure.

Everything seemed to work. But I ran into problem later on when trying to add new books to the database. IT would fail to add the book but upon restarting calibre, would say the database was corrupted and prompt me to create a new one. I then went into sqllite browser and go to the last record which would be a partial entry of the new book. Removed that and everything would start up again but can still not add new books to database.

[itimpi]

Sounds like there must be some other non-obvious problem with the database?

A solution that might work is to first tell Calibre to create a new empty library at a new location, and then use the Calibre facility to copy books to this library from the existing library. As long as this is all done using Calibre itself, hopefully the new library will be self-consistent.

[Starson17]

Originally Posted by itimpi

Sounds like there must be some other non-obvious problem with the database?

It seems likely. It's very tricky to directly access Calibre's database using SQL tools. There are multiple triggers that actuate when Calibre accesses some fields. They function to keep the whole Calibre structure (internally to the db and and externally in the folders) consistent when fields are changed. For certain types of changes, you have to know what Calibre does, disable triggers, do it all manually and then reenable. Using Calibre's own tools is much easier, but then you have to learn those tools and enough Python to run them.