Problem you are trying to address with this feature
Often we want to track down which application instance of many in a given LMS is being actively used and by whom. Currently this involves a combination of queries and guesswork to attach specific app usage over a specific date range to a given AI.
Additionally, some schools will make multiple deployments for different subgroups within the LMS, and we do not have a easy way to note which deployment is being used where.
Other scenarios where differentiating between AIs within a given org or LMS include:
Multiple course-level deployments during a pilot
We need to turn on partner integrations (e.g. JSTOR, VitalSource) for a specific deployment in an LMS, but not for another
Your solution
The addition of a note field -- editable using LMS admin portal -- would allow important misc, human-parsable info to be captured for future context about that AI.
Feature Request Form
Problem you are trying to address with this feature
Often we want to track down which application instance of many in a given LMS is being actively used and by whom. Currently this involves a combination of queries and guesswork to attach specific app usage over a specific date range to a given AI.
Additionally, some schools will make multiple deployments for different subgroups within the LMS, and we do not have a easy way to note which deployment is being used where.
Other scenarios where differentiating between AIs within a given org or LMS include:
Your solution
The addition of a note field -- editable using LMS admin portal -- would allow important misc, human-parsable info to be captured for future context about that AI.