🧐 Fix remaining sync issues, adjust schema #58
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change resolves remaining issues introduced by #57 and #53.
The schema has had some slight adjustments made necessary by changes to MyPurdue as well as breaking changes to the database library detailed here:
Capacity
,Enrolled
,RemainingSpace
,WaitListCapacity
,WaitListCount
, andWaitListSpace
are no longer available onSection
. Recent changes to MyPurdue have made it not feasible to synchronize these values. This is tracked in No unauthenticated information source for capacity, enrolled, remaining space, and wait lists #56 for a potential future solution.StartDate
/EndDate
onMeeting
,Section
, andTerm
is now stored asDateOnly
objects, and may be nullStartTime
onMeeting
is stored as aTimeOnly
object, and may be nullSome offline conversion tables were introduced for pieces of information CatalogSync no longer has access to, such as campus/building short codes. Tracked in #54 and #55 for potential future solutions.