HMH Rostering Service allows you to store one or multiple Key IDs for users, which are stored in Ed, Flight, and NWEA.
By storing and sharing any of these fields, we can support all the NWEA ICP integration vendors as well as NWEA state contract reporting needs. An example of users values with each of these IDs is provided on this page.
This page gives you the power to map one or many user IDs to fields in our platforms, which will be used in reports and exported data sets. In the case of NWEA, many of these IDs are used to share data with states and/or 3rd-party Instructional Connection Provider (ICP) vendors to support data interoperability. HMH strongly recommends that you map populated data for at least the StaffID, StudentID, and StateID fields. ICP vendors look at any/all ID fields, not just hard coded to one value.
Depending on how you roster, the system attempts to select fields for you, but you can change that if needed. None of these IDs will lead to user duplication. If you choose the wrong value, just change it and re-import.
Step-by-Step Instructions
Note: The options you see on this page depend on the rostering data provider you are using. The data being sent in the rostering feed is what will be used in these selection options.
1. For each HMH ID, select an option in the Mapped ID list. Note the following:
– If you want to populate the StaffID field, click in the Mapped ID field for Staff ID and scroll through the list to locate the incoming field from your rostering data feed that contains the local staff ID you want stored in the HMH Systems.
– If you want to populate the StudentID field, click in the Mapped ID field for Student ID and scroll through the list to locate the incoming field from your rostering data feed that contains the local student ID you want stored in the HMH Systems.
– If you want to populate the StateID field, click in the Mapped ID field for State ID and scroll through the list to locate an incoming field that holds your student State ID value. If you do not want staff state IDs populated, be sure the data sent in this source field is only populated for students.
Note: Student and Staff IDs are expected to be district unique across all users in the district. StateID is expected to be unique across all students in the state and may have state specific length and values required.
2. If needed, click Preview to see an example of your selected Mapped ID.
3. Click Next.
See Next: Manage Preferences