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

SPIKE - what will be required to fetch Course and other Rosters from: D2L, Moodle, Blackboard #1618

Open
mkdir-washington-edu opened this issue Dec 13, 2024 · 0 comments
Labels
dashboard 1 Dashboard tags 1 and 2 are for grouping "fast follow" and "future" work after MVP feature request

Comments

@mkdir-washington-edu
Copy link

The problem:

After the completion of the project to collect Course, Assignment, Group, and Sections rosters for Canvas, there's an open question as to whether we'll be able to also fetch these types of rosters in the remaining LMSs easily (using data we're already able to receive from them) or if we'll need to investigate and use new parameters to fetch this data.

The outcome of this spike will help inform the prioritization around fetching rosters for other LMSs.

The solution:
An initial investigation to determine the level of effort and what will be needed to fetch some or all rosters from D2L, Moodle, and Blackboard LMSs.

@mkdir-washington-edu mkdir-washington-edu added dashboard 1 Dashboard tags 1 and 2 are for grouping "fast follow" and "future" work after MVP feature request labels Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dashboard 1 Dashboard tags 1 and 2 are for grouping "fast follow" and "future" work after MVP feature request
Projects
None yet
Development

No branches or pull requests

1 participant