@dtod ,
I don't know of any options for custom data, but naming conventions for courses, terms, and sub accounts provide some decent compartmentalization, which can be effective for some downstream tasks and queries.
We use naming conventions across our integration to provide more detailed information to users and scripts.
Geoscience - S1 -- P03 - LASTNAME, F | 30800001-4 - FAL19
- Course topic
- S1 (semester 1 of 2)
- Period 3
- Teacher
- Curriculum Code
- Semester/Term
All courses from the SIS include the curriculum code, but when deployed with our content, we can track strings and files in the content to see who is using our content vs their own, and teachers and schools who recently started deploying our content, etc. This helps us with adoption, deployment and outreach questions.
We auto generate and allow employees to create additional work rooms.
WORKROOM -- Employee Name | CCSD
As well as School/Sub Account conference courses (essentially online teacher lounge/resources).
CONF -- School Name | 123
We can manipulate these in the UI
We also place courses into various sub accounts for different purposes
Workrooms (root)
School (each school has these)
- SIS Courses (all managed via integration)
- Manually Created Courses
- Conferences
- Course Shells
- Training
- Workrooms (school level workrooms)
- Online Tutoring
Homeroom courses are generated by the SIS for the online school, these land in School > SIS Courses > Student Services sub account. Students and Teacher are managed by SIS, but I typically try not to count them in stats.
Professional Development, which is a separate department has their own sub account and terms, this allows us to separate student and school stats from PDE.
Terms are useful as well
Forever (workrooms, conferences)
Professional Learning (PL 18-19)
K12 18-19 Fall
K12 18-19 Spring
K12 18-19 Summer