Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
E
edx-platform-release
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Package Registry
Model registry
Operate
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Hsin-Yu Chien
edx-platform-release
Commits
6b7a51f8
There was an error fetching the commit references. Please try again later.
Commit
6b7a51f8
authored
4 years ago
by
SaadYousaf
Browse files
Options
Downloads
Patches
Plain Diff
ADR for upcoming update for certificate_available_date.
parent
b9a51eb2
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
openedx/core/djangoapps/programs/docs/decisions/0001-sync-certificate-available-dates.rst
+46
-0
46 additions, 0 deletions
.../docs/decisions/0001-sync-certificate-available-dates.rst
with
46 additions
and
0 deletions
openedx/core/djangoapps/programs/docs/decisions/0001-sync-certificate-available-dates.rst
0 → 100644
+
46
−
0
View file @
6b7a51f8
Sync certificate_available_date and visible_date for certificates
=================================================================
Status
------
Review
Context
-------
In the Credentials service, certificate_available_date is called visible_date.
Whenever a generatedCertificate is updated or saved the first time, it sets
the visible date to certificate available date (available in studio settings).
There is a limitation in our code, if course team decides to change the
certificate_available_date it is not reflected in the credentials service
for all the certificates that were awarded before that change and have been
pushed to credentials service. The certificates' dates need to be in sync on
both places.
This has caused problems when a learner is able to see the certificate on
their dashboard but the change is not reflected on their learner record in
credential service.
Decision
--------
Whenever a CourseUpdate is made with change to the certificate_available_date,
the system updates the certificate visible_date on the credential service.
To achieve this, a signal is created to listen to any course update signal that
contains change in certificate_available_date and start a task to compute all
certificates that have been issued.
We will then reuse the award_course_certificate task for every certificate user
and get their visible_date updated on credential service to keep dates in sync
on both ends.
Consequences
------------
The system will have to process each issued user certificate and update the
visible_date for all of them individually as visible_date is an attribute for
every UserCredential object on credential service.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment