> For the complete documentation index, see [llms.txt](https://resources.unizin.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resources.unizin.org/products/data-and-analytics/unizin-data-platform/release-notes/2.0.99-allow-course-section-and-course-offering-lms-ids-to-be-provided-by-sis-data.md).

# 2.0.99

## Allow Course Section and Course Offering LMS ids to be provided by SIS data

| Version      | 2.0.99         |
| ------------ | -------------- |
| Release Date | March 24, 2022 |

## Key Features

The UDP now supports batch ingest of an `lms_ext_id` value in the Course Section and Course Offering entities in the SIS 2.0 schema. Separately, in this release, an update was applied to the Google Cloud Storage path bucket folder naming convention.

## Details <a href="#id-2.0.99allowcoursesectionandcourseofferinglmsidstobeprovidedbysisdata-details" id="id-2.0.99allowcoursesectionandcourseofferinglmsidstobeprovidedbysisdata-details"></a>

Course Offering and Course Section may now include an `lms_ext_id` in the SIS data, overriding any mapping (or lack of mapping) between the SIS and LMS found in the LMS data. That is, any `sis_ext_id` value provided by an LMS record referenced by the new SIS `lms_ext_id` field will be ignored upon ingest. This feature was introduced to address an institution's unique provisioning process, but may also be seen as the first in Unizin's general effort to allow greater flexibility in source system contributions.

Separately, the Google Cloud storage path folders for the SIS data now allow the naming convention to be defined by institutions rather than a predetermined format. Folders no longer need to contain the date value or otherwise. The latest SIS data will always appear last, and any number of sub-folders may be used. No changes are necessary to an institution's existing naming convention of the storage folders. The current date format remains supported.

## Known Issues

None.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://resources.unizin.org/products/data-and-analytics/unizin-data-platform/release-notes/2.0.99-allow-course-section-and-course-offering-lms-ids-to-be-provided-by-sis-data.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.