Rescans in already present books.

Nova5 · 01-07-2014, 09:46 PM

I have a collection of books on my server, I corrected some books which were scanned from my network location into the local PC's library. Then added found some that were stored in the wrong spot on my server, moved those into the correct spot and scanned the folder again. Calibre imported the already fixed books again as the uncorrected version. How do I prevent this from happening? the uncorrected versions metadata was useless to the extreme.

eschwartz · 01-07-2014, 10:46 PM

Did they have a metadata.opf, and were they added via the second Add Books option? (perhaps they came from an old library.) If so, you have told calibre not to read metadata from the book, but from the metadata file.

Personally, if you are fixing the metadata I would think the easiest way is to import into calibre and update through there.

theducks · 01-07-2014, 10:47 PM

Quote:

Originally Posted by Nova5

I have a collection of books on my server, I corrected some books which were scanned from my network location into the local PC's library. Then added found some that were stored in the wrong spot on my server, moved those into the correct spot and scanned the folder again. Calibre imported the already fixed books again as the uncorrected version. How do I prevent this from happening? the uncorrected versions metadata was useless to the extreme.

If you tell Calibre to Import again, it will.

There is a settings Preferences: Adding Books: Automerge and you set the disposition when duplicates are detected

Nova5 · 01-08-2014, 01:57 PM

metadata.opf would be seemingly pointless as it doesn't get created in the source directory only the destination directory. Many of these are .txt format, those that I hadn't yet corrected/created metadata for weren't reimported as the were seen as dupes. but the correct ones were reimported. I probably should set the destination to be the same as the source that way it can't have this problem and will add the metadata files/tags to the original files.

my music/video management software leaves the files in the original location and just adds the location to a sql database. I can have it MOVE my files to follow a structure I build. Calibre should do the same database wise for where the files are, not neccesarily be able to follow my structure I have for movies/music.

MediaMonkey..

eschwartz · 01-08-2014, 02:40 PM

All I'm saying is, if the file had updated metadata, but calibre didn't read it, the only reason I can think of is if it was overridden by a metadata.opf -- for instance, you had previously saved this folder from calibre.

Nova5 · 01-09-2014, 09:29 PM

most being .TXT don't support metadata in any form. the format just was never designed to accommodate it, and the source directory did not have metadata.opf's for the books for Calibre to scan in when it imported them. perhaps other formats are less susceptible to this problem. I'm converting them to epub's on upload to the reader (Nook ST Glow),

01-07-2014, 09:46 PM	#1
Nova5 Enthusiast Posts: 38 Karma: 10 Join Date: Mar 2009 Device: Sony PRS-505	Rescans in already present books. I have a collection of books on my server, I corrected some books which were scanned from my network location into the local PC's library. Then added found some that were stored in the wrong spot on my server, moved those into the correct spot and scanned the folder again. Calibre imported the already fixed books again as the uncorrected version. How do I prevent this from happening? the uncorrected versions metadata was useless to the extreme.

01-08-2014, 01:57 PM	#4
Nova5 Enthusiast Posts: 38 Karma: 10 Join Date: Mar 2009 Device: Sony PRS-505	metadata.opf would be seemingly pointless as it doesn't get created in the source directory only the destination directory. Many of these are .txt format, those that I hadn't yet corrected/created metadata for weren't reimported as the were seen as dupes. but the correct ones were reimported. I probably should set the destination to be the same as the source that way it can't have this problem and will add the metadata files/tags to the original files. my music/video management software leaves the files in the original location and just adds the location to a sql database. I can have it MOVE my files to follow a structure I build. Calibre should do the same database wise for where the files are, not neccesarily be able to follow my structure I have for movies/music. MediaMonkey.. Last edited by Nova5; 01-08-2014 at 02:00 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Should I present myself here?	poleodementa	Introduce Yourself	7	10-04-2012 03:06 AM
ee only works when ac is present	thorne	enTourage Archive	4	01-10-2011 09:46 AM
Best Present?	pdurrant	Lounge	40	12-29-2010 08:25 AM
Images in Books- Not Present???	dashto	Kobo Reader	5	11-23-2010 07:11 PM
A self imposed present	medfield	Which one should I buy?	4	07-02-2009 05:55 AM

01-07-2014, 10:46 PM	#2
eschwartz Ex-Helpdesk Junkie Posts: 19,421 Karma: 85400180 Join Date: Nov 2012 Location: The Beaten Path, USA, Roundworld, This Side of Infinity Device: Kindle Touch fw5.3.7 (Wifi only)	Did they have a metadata.opf, and were they added via the second Add Books option? (perhaps they came from an old library.) If so, you have told calibre not to read metadata from the book, but from the metadata file. Personally, if you are fixing the metadata I would think the easiest way is to import into calibre and update through there.

01-08-2014, 02:40 PM	#5
eschwartz Ex-Helpdesk Junkie Posts: 19,421 Karma: 85400180 Join Date: Nov 2012 Location: The Beaten Path, USA, Roundworld, This Side of Infinity Device: Kindle Touch fw5.3.7 (Wifi only)	All I'm saying is, if the file had updated metadata, but calibre didn't read it, the only reason I can think of is if it was overridden by a metadata.opf -- for instance, you had previously saved this folder from calibre.

01-09-2014, 09:29 PM	#6
Nova5 Enthusiast Posts: 38 Karma: 10 Join Date: Mar 2009 Device: Sony PRS-505	most being .TXT don't support metadata in any form. the format just was never designed to accommodate it, and the source directory did not have metadata.opf's for the books for Calibre to scan in when it imported them. perhaps other formats are less susceptible to this problem. I'm converting them to epub's on upload to the reader (Nook ST Glow),

Advert

Advert