Pending data shows records for users not automatically imported from the University data feed, usually if the user's details, except for the card number, match those of existing account holders in your MSL System. Managing pending data is essential; users in this state cannot log in until the issue is resolved - this is a safeguarding mechanism to prevent users from logging in with multiple accounts for activities like voting in your elections.
If a student's card status indicates they're in pending data, resolve their login problem through the Pending Data window. Clicking the Last Imported column header re-orders users according to their current status in your data file, allowing you to prioritise currently enrolled students.
To find a specific record, you can filter the Pending Data window by the user's card number. Clicking an ID/ Card Number displays the people considered as potential matches by the MSL System, along with a message indicating why it hasn't imported the record, for example "Card number link does not exist, but there are possible matches" indicates that someone with matching details (e.g. name and date of birth) is already registered in the system without a linked card number.
Upon selecting a user, choose an action from the displayed options:
For more details on the actions shown, see Pending Data Fields.
TABLE OF CONTENTS
You can access this feature from your MSL System Admin site. Only Super Admins with Membership Admins or Site Admins permissions can access the Pending Data windows.
Before proceeding, if you're uncertain about which action to take for a person's record, consult your University records team. They can help determine whether two users are different individuals or the same person. Remember, merges cannot be undone. In some cases, such as twins with the same date of birth in the same year of study and on the same course, careful consideration is necessary.
If you have several pages of records in Pending Data, contact support@ukmsl.com to arrange a bulk merge. Note that this merge is for clear matches where the first name, last name, and date of birth are an exact match. Manual handling will be required for any users remaining in Pending Data.
For further information, see People Overview.
Pending Data Fields
This table lists and explains the fields in the Pending Data windows.
| Field Name | Definition |
|---|---|
| First Imported (Date) | This refers to the first recorded appearance of the data record. |
| Last Imported (Date) | This refers to when a record last appeared in the data file. If this date coincides with today, the record remains in the file. |
| Inserted Date | This refers to the initial creation date of the account in your MSL System. This field is displayed only in the Import Person window. |
| Inserted By | This is the the super admin who created the account. If the user's identifier is UKMSL\sql.service, UKMSL\AMBER$, UKMSL\BRASS$, UKMSL\CRESS$, UKMSL\LEAD$, or UKMSL\RUBY$, for example, it indicates a system activity like data import or registration. This field is displayed only in the Import Person window. |
| Updated Date | This refers to the most recent date the account was modified or changed. This field is displayed only in the Import Person window. |
| Updated By | This is the the super admin who updated the account. If the user's identifier is UKMSL\sql.service, UKMSL\AMBER$, UKMSL\BRASS$, UKMSL\CRESS$, UKMSL\LEAD$, or UKMSL\RUBY$, for example, it indicates a system activity like data import or registration. This field is displayed only in the Import Person window. |
| Registration Attempts | This refers to the number of times a user has tried to validate their account through a data match registration page. Data match registration pages are used on sites with a data file, but without single sign-on (SSO) login. This field is displayed only in the Pending Data window. |
| Last Attempt | This refers to the last time a user tried to validate their account through a data match registration page. This field is displayed only in the Pending Data window. |
| Import Anyway | Click to bypass the existing person check and import the account. This action is suitable when the users are definitely different people, for example, when the person's name closely matches an existing entry, but the date of birth is different. This field is displayed only in the Import Person window. |
| Update Card Number | Click to replace the existing person's card number with the one in the imported row. If the existing account doesn't have a card number, this action adds the one from the imported row to the account. Use this when the system correctly recognises the records as belonging to the same user, and the person's details are correct but the card number needs updating. This field is displayed only in the Import Person window. |
| Update Card Number and Details | Click to replace the existing person's card number with the one in the imported row, and update their name and date of birth. If the existing account doesn't have a card number, this action adds the one from the imported row, along with updating the name and date of birth. Use this when the system correctly recognises the records as belonging to the same user, and details need to be corrected, such as misspelled names, when a name has changed following marriage, or when both user details and card number need updating. This field is displayed only in the Import Person window. |
| Remove Row and Add to Block List | Click to add the imported number to the block list, preventing it from being imported in future data runs (beyond the set data validity period in your system's configuration). Use this when the system correctly recognises the records as belonging to the same user, and the imported card number is incorrect. This field is displayed only in the Import Person window. |