[OPEN-ILS-DOCUMENTATION] Book of Evergreen: suggestion for additional chapter

[Steve Wills]

I rather agree with Joe that the idea of a Systems Integration manual for EG is necessarily technical.

I would suggest that DIG generate a Users Manual and System Integration Manual as separate documents.
If I was going whole hog, I'd point out that most systems that are this complex actually target three groups separately.

Users Guide
System Administrators
Developers

These three groups generally have different interests and areas of expertise.  Try to speak to all three audiences in a single
document has the potential of not speaking to any of them.

Stev3
LYRASIS Open Source Consultant
________________________________________
From: open-ils-documentation-bounces at list.georgialibraries.org [open-ils-documentation-bounces at list.georgialibraries.org] On Behalf Of Joe Atzberger [jatzberger at esilibrary.com]
Sent: Friday, February 05, 2010 1:22 PM
To: Documentation discussion for Evergreen software
Subject: Re: [OPEN-ILS-DOCUMENTATION] Book of Evergreen: suggestion for additional chapter

Maybe "3rd Party System Integration" since it's not all about data access or retrieval.  Sometimes the integration wants to *do* stuff.

- other suggestions ?

SIP2,
Asterisk (telephony),
and (forthcoming) EDI.

These are all very technical, so maybe not the best for cookbook recipes.  They assume a lot of specialized protocol-intelligence on the part of the 3rd party.  But there is also enough capability from the SendEmail and SendFile reactors in the action/trigger framework that you could do dozens of different integration tasks with them, like updating remote webservers, pushing files onto print queues, emailing patrons copies of checkout receipts, etc.

--Joe