It is important for the Registrar to understand how data is inherited from one record to another in KEYSTONE. This diagram is designed to help explain the concept of Inheritance.
Certain values are assigned first at the resource level and are then carried through as Section, and then Registration records are created. These default values can generally be overridden both at the section level and the registration level.
FileMaker uses the term Looked-up values for data that are copied into another record; looked-up values, because they are copied, stand alone and can be edited. Looked-up data is not automatically updated if you create registration records, for instance, and then subsequently go back and change resource or section data.
Some changes made to resources or sections after a higher-level record is created will require a “refresh” or “re-lookup” to pull the new value “forward.” This scheme provides the maximum amount of flexibility overall, but the Registrar user must be aware of the need to refresh values after editing to ensure that changes are reflected correctly where needed.
The values include whether a course awards academic credit or not, whether it is counted toward the GPA, whether it is shown on the schedule, on transcripts or grade reports. Other values pulled forward include the timeblock, room, teacher, credits, etc.
Dynamically related data is live data viewed from a different record; changes to a dynamically related record are immediately seen everywhere the field is used.
