The historical entitlements import is available to all Order Tool institutions. This import might be used to support the addition of a learning tool (e.g. TopHat Classroom) to an institution’s catalog. For example, an institution might seek to add TopHat Classroom to its catalog and require a backfill of historical entitlements to ensure that students are not overcharged. These historical entitlements represent purchases that students made outside of Order Tool but allow them to access TopHat Classroom for the lifetime of their enrollment. By importing an institution's historical entitlements, students will not be charged again for use of the learning tool in future courses where it is adopted (where the entitlement is valid). Order Tool will have a record that the student has an entitlement and report it accordingly in the Final Declined Offers Feed based on the import of historical entitlements.
To implement a run the historical entitlements import, please reach out to the Unizin Services team via support ticket to discuss your use case. An institution must When proposing your use case, please provide details of the digital course material they’re seeking to add to their catalog in Order Tool and the reason that a backfill of historical entitlements is required for this.
Since there must be, at most, one offer per academic term, a backfill academic term must be created by the institution for every backfill offer needed. An For example is , an institution that would like might want to backfill entitlements where students are entitled to the catalog item for the lifetime of their enrollment and for 1-year access. Given this example, the institution would create two backfill academic terms which will be added to the SIS Feed for one import. The terms in this example would be be:
- 1-Year Backfill
- Lifetime Backfill
The Unizin team will archive these two terms after a successful import. The institution would only need to provide these backfill terms once. Once the academic term is archived, the term start and end dates will be set by Unizin to 01/01/2000 to 12/31/2000, respectively.
Next, the Unizin team (i.e. Director of Partnerships) will create a backfill offer for each backfill term. These offers must be associated with the same content record, and that content record will be the same record used for future offers. The list price, offer price, and student price for each backfill offer should will be $0 since it was paid for outside of Order Tool.
Once the backfill offer records are created in an institution’s production tenant, the offer ids must will be provided to the institution. From here, the institution (often in partnership with the publisher or learning tools vendor) will create an “entitlement.csv” file.
Next, an institution will upload the “entitlement.csv” file to their “sis-data” bucket, for the appropriate environment (UAT or PROD) to BrickFTP. The Unizin team recommends testing this import in UAT prior to performing it in an institution’s PROD tenant. To run the import, the Unizin Services team work with engineering to perform this at will run the import on an agreed-upon date/time. Unizin engineering should be able to provide a final report of the number of entitlements created and the set of records (from the CSV) where an entitlement was not created and why. The set of records where an entitlement was not created will be provided back . Once the import is complete, the Unizin team will provide a report describing the outcome of the import. In the case that some entitlements could not be created, those records will be communicated to the institution for review.
Unizin will also discuss with the institution how they intend to facilitate ordering for this digital course material in the future. For some institutions, it might make sense for the Unizin team (i.e. Director of Partnerships) to add these offers manually. For other institutions, it might make sense for them to provide content and offers through the Institutional Catalog Import. This process will be performed on a case-by-case basis.The Unizin team will work with you to determine the best approach for your use case.
The entitlement.csv file must contain all data outlined below.