We would like to use Commons as a repository for individual content modules that we can reuse across courses. In the current settings, only the person who sent the content from a Canvas course to Commons can update the content in Commons, but in our case, we have a few people responsible for updating course content.
For example, we have a course on database design which is geared toward developers who will be administering databases. We also have software development courses where the learners only need a bare-bones understanding of relational databases and SQL. We would like to reuse only the first couple of modules from the database course in the developer courses. As it is now, when we import those two modules into the developer course, we create a copy that needs to be maintained in both places (for errata, especially). And then we have a client who wants to include the basic SQL module only with Linux, so we have yet another copy to maintain. Blueprints help reduce the number of copies we have to maintain, but it would be much easier if we had a single source of those modules that we can drop into courses as needed rather than multiple copies across Blueprints.
Commons would also be useful as a way of letting a SME see our existing content catalog without having to enroll him/her in multiple courses to see modules on different topics. The SME could simply pick and choose the modules and we would build a Blueprint for that course using only the selected modules.
Associating Commons updates to a single user rather than to a role seems fragile to me, especially in the current climate. If I "own" content in Commons but I am suddenly not able to work for an extended period of time, someone else would have to use my login to make those updates. A workaround would be to create a Canvas account as "Commons owner" and allow multiple people to use that account to create and update content, but then we lose the ability to see which user made those updates. There should at least be an option at the account owner level to allow admins to update Commons content, rather than restricting all updates to individual users across the board.