Purpose | To merge the records of a student with two ID numbers, under one of those numbers | |
Subsystem | Enrolments | |
Structure | Four Blocks | Merge IDs
Merge Table Name Information Action Choice |
Buttons invoke: | Determine Actions process
Merge Person IDs process | |
Image |
Merge IDs |
A person may be inadvertently recorded in the System under two (or more) ID numbers. This form is used to run a process which copies data from one of the ID numbers (Obsolete ID) into a single set of data under the other number (Current ID).
This block is used to record the two ID numbers to be merged. The Determine Actions button is then selected to display details of the data to be merged. Users of this function should have an understanding of the data being merged. |
Merge Table Name |
When the Determine Actions button is selected, Callista determines which database tables from both ID numbers are involved in the merge process and displays their descriptions in this block. Each of these tables can be selected in turn to determine the action(s) to be performed on the data they contain. |
Information |
This block describes the information contained under both IDs prior to the merge process. Based on the information displayed here, choices are made as to the actions to be performed during the merge process. Not all data has to be merged. Where data relating to two students is recorded under one ID, it is possible to selectively merge this data into the two correct IDs by performing this process twice, once for each current ID.
The block contains four fields, the fields on the left displaying information about data under the obsolete ID, the fields on the right displaying information about data under the current ID. The scroll bar on the extreme left is active when more than two information records exist for a merge table. The scroll bars to the right of each field are active when an information record occupies more than three lines of text. To interpret the data contained in these fields it is necessary to read the highlighted information in conjunction with the highlighted information in the Action Choice block. |
Action Choice |
When information is highlighted in the Information block, the proposed actions to be performed on this information are displayed in the Action Choice block. The choice is then made as to whether or not to perform the action by selecting or deselecting the Perform Action checkbox. (Default is selected for all actions). Where the System determines that an action is not possible, the reason is displayed in the Action Choice block and the Perform Action checkbox is deselected.
When all actions have been decided, the merge Person IDs button is selected to perform the process. Successfully merged records are automatically saved and cannot be 'undone'. If the merge is unsuccessful, it is most likely because some data under the obsolete ID conflicts with data under the current ID. Callista provides detailed messages which enable the user to determine the reasons for the failed merge and take action to either:
Where a merge is unsuccessful, the obsolete and current records remain in their pre-merge state. |
Example |
To merge the records from two ID numbers under one of those numbers using the Merge Person With Two IDs form: | |
| Rules:
|
Changes within this form will have the following notable effects: |