Although you always wanted to be an artist, you ended up being an expert on databases because you love to cook data and you somehow confused database with data baste. Your old love is still there, however, so you set up a database company, ArtBase, that builds a product for art galleries. The core of this product is a database with a schema that captures all the information that galleries need to maintain.

ArtBase is designed to support a single art gallery. A specific gallery will generally keep information about ARTISTS, including their names (which are unique), birthplaces, and age. Galleries often keep track of artists of interest, even if the gallery doesn’t own any artwork from that artist.

A gallery will also keep track of the ART that it sells, which usually includes the artwork’s name, the artist who created it, the year it was made, its type of art (e.g., painting, lithograph, sculpture, photograph), and its price must be stored.

Pieces of artwork are also classified into GROUPS of various kinds, for example, portraits, still lifes, works by Picasso, or works of the 19th century; a given piece may belong to one or more group or none at all. Each group is identified by a name (like those just given) that describes the group.

Finally, galleries keep information about CUSTOMERS. For each customer, galleries keep that person’s unique name, address, total amount of dollars spent in the gallery (very important!), type of customer (big spender or not), and the artwork purchased, as well as the groups of art that the customer tends to like. Just as with artists, galleries like to keep track of serious art buyers even if they have never purchased anything from the gallery.

Draw the ER diagram for the ArtBase database, using the information presented. Make sure to state any assumptions that you have in order to validate your diagram, but do not violate any given facts.