Automatic PI identification

[cc-a]

Description

A port of the PI identification logic from the old portal. At the moment this is a single function in the policy module (and tests) that will be used in later PRs.

Fixes #65

Type of change

• Documentation (non-breaking change that adds or improves the documentation)
• New feature (non-breaking change which adds functionality)
• Optimization (non-breaking, back-end change that speeds up the code)
• Bug fix (non-breaking change which fixes an issue)
• Breaking change (whatever its nature)

Key checklist

• All tests pass (eg. python -m pytest)
• The documentation builds and looks OK (eg. python -m sphinx -b html docs docs/build)
• Pre-commit hooks run successfully (eg. pre-commit run --all-files)

Further checks

• Code is commented, particularly in hard-to-understand areas
• Tests added or an issue has been opened to tackle that in the future. (Indicate issue here: # (issue))

[jamesturner246]

Are these categories, and the others in here, relatively constant, or does any of it rely on manual entry? Seems a little on the fragile side if so. A shame they can't just all be precomputed as extra graph API parameters, but 'spose that is what's been given..

[jamesturner246]

Visiting profs can't be PIs?

[cc-a]

Only if they ask nicely.

[cc-a]

Are these categories, and the others in here, relatively constant, or does any of it rely on manual entry? Seems a little on the fragile side if so. A shame they can't just all be precomputed as extra graph API parameters, but 'spose that is what's been given..

All the data ultimately comes from Imperial's source of truth on identity data. We ultimately have to trust that that data is accurate. Reports from the platforms team are that this logic has been sufficiently robust for them so far.