(100 pts) An art gallery would like to store information about artworks, exhibitions, artists, and customers. Since you are taking a database class, you are asked to assist the museum to design a database based on the following specifications.
The gallery keeps track of artists information: a unique identifier, first name, middle initial, last name, birthplace, date born (if known), date died (if not living), country of origin, and main art style.
A piece of artwork can be created by a collaboration of a group of artists. An artist can create more than one artwork. To be called an artist, one, of course, has to create at least one artwork.
The gallery keeps information of artworks. Each piece of artwork has a unique identifier, a year (when it was created, if known), a title, a description, a size (height x wide by inches) and a listed price.
Pieces of artwork are also classified into three categories: painting, sculpture, and statue. Paintings have a paint type (oil, watercolor, etc.), materials on which it is painted on (paper, canvas, wood, etc.) and style (portraits, still life, abstract, etc.); a given piece may belong to more than one category. A sculpture or a status has a material from which it was created (wood, stone, etc.), weight, and style.
For every exhibition, the gallery keeps track its name, theme, started date and end date. Each exhibition displays 10 to 30 pieces of artwork.
Finally, galleries keep information about customers. For each customer, the gallery keeps that persons unique identifier, first name, middle name, last name, address, total amount of money spent in the gallery (very important!).
Each customers preference of the categories of arts and artists must be recorded as well. Each customer can like more than one category of arts. Also, each customer may favor several artists, and each artist may have several customers like their work.
Specifically, your tasks are:
1) Draw an ER-diagram for the database by identifying the entity sets, relationship sets and their multiplicity, and the primary key for each entity set (and weak entity set, if any) and each relationship set.
2) Indicate (what and why) feature(s)/property(ies) (if any) in the above description that are NOT captured by your ER-diagram.