Top of ENR | Index | Table of Contents | Feedback | ![]() |
ENRF5900 - Merge Person With Two IDs
Purpose |
To merge the records of a student with two ID numbers into one ID number |
|
SubSystem |
Enrolments |
|
Normally Run By | Enrolment Specialist | |
Anticipated Frequency | As required | |
Structure | Blocks | Merge IDs |
Merge Table Name | ||
Information | ||
Action Choice | ||
Buttons | Determine Actions | |
Merge Person IDs |
Merge IDs block 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 block 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 block 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 block 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 check box. (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 check box 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. |
The Merge IDs block contains:
The Merge Table Name block contains:
The Information block contains:
The Action Choice block contains:
|
Rules/Notes: The Obsolete ID is available for reallocation once the merge is complete. Note: Care should be taken not to merge two ID’s in BOTH directions. This could cause unpredictable results in some other processes, and some may fail altogether (e.g. STAJ0100). If you need to re-do a merge in the opposite direction, you should first ensure that records created in the original merge are cleaned up (in particular, alternate_person_id records should be deleted). |
To
merge the records from two ID numbers under one of those numbers using the
Merge Person With Two IDs form:
If the merge process is unsuccessful, error messages are displayed advising of the problem. Either:
|
Rules/Notes:
When the merge process fails to copy any part of the obsolete data to the current ID, the whole process 'fails' and no obsolete data is transferred. Callista can identify many instances where data cannot be merged and reports on each in the Action Choice block. The Perform Action check box is automatically deselected in these cases. If the merge process fails, solutions should be sought from those action choices with the Perform Action check box selected. |
Last Modified on 16 April, 2007 2:37 PM
History Information
Release Information | Project | Changes to Document |
10.0.0.0.0.0 | C20672 | Added 'Note' in first 'Rules/Note' area |