A database used for storage of information to be accessed at a later date for a specific use such as in this case, an Art Museum, must utilize many views for user. These views should include what a visitor of the guest would want to see, an employee of the art museum, or an administrator or contributor to the museum. You must also analyze the need of each person.
For example, a guest may want to see information on whose pieces are on display and the employees may want to know where in the museum those items are located for security reasons. The database asked for must contain the ability to track all the artworks, the artists who created them, and places within the museum where these works of art displayed within the museum. Also if requested a more specific database accessible to the inner workers of the museum, such and for the artist themselves or the person who contributed to the museum.
Some of the problems and constraints we would run into would be the duration of some of the information, for example some of the art would be a loan and would not remain in the museum for a long period of time, so that information in the database loud need to be changed or limited. Also you would need to limit access to some of the portions in the database as you would not want visitors to be able to access portions meant for security employees of the museum. Same would go for the schedules of the pieces to be leaving and coming to the museum, or private information about the employees, etc.
When developing the database the formula should be the question or input, such as the artist's name, then the variable, such as the item location. Then the result is your yield of desired result. This simplifies the process in the case that multiple pieces room the same artist or time period may be on display. With an art museum such as The Dayton Art Institute with over 5,000 years of art on display, the complexity of the database can be overwhelming, not to mention the special events they host. ( The Dayton Art Institute. 014) We need to take into account what kind of database is used-relational, object oriented, hierarchical, or another type. - Also take into account DB'S specific language or how it will implement the database. The conceptual design stage for this database allows us to focus solely on the problem of structuring information, without roaring at the same time to resolve technology issues. In this database we need to capture the information needed for the specific Art Museum, for example the Dayton Art Institute.
This information must include the artist's name, the name of the work of art, the exhibition its included in, and the in room where this work of art is inside the museum. This is where specific sectors of the database could be included for specific users for example for the users visiting the museum or the employees in charge of maintaining records of whom the work belongs there could be a sub section stating if it's a borrowed work of art from another museum, where its future position is in another museum, or if it is on permanent display.
To develop this database, we will use a program like Microsoft Access. According to "Access 2010"(2014), "Access is a database tool for gathering all your information and Understanding your phone numbers, inventory, guest lists, whatever you're tracking and providing a convenient way to enter, navigate, and report out your data. " (p. I). A good database design ensures easy maintenance. Data is stored in tables and each able contains data about a subject, such as customers.
Therefore, when upgrading a portion of the data, such as an address, it is in one place, but that change automatically appears throughout the database. A well-designed database usually contains different types of queries that show the necessary information. A query can display a subset of data, like all works of art from a specific region, artist, or era, or combinations of data from different tables, such as artist information combined with location information in the museum. An attribute is another word for category. In a spreadsheet it would be a cell.
It is a place in a database table to store one piece of data of a given type. For example an attribute designated to hold a last name, could hold "Smith", but should not hold "Amy Smith. ("Database Fundamentals", 2012) An entity is something that someone wants to track, an employee, for example. It is basically the subject for a table. You gather data about the employee, you run queries to find out information about them, track their time, vacation, sick days etc... Therefore, an entity is very much the same as a record in a table. ("Database Fundamentals", 2012).