[Building Sakai] Status IMS LIS support

John Bush jbush at anisakai.com
Wed Oct 16 10:46:57 PDT 2013


Correct, I think the data format going thru LIS is based on that stuff,
probably looks pretty similar.  The key is understanding that model, and
getting really good with the sakai course mgmt model, and understanding how
that works in Sakai.

You definitely don't need to implement the whole spec, there are for
example a bunch of redundant methods.  What LIS added is most the protocol
of the exchange rather than just the data spec.  There's both a batch and
an event driven model.


On Wed, Oct 16, 2013 at 6:53 AM, Mark J. Norton
<markjnorton at earthlink.net>wrote:

>  LIS is considerably more complex than the older Enterprise spec, though
> LIS did grow out of it.
>
> - Mark Norton
>
>
> On 10/16/2013 3:56 AM, Mark Breuker wrote:
>
> Hi John,
>
>  I didn't mention the SIS [1] because as far as I know it's only used in
> The Netherlands.
>
>  We have done a partial implementation of IMS Enterprise in the past
> which was pretty straight forward, mainly because of the SDK provided by
> Cetis. Do you think LIS (apart from the fact that it has a broader scope)
> is more complicated to implement?
>
>  Cheers,
>
>  Mark
>
>  [1] http://www.trajectplanner.nl
>
>  ------------------------------
> *Van:* John Bush [jbush at anisakai.com]
> *Verzonden:* dinsdag 15 oktober 2013 18:23
> *Aan:* Mark Breuker
> *CC:* sakai-dev at collab.sakaiproject.org
> *Onderwerp:* Re: [Building Sakai] Status IMS LIS support
>
>  We built on unicon's work that was for peoplesoft to add LIS support for
> Sungard's banner.  You can find the most up to date work for that here:
>
>  https://source.sakaiproject.org/contrib/rsmart/msub/sakora/trunk/
>
>  I think knowing what SIS system you are targetting might help answer
> your question better.  If its Banner or PeopleSoft then LIS might work for
> you, since most of the work is done.
>
>  As Mark said, LIS is big and complicated, it a big mess of xml soup.
>  Its one of those things where the spec gets you maybe 80% of the way there
> and then each vendor does the 20% a little different.   If I had to choose
> myself, I'd explore other more simple and straightforward routes to doing
> integration first.  It really depends on your needs.  For the majority of
> folks, batch processes work just fine.   If you need something more
> realtime, using Sakai's existing soap or rest services might be good enough.
>
>
>
> 2013/10/15 Mark Breuker <mbreuker at loi.nl>
>
>>  Hi all,
>>
>>  We are planning to build an integration between Sakai en our new SIS
>> and are considering using the IMS LIS specification [1] for this. I found
>> some information about the Sakora project on Confluence [2] but it seems
>> quite out of date (it dates from 2009 and mentions Sakai 2.6).
>>
>>  Does anyone know the current status of IMS LIS support in Sakai?
>>
>>  Thanks,
>>
>>  Mark
>>
>>  [1] http://www.imsglobal.org/LIS/
>> [2] https://confluence.sakaiproject.org/x/BAACAg
>>
>>
>>
>>    Mark Breuker
>> Product Owner
>> Tel.: +31 71 5451 203
>>
>> Leidse Onderwijsinstellingen bv
>> Leidsedreef 2
>> 2352 BA Leiderdorp
>> www.loi.nl
>>
>>  ------------------------------
>>
>> [image: Nederland wordt steeds slimmer. Leidse Onderwijsinstellingen]
>>
>> De informatie verzonden met dit e-mailbericht (en bijlagen) is
>> uitsluitend bestemd voor de geadresseerde(n) en zij die van de
>> geadresseerde(n) toestemming hebben dit bericht te lezen. Gebruik door
>> anderen dan geadresseerde(n) is verboden. De informatie in dit
>> e-mailbericht (en de bijlagen) kan vertrouwelijk van aard zijn en kan
>> binnen het bereik vallen van een wettelijke geheimhoudingsplicht. Indien u
>> deze e-mail ten onrechte ontvangen hebt, wordt u verzocht ons daarvan zo
>> spoedig mogelijk per e-mail of telefonisch op de hoogte te stellen, en het
>> ontvangen bericht (en de bijlagen) te wissen zonder deze te lezen, te
>> kopiëren of aan derden bekend te stellen.
>>
>> P  Denk aan het milieu voordat u dit bericht print
>>
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to
>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>> "unsubscribe"
>>
>
>
>
>  --
> John Bush
> 602-490-0470
>
> ** This message is neither private nor confidential in fact the US
> government is storing it in a warehouse located in Utah for future data
> mining use cases should they arise. **
>
>
> _______________________________________________
> sakai-dev mailing listsakai-dev at collab.sakaiproject.orghttp://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>
>
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>



-- 
John Bush
602-490-0470

** This message is neither private nor confidential in fact the US
government is storing it in a warehouse located in Utah for future data
mining use cases should they arise. **
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20131016/baf7d1b8/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 4378 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20131016/baf7d1b8/attachment.gif 


More information about the sakai-dev mailing list