Syrup+Evergreen: Campus SIS information exposed via OpenSRF?

[Graham Fawcett]

Hi folks,

Part of running Syrup is specifying a set of campus-integration
functions: things like "tell me who is registered for ENG-101" and
"what course sections are taught by Prof. Jones". These functions are
specified by an interface, and it's up to the institution to define
appropriate implementations.

In the context of Syrup-with-Evergreen, it occurred to me that it
might be preferable to have the campus-integration services exposed
via OpenSRF, so that other OpenSRF clients could ask the same kinds of
questions. So, looking up a class list might take a call to, say,
('windsor.courses.sections.members.retrieve', 'ENG-101').

Would that be useful to anyone? I'm not looking to make work, but if
there's a use for exposing this kind of info in a way that's broader
than Reserves, then it might be worth investigating.

Best,
Graham

[robin]

I couldn't agree more! In fact, this is exactly what I was going to
suggest for the Syrup integration into Evergreen. In fact, some of
the workflow as I envisioned it was based on OpenSRF services talking
to each other.

cheers,

Robin