Changes between Version 12 and Version 13 of ERModel

Timestamp:

09/21/26 15:26:45 (6 days ago)

Author:

236024

Comment:

--

ERModel

@@ -55 +55 @@
 ==== !MembershipStages ====
 
-!MembershipStages stores the possible membership stages used in membership history, such as observer, young member, full member, and alumni. It is modeled separately even though the member subtypes exist because the has_stage relationship needs to store historical periods with valid_from and valid_to.
+!MembershipStages stores the possible membership stages used in membership history, such as observer, young member, full member, and alumni. It is modeled separately even though the member subtypes exist because !MembershipStageRecords store historical periods with valid_from and valid_to.
 
  * '''Candidate keys:''' ms_id and ms_name. ms_id is chosen as the primary key because membership stage names are text labels. ms_name is unique.
@@ -218 +218 @@
 ==== Members Membership-Type Specialization ====
 
-This disjoint specialization separates Members into Observers, !YoungMembers, !FullMembers, and Alumni. It is needed to show the main membership stadiums clearly in the conceptual ER model. The historical periods of these stages are still stored through has_stage.
+This disjoint specialization separates Members into Observers, !YoungMembers, !FullMembers, and Alumni. It is needed to show the main membership stages clearly in the conceptual ER model. The historical periods of these stages are stored in !MembershipStageRecords.
 
 ==== !OrganizationalFunctions Board/!NonBoard Specialization ====