Study leads

[iaindillingham]

The IG team have asked for information about applications' study leads.

Currently, an application is associated with a study lead. The study lead was the current study lead at the point when the application was approved. Ideally, when the study lead leaves the organization, the application should be associated with a different study lead. Ideally, an application's previous study leads should also be retained.

At present, it is possible to determine an application's current study lead and previous study leads by querying the Git history of the "Approved projects" page. This page is built from a collection of files that are mostly updated by @tomodwyer and @LiamHart-hub.

Based on a Slack thread,¹ we think Liam would be happy with the current/previous information coming from the "Approved projects" page. (The application would be associated with the study lead when the application was approved.) However, clearly querying the Git history is not ideal.

Footnotes

1. https://bennettoxford.slack.com/archives/C069SADHP1Q/p1710170906365829 ↩

[iaindillingham]

I'm going to move this to Later. There isn't a need for information about applications' study leads to be stored in job-server now; the "Approved Projects" page is a good, albeit short-term, alternative.

[lucyb]

I've added this to the list of things for a future initiative around permissions and I don't think we should start work on it just yet, so I'll move it out of the backlog. I think we need to gather some more requirements about what a study lead does, before deciding whether/how to model it within Job Server.