Create an entity relationship diagram (ERD) for the owners of a store names Jewel Palace. Jewel Palace sells and buys all kinds of an(paintings, jewelry, clothing, etc). An ItemNumber uniquely identifies each item, but no two items are alike in the store, so this is not a standard inventory application.

In a standard inventory application, the database designer assumes that there will be more than one of a given item in inventory and keeps track of the quantity on hand of that item; in this application, the designer must assume that each ItemNumber represents a unique item and that the quantity on hand will be:

The owners of Jewel Palace decide what composes an item. For example, the owners may decide that a single spoon is an item or they might decide that an entire silver place setting is an item. This decision is made when the item is purchased and made available for sale in the store. This decision does not change once it has been made.

Each item is also characterized by a Description, AskingPrice, InitialCondition, and open-ended Comments about the item.

The owners of Jewel Palace work with many different individuals, called Clients, who sell items to and buy items from the store. Some clients only sell items to Jewel Palace, some only buy items from Jewel Palace and some both sell and buy.

A client is identified by a ClientID and is also described by a ClientName and PhoneNumber. The owners aren't planning on keeping track of whether a client is a buyer or a seller in the actual Client data.

When Jewel Palace sells an item in stock to a client, the owners want to record information about the sale such as the actual selling price, sales tax, date sold, and commission paid.

When Jewel Palace buys an item from a client, the owners want to record the purchase cost, date purchased, and condition at the time of purchase.