opensalt
opensalt copied to clipboard
Add jurisdiction attribute to frameworks
AS A teacher viewing OpenSALT
I WANT to find the frameworks relevant to me and my students
SO THAT I do not need to look through all the available frameworks to find ones that are useful
Tagged for UI work.
- do we want to start having users sign up with grade level, subject or geographic information or get that from their browser?
I'm not sure we need to have users provide that information yet, especially since most of the "teacher" users for this story would be expected to be anonymous users.
How should we structure the jurisdiction
attribute?
Did we want it to be just a plain text field or more structured to have a hierarchy and possibly allow for ip locationing to make it possible to hoist relevant content for a user based on where they seem to be coming from?
We need to have a conversation about jurisdiction, org and license together. There should be some org defaults for both license and jurisdiction, and maybe even a new helper object for each (For SALT and CASE). We should also talk with customers about what they need (e.g. states and districts).
@jmarks The listed story has nothing to do with organisations nor licences.
Yes, we need to work on how to make things easier for creating frameworks, but this is more about the consumption of frameworks.