Can't finish my ER diagram I am trying to create a database for a small book library. This is not a professional project, just an exercise of my own. This is my first time to try this ( I am self-taught ) and I am encountering a problem. Before I continue I will provide my version of the ER diagram below ( I made it in Paint, using the following resource for notation ):



My biggest problem is to solve the fact that book can have the same title but have several editions or be a part of a set. An example would be Lord of the Rings trilogy, or Programming Windows, 5th edition, or Encyclopaedia of chess openings, volume D. 

I don't know how to incorporate this into my ER diagram so that I can avoid data redundancy.

Therefore I ask these questions:


How should I address the fact that book can have the same title but have several editions or be a part of a set, in my ER diagram?
Since I am inexperienced, can you point out mistakes in my ER diagram, if there are any, and suggest an improvement?


Since this is my very first post here, please leave a comment if anything needs to be changed ( if it doesn't fit this site's question format ) or if you need further info.

Thank you.
I would say that an Edition is an entity that is related to a Book.  

You then have a one-to-many relationship between Books and Editions.  (One book can have many editions.)  and a many-to-one relationship between Editions and Publishers  (many editions are published by one publisher).  

When I was building actual databases, back in the day, I always had access to one or more "subject matter experts",  people who had become familiar with the data through constant use.  Most subject matter experts were neither computer experts nor database experts.  Your situation is somewhat different.  

I would try to find some kind of on line subject matter expert, like the Library of Congress.  They might have some kind of model of the publishing industry that would provide answers to this and other questions you have regarding how the field of publishing really works.  And this model might be in the public domain.

PS:  Congratulations on using the ER model as an analysis tool,  and not diving into database design prematurely.