Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate canvas_course_id from studio to plugin #12

Open
arslanashraf7 opened this issue Nov 15, 2021 · 0 comments
Open

Migrate canvas_course_id from studio to plugin #12

arslanashraf7 opened this issue Nov 15, 2021 · 0 comments

Comments

@arslanashraf7
Copy link
Contributor

Related to:
#7 (comment) & #7 (comment)

Description:
We created a field in studio advanced settings to map paltform's courses with Canvas Course IDs. (mitodl/edx-platform@b61152ac70#diff-5e5a9a90f02439d6bcd1f65bc96da133eedae87338ba248f7bd49a4752fbbaf7). Since the plugin support in openEdx doesn't currently support this type of enhancement so we couldn't move it to the plugin.

What needs to be done:

  • We should attempt to migrate this part from the platform into the plugin. (Possible approach defined below)
  • Migrate the existing keys from the Studio's Advanced Settings to the newly created mapping model defined below.

Possible Approaches:

1- One possible approach could be to create our own model in the plugin to map the platform's course Ids to the Canvas course Ids. This could be a simple model primarily having two keys e.g. patform_course_id, canvas_course_id probably with unique together constraints or any other if needed.

Frontend? Currently canvas_course_id key shows within Advanced Settings tab of a course in the studio. But, When moving this into the plugin based on the approach defined above, where/how should it look in the frontend? A simpler solution could be to set it in Django Admin but Is it feasible for the users to set this key in Django Admin?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants