Field for Cover Price and Purchase Price

It would be great to add fields for the cover price and purchase price. This would be most useful for insurance purposes. I realize that this is not an exact science, but having this field for my library would be an additional value. Should I ever need to place an insurance claim on my library, the information I already have in LibraryThing would be invaluable to the insurance company. If I were able to provide them with the actual cover price and purchase price that would go additionally in my favor in making a claim. I've checked through all the suggestions and features that are being proposed and cannot find this listed anywhere.

Thanks,
Andy

It's been suggested quite a few times.

The best way to do this with current fields is comments or private comments.

PS Here are some links to earlier discussions, where you might find other suggestions, as well as the debates about how/whether a specific field could work:
http://www.librarything.com/topic/90182
http://www.librarything.com/topic/80195
http://www.librarything.com/topic/53045
http://www.librarything.com/topic/72986
http://www.librarything.com/topic/42094
http://www.librarything.com/topic/26222
http://www.librarything.com/topic/2135

Good proposal. I think I do remember someone mentioning a price field at one time, however, I'm rarely able to locate old information on LT that's outside my library. In this case I don't even recall in what group the topic was mentioned. :/

2. >>The best way to do this with current fields is comments or private comments.

And not very good at that. I am slowly adding other relevant and important to me information in the comments field. Private comments are less frequent but just as important. I don't particularly wish to mix price data with the other comments in either field.

1.>> What I do currently is to export my Library data to an excel spreadsheet (CSV format works nicely) and then add the price data... the only bad thing is I have no external site on which to store the price data as would be the case if there were price fields in my LT catalog. This is cumbersome and a bit labor intensive with a large library... and segregating the books I own from those I've borrowed or once owned and have given away... well, that's not so easy either. But, for my purposes it's better than integrating price data with the other comments.

@4: the only bad thing is I have no external site on which to store the price data as would be the case if there were price fields in my LT catalog.

It would be another layer of cobbling solutions together, but you could upload your spreadsheet to Google Documents, which would be off-site storage.

True, but then I'd have to upload every corrected spreadsheet. I buy books rather frequently, so my spreadsheet changes frequently. :/ That might not be so bad if I could just export by collection instead of having to export the entire list from LT each time, so the changes would be fewer and more easily integrated into the master spreadsheet...

Yes. that is currently the way I do it today. However very difficult export as others have mentioned to put it into a.CSV file would be the ideal way to solve the problem. That way to separate field in a spreadsheet or database and I could work that way keep track of it formal sort of operations against that field loan sum it up for insurance purposes.

Andy

I too would like to see a purchase price column. Many of the books I buy are used. The insurance aspect is something I hadn't thought of and when you have as many books as we do I'm sure that is a good chunk of change.

Any progress on adding a purchase price and cover price fields to the catalog?

http://www.librarything.com/topic/53045#959628

Read this response from the Founder of Librarything.

Basically, your best bet is comments or private comments.