...
Squad / Contacts | Use Case | Status and Notes |
|---|---|---|
Phoenix (Kashif Chaudhry Jeremy Ristau) | Syncing CMS course run creation with Discovery. | Arch-BOM is currently working on implementing this use case. Currently handled with scheduled bulk updates. Has high latency and is prone to errors. |
Aperture (Kelly Buchanan TJ Tracy (Deactivated)) | Syncing catalog data from Discovery to Credentials | Currently handled with scheduled bulk updates. Has high latency and is prone to errors. |
Aperture (Kelly Buchanan TJ Tracy (Deactivated)) | Syncing course certificate and grade data from LMS to Credentials | Currently handled with async call from LMS directly to Credentials. Prone to errors, business logic breaks domain boundaries, no event reuse. See below for implementation notes. |
Purchase (Ben Holt (Deactivated)) | Ecommerce replacement, cross service calls. For example, data sent from LMS to new Ecom. | Need to plan for async direct calls until Event Bus capabilities exist. Events can’t easily be reused by multiple services without being routed by the ecom replacement service. |
Enterprise: Access: Titans (Brian Beggs) | Subscription plan creation, subscription plan expiration, license expiration, license renewals, learner enrollment changes | We need to create and remove things frequently that touch a number of systems (LMS, license manager, catalog manager) that are currently doing synchronously. This can cause timeouts, failures and is prone to errors due to transient errors on the systems being called. Nothing started yet. Would need something where events/messages could be fired and consumed by a number of systems. Also see https://openedx.atlassian.net/wiki/spaces/SOL/pages/3381428720 |
Content: Cosmonauts | Moving proctoring out of platform and into an IDA. Calls to the LMS to update grades, credit, completion, and certificates based on exam review. | This project is currently in the design phase. We would like to decouple a lot of these proctoring features that are currently spread across the LMS. |
Content: Cosmonauts | Detect some program intent actions to drive behavior | A later phase of program intent but I think likely to be implemented sooner or later. |
Brainstorm from Arch-BOM
...
Aperture/Kelly: Syncing course certificate and grade data from LMS to Credentials
...
Other use cases:
Additional parts of Refresh Course Metadata
Studio updates updating discovery
(Not right now) Catalog Caching for Prospectus builds
(Not right now) Improving the boundaries around course-discovery so that it could be removed or replaced with a different offering, either for 2U’s needs or because the community doesn’t generally use it
Would also help simplify development environments
Replacing synchronous calls from publisher (discovery) to lms/studio/enterprise
Maybe? Would need more discovery, including who would be the owner of the consumption.(Not right now) Publishing enrollment event for unknown/various future consumption.
Replacing synchronous calls from LMS to Discovery
Discuss next steps for choosing a use case:
...
Possible rubric for choosing?
Adds immediate value?
Low risk (redundant)?
Size
Can arch-bom implement independently? Use case won't be de-prioritized?
Will owner be happy to take on ownership burden in future?
Will it provide a golden path?
...
Who should I talk to?
...
Any more brainstorming or discussion of use cases?
...
Use Case Notes
Sync certificate and grade data from LMS to Credentials
...