Discussion: Duplicate books

##Plan (Evolving, Based on discussion)

• Modify existing code that ignores duplicate books when adding to say "A book with this ISBN or title/author is already recorded. Dou you want to add a duplicate?"
• If the answer is 'yes', then present the 'Add' screen.
• The user could use the "Notes" area to record distinctive features of the book ("torn cover", "blood stains" etc)
• When showing book details, have a read only field showing # of copies IF there are more than 1. Otherwise don't even show the field.
• modify Import code (see below)

##Export/Import

Export is fine; it will export and ID for each which means more than one record will be imported/updated.

Import is fine for records with IDs. Records without IDs are more problematic.

Import looks for ISBN (or title/author if ISBN blank). If it finds a book, it updates. The new logic should be:

• If there is an ID, just update
• If no ID, .... thinking .... maybe add if no record *exactly* matches?

#Discussion

Grunthos

I have several books with more than one copy, but the same ISBN. There seem to be two solutions to this:

• the 'inventory management' solution -- have a '# of copies' field
• the 'library' solution -- list them both in the library catalogue

The former is probably easier, but the 'library' solution is probably better becuase it allows tracking of distinct books (eg. lending both out to different people). So I am leaning towards the latter.

My thinking is:

• display a warning before adding a duplicate book.
• add it as a new book if the user chooses.

...and problem solved...I think.

Can anyone see a problem with this technically (eg. is uniqueness of ISBNs assumed in the app -- I dont think so) or from a user perspective?

eleybourn

There should be no technical issue. The database can handle books with identical authors and titles. However we would need to be able to show the user the difference between books. So on the list or edit page it would say "copy #1" or "copy #2". Keep it small and discrete.

It should also be unchangable, based on the order in which it was entered into the database.

Grunthos

Not sure about 'unchangeable' eg. each need to be able to be loaned, have different comments. Maybe have different description. I also have two books with same ISBM but differnt covers...so thumbs should also be editable. I do agree it's a bit tricky tho...

Minor aside: any idea why Issue 169 & 170 never appear in my list of open issues?

eleybourn

Sorry, I meant the copy number should be unchangable. If they are stored as separate books in the database you should be able to manage/edit each of them completely independently. And I have no idea why you wouldn't be able to see issue 169/170 in your list.

Grunthos

Not sure about this; if it is fixed, and they lose book '1', having copy '2' will be confusing. I think I'd vote for a combination of using Notes and having the system show '2 copies available'...or something like that.