-
Notifications
You must be signed in to change notification settings - Fork 60.3k
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
[education] add documentation for configuring Blackboard LMS #35028
base: main
Are you sure you want to change the base?
Conversation
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
Automatically generated comment ℹ️This comment is automatically generated and will be overwritten every time changes are committed to this branch. The table contains an overview of files in the Content directory changesYou may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request. fpt: Free, Pro, Team |
@scollovati Thanks so much for opening a PR! I'll get this triaged for review ✨ |
Thanks for opening a pull request! We've triaged this issue for technical review by a subject matter expert 👀 |
A stale label has been added to this pull request because it has been open 7 days with no activity. To keep this PR open, add a comment or push a commit within 3 days. |
@nguyenalex836 may I help in finding a SME to review this? |
@scollovati That's very kind of you! Our internal SME team is actually reviewing this now. Once they have an update to provide, we will post here 💛 |
A stale label has been added to this pull request because it has been open 7 days with no activity. To keep this PR open, add a comment or push a commit within 3 days. |
A stale label has been added to this pull request because it has been open 7 days with no activity. To keep this PR open, add a comment or push a commit within 3 days. |
A stale label has been added to this pull request because it has been open 7 days with no activity. To keep this PR open, add a comment or push a commit within 3 days. |
A stale label has been added to this pull request because it has been open 7 days with no activity. To keep this PR open, add a comment or push a commit within 3 days. |
@nguyenalex836 may I help somehow? I see that also the bot has a bug, since it says "add a comment or push a commit within 3 days" but it immediately closes the PR. |
@scollovati Apologies on behalf of our bot! I've reopened this PR. Our team is still in the process of reviewing, but you'll receive an update as soon as we have more info 💛 |
Why:
Closes: https://github.com/orgs/community/discussions/44066
What's being changed (if available, include any code snippets, screenshots, or gifs):
This PR adds documentation for properly configuring the GitHub Classroom integration with Anthology Blackboard LMS. This LMS is fully compliant with [LTI1.3 Advantage](https://site.imsglobal.org/certifications/anthology/blackboard-learn), particularly the NRPS service used by GitHub Classroom for roster synchronization.
If this PR is accepted, we suggest the following improvements:
register-a-learning-management-system-with-github-classroom.md
).Important note: The optimal integration method for GitHub Classroom into Blackboard would involve GitHub managing a global registration in the Anthology Developer Portal (step #1 in
register-a-learning-management-system-with-github-classroom.md
). This approach is recommended by [Anthology](https://docs.anthology.com/docs/blackboard/lti/1.3/best-practices#why-vendor-tool-registration-is-best), as it allows each institutional deployment to be distinguished by itsdeploymentId
and platform URL. However,deploymentId
is not currently a configurable field on https://classroom.github.com/register-lms. Therefore, the registration flow proposed in this PR, which creates a uniqueclientId
for each institution, is currently the only feasible option.Check off the following:
I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).
data
directory.For content changes, I have completed the self-review checklist.