Define the object model for the Curriculum API, review the
Discussion items
Time
Item
Who
Notes
Discuss curriculum model
team
Department users run the curriculum extract in STAR if they need to get curriculum data.
Anthony used to send the curriculum extract for engineering students (prof. Phil Conrad's course). They no longer request the extract as they do screen scraping from GOLD and try to rewrite the curriculum search. They also search by GE requirements. We need o add the GE requirements to the curriculum API.
Anthony will contact Phil Conrad when we have a first version of the API to review it.
Decided to publish at the QSO level, and propagate down data from QCO and Master Course.
Parameters for the Curriculum API: always by Quarter, by Department, College, Course ID (need to decide on course parser).
Discussed use of URIs. Steven and Diana will bring it to the API management group for discussion. Steven likes lighter response, without a lot of repeated data. Prefers not to use URIs, but keep the information in the API documentation.
Reviewed Github's API model. Ann really likes their model. They use URIs heavily.
Discussed use of lookup values in APIs. Steven prefers to not return descriptions, but let developers cache lookup table values for translations. Will discuss with the API group for a final decision.
Will use URI for paging.
Next meeting in 3 weeks.
Next steps:
Define the object structure
Define the parameter list
Decide on the parser for Course ID
Action items
@Mike Nesbit Add GE Requirements info to Curriculum API spreadsheet
Diana AntovaSteven Maglio discuss/set rules with the API management group about the use of URIs, use of lookup values in APIs, where to put paramenteres.