Hello, I am a student and I was assigned to create my first entity relationship diagram and I'm kind of lost. The professor hints the paintings should be broken into a generalization hierarchy since they have so many attributes but I can only break them into two sub(entities) based on my understanding of G.H.(using the "is a" rule)

Anyway I'm struggling with that and finding the weak entity(professor also hinted that there is a week entity)

I attached what I have so far as ERD1.pdf (didn't establish relationship type/participation constraints yet)

Am I even on the right track/have the right idea?

The prompt is below:

The BestArt museum, which owns several millions artifacts, has asked you to do the conceptual design of a database for the following information requirements.

The only artifacts of the museum in its database will be paintings. Each painting is uniquely identified by an artifact number. Data about each painting include a name, year completed, year acquired by the museum, estimated value, and a “school” (e.g. Cubism). Each painting was created by one painter, although the painters of some paintings are unknown. Due to shortage of exhibit rooms, the least valuable paintings are kept for long period of time in storage rooms, whereas the most valuable ones are shown in exhibit rooms. A room is identified by a unique room number and has a size (in square feet).

Some of the BestArt paintings may be on loan to allied museums, typically for several months. BestArt may also have temporary possession of paintings loaned to it by allied museums. They are shown in exhibit rooms alongside BestArt paintings, typically for several months. Each allied museum has a unique name, a city, a state, and a curator (with whom BestArt negotiates loans). Paintings loaned to BestArt or by BestArt will also be in the database and will have the same attributes as the paintings owned by BestArt, plus a return date

Customers of BestArt consist of members and non-members. Members may be VIP or regular members. VIP may be benefactors and/or docents. Benefactors have a level (e.g., silver, gold, …). There is an expiration date for regular members. A docent may have one or several specialties, such as cubism and impressionism. A docent may volunteer to be present at certain dates and times in a specific room to explain the room paintings to visitors. In honor of a painting loaned to BestArt, there may be one or several gala-nights at different dates, with invitations to some benefactors. BestArt also organizes art-nights. An art-night will involve a discussion about one painter by one docent. A date and time is specified. Non-members who wish to attend art-nights are required to register in advance. A museum room may or may not be specified for an art-night.

The following data is assumed for all persons in the database: a unique id, a name, sex, year of birth, year of death (when applies), country of birth.

what I consider to be his hints
2. As discussed in class concerning the qualities of an ERD, completeness is more important than simplicity. For example, if the information requirements describe in some length different categories of PAINTINGs, with different relationships to other entities, maybe that tells you if your ERD should have a single entity or a Generalization Hierarchy.

  1. Do not spend too much time in trying to identify early on a weak entity and an associative entity, if you have trouble with them. Good GH and relationships come first. (you can still get an A, albeit with a slightly lower score, without the correct weak entity and associative entity).

Thanks in advance to anyone who can help!

Dani AI

Generated

In 's thread the "generalization hierarchy" hint is best treated as a prompt to separate shared painting attributes from loan-specific data. Practically, keep a single PAINTING entity (artifact_no as PK) for canonical attributes and model each loan as an associative LOAN between PAINTING and ALLIED_MUSEUM with attributes such as loan_direction (inbound/outbound), start_date and return_date. That approach preserves one source of truth for a painting and lets the database record multiple loan events over time; specializing into OWNED_PAINTING vs LOANED_PAINTING is only preferable if those subtypes require different integrity rules or exclusive attributes.

Model PERSON as the central people entity (person_id PK) and treat membership and volunteer roles as roles or light specializations. Use a partial MEMBER -> {REGULAR, VIP} specialization, and represent BENEFACTOR and DOCENT as overlapping roles (VIPs can be one or both). Store benefactor level on the benefactor role record and make DOCENT_SPECIALTY an M:N table so a docent can have multiple specialties. Capture docent availability with an associative DOCENT_SHIFT (docent_id, date, time, room_no).

INVITATION and REGISTRATION are good weak/dependent entities: INVITATION can be keyed by (gala_id, benefactor_id) or by a surrogate invitation_id; REGISTRATION by (artnight_id, person_id) and created only for non-members. Link GALA_NIGHT to the relevant LOAN (not just the painting) because the gala honors a loan event. Follow a workflow like @LastMitch suggested: identify entities and PKs first, convert multi-valued attributes to M:N tables, promote relationships-with-attributes to associative entities, mark optionality (e.g., painter FK 0..1), then decide disjoint/overlapping and total/partial specializations and finally annotate cardinalities.

Recommended Answers

All 6 Replies

Member Avatar for Member #949455

I attached what I have so far as ERD1.pdf (didn't establish relationship type/participation constraints yet)

You need to show some effort. Can you post any chart you done related to the ERD assignment you have?

Member Avatar for Member #949455

I did attach it it is called erd2.pdf. Ill attach it to this post as well

It's incomplete. That's why I ask any other chart(s). The chart you provide won't able to create a query because your table structure is not fill correctly.

You only did 1/4 of the work. That is not much. You need to do at least 3/4 of the work. There should be a chart from your book that you can used as a reference that you can follow.

@LastMitch Thanks once again for responding, at this point im not worried about being able to create a query. The assignment is just to draw a ERD. The textbook was written by my professor(Koster) and only has one complete example of and ERD for a university. And of course I did use this example to get as far as I have.
Any other thoughts on how I get to 3/4ths completion?

I attached a jpeg of the example in the textbook
http://i172.photobucket.com/albums/w34/rob9095/kostererd.jpg

Member Avatar for Member #949455

Any other thoughts on how I get to 3/4ths completion?

I guess you can used logic model outline to do the assignment. Then you will understand how ERD works.

@LastMitch I guess your not going to help haha i finished my assignment anyways and ill let you know how i do. I attached my final ERD if anyone would like to see it.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.