|Open||None||T107937 Streamline workflow for setting up groups that are not courses|
|Resolved||awight||T120510 [Epic] Implement course "type"|
|Resolved||Abit||T125724 Spike: Which wikiedu features still need to be customized for more general use?|
|Declined||None||T125773 Clean up and improve course type implementation|
|Invalid||awight||T126413 Don't restrict who can assign articles|
@AndyRussG asked me to illustrate how the interfaces would need to change for the different program types. These show where language should be changed and education features should be struck. Where not noted, "course" should become "program", "school" "institution", "instructor" "organizer, and "students" "participants".
Another tidbit: writing contests should only track content created as part of the contest, as opposed to any content created on that account. Editing on some writing contests could be tracked by categories, but some, like WikiCup or the tyop contest, cannot be tracked by category. Do the metrics on the Dashboard track all editing by a user, or just the editing related to a course?
We've already started modifying course pages based on course type. Here is a Visiting Scholarship course, which has the course/student language replaced with more generic terminology: https://dashboard-testing.wikiedu.org/courses/test/Visiting_Scholarship_Test_%28test%29
For that course type, we also only track metrics for articles that are explicitly assigned, rather than all the edits that enrolled users make during the course timeframe. This happens by changing the "revisions" scope of the course and only counting revisions to articles that have associated assignments for the course.
While we're collecting features to axe, this welcome page should not say "have your instructor give you a passcode"--enrolling in a password-protected course is when we should ask for a passcode.
Part of the intent of that kind of messaging is to make it clear that this is not a MOOC platform where you can browse and join arbitrary projects.
That specific messaging is particular to the Wiki Ed use case, but the idea is that receiving a link that includes the passcode for the intended course is the main entry point for non-instructors. That basic concept is probably relevant for many of the use-cases for the Wikimedia instance, although maybe not all.
I'd like to do this anyway. Milestones is pretty closely tied to a course plan that looks something like a typical Wiki Ed course timeline, and it won't necessarily make sense for many kinds of projects, including Editathons.
I was curious about Talk page metrics... Do these factor in anywhere? Are there any projects where it would be useful to surface this number?
I imagine there could be some projects, but not ones included in our current uses cases.