ER Diagram for Composite or Multivalued Attribute

[sleek geyser]

@vast marlin

Composite and multi-valued attributes can be nested to any number of levels. Suppose we
want to design an attribute for a STUDENT entity type to keep track of previous college
education. Such an attribute will have one entry for each college previously attended, and
this entry is composed of: college name, start and end dates, degree entries (degrees
awarded at that college, if any), and transcript entries (courses completed at that college, if
any). Each degree entry is formed of degree name and the month and year that it was
awarded, and each transcript entry is formed of a course name, semester, year, and grade.
Design such an attribute to hold this information using the ER diagram notation.

Pretty much this is what's asked of me

I was thinking like something like this

that's what I meant be multvalued composite attr

[vast marlin]

Can you use weak entities?

because that'd be the terminology for the grouping of those attributes that can only be accessed from the student entity

[sleek geyser]

I don't think so as I'm asked to only design an attribute

yeah...

[vast marlin]

I think the instruction to only 'design an attribute' might be a error(?) because it doesn't make sense to me either why all that data would be a single attribute

because to me a multivalued attribute is nesting all that data in a single column in a db, which makes 0 sense in this case, it'd make sense to have a one to many weak entity to the student -> education

[sleek geyser]

Idk, I just emailed the lecturer

See what's going on cause the question makes no sense to me

[vast marlin]

curious what they say

[sleek geyser]

I'll let you know

[vast marlin]

maybe i've misunderstood ERDs from day 1 idk lmaoooooo, we both be learning here

[sleek geyser]

@vast marlin

This is what I asked

This is what lecturer said

ngl that's pretty crazy