Component 3: Data
To help lay out details around data, let’s look at two different user stories. First we will consider Jack who needs information about the students in a district, so that they may access his company’s subscription learning service. Then we will take a look at Jill who wants her class roster with her on a mobile device, as she wonders around her classroom.
More details about the API can be found in the examples below and also in the SIF Data Model Implementation Specification (NA) 3.3.
In order to ensure all XPress Roster Providers add value, a baseline set of support has been established. While these tables layout a set of recommendations, the A4L Community fully recognizes that some use cases may require omitting certain data elements. Therefore software meeting these minimums may be badged differently than those that do not.
We’ve reviewed how to properly access data by: asking permission, formatting information requesting, and processing the data available. Let’s walk through the two examples to illustrate how these processes come together.
User Scenario 1: Provisioning Educational Systems
Jack sells online learning for “Earth Sci 9H”, a popular online earth science curriculum. Planet School District purchased Jack’s curriculum only for its students who are taking earth science and the teacher teaching it. The school’s online learning platform uses XPress to securely connect the district and its content publishers. “Earth Sci 9H” has been given XPress Roster credentials to the district’s data. Jack wants to make sure that only teachers and students actually taking earth science will be set up with “Earth Sci 9H” accounts.
First Jack’s application requests all the courses and finds all courses of interest.