The lack of Lookup ability to cancel/delete old non-existing institutions (also banished from Jackdaw) is creating problems and confusions.
See #2
To add to requirements for new system
User admin register people involved in student teaching who are not in any existing inst node under the SPVSR[YY] nodes in Jackdaw; those accounts are subject to annual review - people continuing are moved into the current year node and anyone not doing so is added to a cancellation run. This fulfils the GDPR requirement that information held about people should be kept up to date. The people in question have been appointed to teach by a Director of Studies but have no other affiliation with the University and do not have an active CHRIS record as they are paid through CamCORS. Sometimes people in these nodes subsequently join the University and are then moved into a new node in Jackdaw when they appear on the CHRIS or CamSIS feeds or are registered by a College. Each of the SPVSR year nodes in Jackdaw maps across to a corresponding "College business [YYYY]" inst in Lookup. It is essentially a bucket for people with no other institutional affiliation who are not on a datafeed.
When the old SPVSR[YY] nodes are closed in Jackdaw the College Business groups persist in Lookup and also continue to have members, although anyone in the corresponding node in Jackdaw has either been moved to a later SPVSR year node or cancelled. It looks like the members of these insts are being seeded by Jackdaw, but not subsequently updated. The year groups should be removed once their purpose has ended and people should not be affiliated with them once the SPVSR nodes have been cancelled in Jackdaw.
Example: SPVSR11 is a closed node in Jackdaw with no members. It corresponds to the "College Business 2011" group in Lookup which has 13 members. Each of these members is affiliated with at least one other inst or the current "College business [YY]" inst in Lookup. The College Business 2011 inst is now 9 years old and ceased to be needed in 2012.
@amc203 To edit/add description.
The lack of Lookup ability to cancel/delete old non-existing institutions (also banished from Jackdaw) is creating problems and confusions.
See #2
It's unknown what the implications are of cancelling an {inst}-members
group as this is treated as a special group for the institution.
From the message at the top of a cancelled institution's members tab, this appears to be known behaviour, so hasn't been changed in the past:
I don't think we have capacity or priority to investigate this fully at the moment so pushing to backlog.
Deployed
The sync process reports reports that it needs to add various people to the groups in Lookup every run. These people don't get added as no person exists with the matching USNs (due to Lookup currently only having a single USN per person).
Filter out unrecognised (by Lookup) USNs before attempting to add them. Log these as warnings.
Follow on from #5
Back to review for deployment update https://gitlab.developers.cam.ac.uk/uis/devops/iam/deploy-identity/-/merge_requests/124
Robin Goodall (7a755b6c) at 13 Jul 08:21
Merge branch 'ignore-missing-usns' into 'master'
Working on MR for deployment.
The sync process reports reports that it needs to add various people to the groups in Lookup every run. These people don't get added as no person exists with the matching USNs (due to Lookup currently only having a single USN per person).
Filter out unrecognised (by Lookup) USNs before attempting to add them. Log these as warnings.
Follow on from #5
Robin Goodall (84fb45aa) at 13 Jul 08:16
The sync process reports reports that it needs to add various people to the groups in Lookup every run. These people don't get added as no person exists with the matching USNs (due to Lookup currently only having a single USN per person).
Filter out unrecognised (by Lookup) USNs before attempting to add them. Log these as warnings.
Follow on from #5
Per commit review may be easier
Makes no sense filtering 'remove' changes as these will only exist if the USN was already found in lookup group.
Closes: #6
Robin Goodall (7a755b6c) at 13 Jul 08:16
Merge branch 'ignore-missing-usns' into 'master'
... and 5 more commits
Per commit review may be easier
Makes no sense filtering 'remove' changes as these will only exist if the USN was already found in lookup group.
Closes: #6
Agreed, after actually making use of these myself in the admin tool having a skeleton class and then adding specific functions to it (if needed) using patch.object
is a good approach.
Ready for re-review
Also remembers to bump version number!