Design Simple Database Data Model

Art Museum Data Model: An art museum owns a large volume or works of art. Each work of art is described by an item code (identifier), title, type, and size; size is further composed of height, width, and weight. A work of art is developed by an artist, but the artist for some works is unknown. An artist is described by an artist ID (identifier), name, date of birth, and date of death (which is null for still living artists). Only data about artists for works currently owned by the museum arc kept in the database. At any point in time, a work of art is either on display at the museum, held in storage, away from the museum as part of a traveling show, or on loan to another gallery. If on display at the museum, a work of art is also described by its location within the museum. A traveling show is described by a show ID (identifier), city in which the show is currently appearing, and the start and end dates of the show. Many of the museum works may be part of a given show, and only active shows with at least one museum work of art need be represented in the database. Finally, another gallery is described by a gallery ID (identifier), name, and city. The museum wants to retain a complete history of loaning a work of art to other galleries, and each time a work is loaned, the museum wants to know the date the work was loaned and the date it was returned. Part 2 - Art Museum Model: After you complete the data model, map the data model to a set of relational tables using the mapping rules discussed in class. For primary keys use the (PK) identifier and put (FK) at the end of attributes that are foreign keys in the relation. For attributes that are both, use (PK, FK). Be sure to indicate referential integrity constraints. Use the following form for the relational tables: Relational_Table_Name (Att_1_Name, Att_2_Name, …. Att_n_Name), This is a quick and easy project.