# Credentials IDA: Implementing old ADR with change to Certificate date availability internals **URL:** \ **Category:** Architecture\ **Created:** [June 21, 2024, 5:06pm UTC](https://discuss.openedx.org/t/credentials-ida-implementing-old-adr-with-change-to-certificate-date-availability-internals/13259 "2024-06-21T17:06:20Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![deborahgu](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/deborahgu/32/5782_2.png) [@deborahgu](https://discuss.openedx.org/u/deborahgu)\ **Post date:** [June 21, 2024, 5:06pm UTC](https://discuss.openedx.org/t/credentials-ida-implementing-old-adr-with-change-to-certificate-date-availability-internals/13259/1 "2024-06-21T17:06:20Z")
More than 3 years ago, a Credentials ADR was proposed and accepted: [0001 Certificate Available Date](https://github.com/openedx/credentials/blob/master/credentials/apps/credentials/docs/decisions/0001-centralize-certificate-available-date.rst). The purpose of this ADR was to move away from having both `CourseCertificate.certificate_available_date` and a calculated visible date per awarded certificate. At the time, technical issues arose, and prevented this from being implemented fully. It was partially implemented, but partially rolled back, and the current implementation is mixed. Now, although the relevant date information is available in the `CourseCertificate`, we are still communicating an updated date visibility calculation for every `UserCertificate`. This can cause massive load spikes given certain changes to a course overview, for obvious reasons (updating thousands of individual awarded certificates, rather than a single course certificate configuration). 2U’s Aperture squad intends to fully implement this ADR. We are raising it here because it was never fully implemented in the past, and it has been several years, so we want this not to be a surprise.