Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

What is a “Ghost Programme Membership”?

Occasionally we will receive a Slack/Email alert from Metabase that indicates we have a “Ghost” Programme Membership. This Programme membership will appear in the database and will be identical to another, but it will not be visible to the user in Admins UI - it is a “ghost”

What do I do about them?

  1. Use the PersonId and ProgrammeId provided in the Alert to find the offending Programme Memberships

    • If you log on to Admins UI, you will notice that only one of these Programme Memberships is visible

    • If you search for the Programme Memberships in the CurriculumMembership table, you will likely notice two different curriculums

  2. If possible, find the user that submitted the latest change to the Programme Membership

    • Search TCS logs for the PersonId in the logs to find the audit event (e.g. “AuditEvent: type=tcs_updateProgrammeMembership user=firstName.LastName@nhs.net")

  3. Contact the user to determine which of the Programme Memberships has the correct curriculum membership assosciated with it

  4. Delete the incorrect programme membership and curriculum membership from the database

  • No labels