Hi Kate,
This is a mix of implementation nitty-gritty and scenarios... might be a "day before a three day weekend" issue.
On the implementation side, I feel like this all needs some way for end-users (and admins) to manage the display of available sub-accounts for sharing. From the admin side, maybe this looks like the ability to switch on or off the following:
- Allow end user to share to the full list of sub-accounts (but not see the full list)
- Allow end user to only share to sub-accounts they are a part of
- Allow end user to share to individuals on this instance
- Allow end user to share to specific individuals in the rest of the world
For end users, maybe the default view is all the sub-accounts they can share to by virtue of their enrollments, and then a +More… link that allows them to pick from a larger list, and/or search by course code, instructor name, etc. within their instance.
Sharing across institutions feels like a place for Google Docs-type sharing interface. The person doing the sharing can decide to share with anyone who has the URL (and pick an access level - see, use, edit, share alike). Or, they can share only with specific email addresses. That seems like it could go under the More... button.
As for scenarios...
Sharing across departments in the sub-account structure (cross-listed courses) - One use case is the simple cross-listed course. While the regular enrollment-based sharing should work for that, it doesn't work as well when the faculty are still building the course before the actual shell exists in Canvas. For instance, we have a political science class that cross-lists into our legal program; they’re in different divisions.
Sharing across departments for basic skills/"service" courses - Over the years, we’ve had several initiatives that look like this: a short math class taught in a science department, reinforcing/remediating the math skills in that science class; an English class where the content is tied to a professional program (for example, Medical Assistant). The two instructors wouldn’t necessarily be able to see content in each others’ sub-account, but would need to share.
Sharing across institutions in a consortium - This really is like a super-account share, I guess. The idea is that a course author could designate a Commons item to be available to everyone in the system, but not to the world at large. In most cases, we just share them with the world, but a) occasionally there’s resistance to that or a restriction requiring we keep it local and b) something that really, truly is relevant only within these schools in this state (maybe a particular legislated requirement?).
Sharing with a scholar at another institution - So a faculty member at my institution is collaborating with faculty at three other institutions on a grant. They’d like to be able to share various course materials, but aren’t on the same instance of Canvas. They also aren't ready to share the materials with the world. For instance, the participants could share assignments or drafts of courses back and forth without the export/import hassle… and use notifications to share when they’ve finished their updates. Bonus points on this would be a way to manage outcomes for the materials. In our system, outcomes usually vary across colleges; some way to handle either “import and use the cartridge outcomes” or “skip the outcomes and link my own”.
Sharing with others who use the same open textbook - This probably isn’t much different than the above scenario, but a different use case for the same tools. Perhaps the workflow is ‘limited sharing to the people who are working on this thing’ until it’s considered ready for public consumption, then flip the switch to make it globally available.
Marc
This discussion post is outdated and has been archived. Please use the Community question forums and official documentation for the most current and accurate information.