I work at Wake Forest University School of Medicine and we just purchased InteDashboard. I am looking for tips on naming courses when we have the same course on two different campuses if anyone has any. We have thought about putting city in the beginning of the course name, but was curious if anyone had any best practices.
Regarding team naming conventions, while I can’t speak to universal best practices, I’m happy to share our approach. At our institution, we manage two campuses: Duluth (DL) and Twin Cities (TC). For clarity and consistency across both InteDashboard and our LMS (Canvas), we use a simple, location-based naming system: Team TC1, Team TC2, Team TC3, etc. for Twin Cities teams, and Team DL1, Team DL2, etc. for Duluth teams.
1 Like
Here are some of the best practices that we follow internally:
- Be consistent: Use the same format every time.
- Keep it scalable: Format should work across campuses, terms, and growing numbers of sections.
- Make it human-readable: Avoid codes or abbreviations that only insiders understand.
- Limit to 4–6 words in course name to avoid system cutoffs.
A good formula might look like:
COURSE NAME : [Course Name] - [Semester]
COURSE CODE : [Course Code]
SECTION NAME: [Campus Code] - [Section Identifier] - [Day/Time or Semester]
