Closed mackensen closed 6 years ago
We worked around this by identifying the outdated rows in mdl_enrol_lmb_crosslists
and deleting them, which allowed the enrollments to process on the now-independent courses.
For future reference, the "proper" way to do it would be to inject XML that looks like this to remove the members from the crosslist:
<membership>
<sourcedid>
<source>Oakland University SCT Banner</source>
<id>XLSAA201510</id>
</sourcedid>
<member>
<sourcedid>
<source>Oakland University SCT Banner</source>
<id>14482.201510</id>
</sourcedid>
<idtype>2</idtype>
<role roletype = "02">
<status>0</status>
</role>
</member>
<member>
<sourcedid>
<source>Oakland University SCT Banner</source>
<id>14483.201510</id>
</sourcedid>
<idtype>2</idtype>
<role roletype = "02">
<status>0</status>
</role>
</member>
</membership>
On Wed, Jan 14, 2015 at 10:57 AM, Charles Fulton notifications@github.com wrote:
We worked around this by identifying the outdated rows in mdl_enrol_lmb_crosslists and deleting them, which allowed the enrollments to process on the now-independent courses.
— Reply to this email directly or view it on GitHub https://github.com/merrill-oakland/Banner-Luminis-Message-Broker-for-Moodle/issues/7#issuecomment-69938063 .
@merrill-oakland just to ensure I understand, this would be a one-time injection of XML so that LMB could handle things correctly? If we're doing folder processing, we'd add something like fixup.xml
containing the above?
Correct.
I'm planning on fixing this problem in the LMB/ILP rewrite currently in progress over at https://github.com/merrill-oakland/lmbnxt.
Thanks!
We have a scenario where two courses were crosslisted and became a merged course, but this crosslisted was later undone by the registrar. The merged course remains, and there are no enrollments in the original courses. I can see the entries in
mdl_enrol_lmb_crosslists
; would changing the status to 0 and re-running the enrollments fix the issue?