[OPEN-ILS-DOCUMENTATION] noting what sections need content - in outline or in docs

Joe Atzberger jatzberger at esilibrary.com
Wed Sep 1 17:05:39 EDT 2010


I would be qualified to write a good portion of the 3rd party integration
docs (SIP2, EDI, Asterisk, RemoteAccount, etc.), but I cannot commit to it
right now based on client priorities and deadlines... including getting EDI
finished.

--Joe

On Wed, Sep 1, 2010 at 2:38 PM, Repke de Vries <repke at xs4all.nl> wrote:

> Late reply from Repke: this was me proposing, discussing (number of
> responses) and adding this as a separate major section ("Part") to
> the outline page at the time.
>
> The point being that the Administration Part only indirectly covers
> for example SIP2 and SRU and does so from a very particular
> perspective: the Evergreen Administrator doing Administration.
>
> The idea behind this new Part "Third Part System Integration" is to
> turn that perspective to that of a "Third Party Developer" looking
> for information on Evergreen's degree of openness for third party
> apps (exposure) and which standards Evergreen has implemented to
> "talk to it" and access all the information it has in its database.
>
> Point taken that nobody volunteered but asking NOT to leave this Part
> out and have all the discussion around it (including reactions by
> Equinox) vaporise but rather to leave it in and have it in italics
> with a short comment "to be addressed later" or some such (like
> another colour in your coding scheme Robert).
>
> What do we think?
>
> Thanks, Repke
>
> Op 1-sep-2010, om 16:44 heeft Karen Collier het volgende geschreven:
>
> > Robert,
> >
> > The color coding is great.  Thanks for taking the time to put that
> > in place!
> >
> > Leaving out third party system integration for now, unless and
> > until there are volunteers interested in covering that topic sounds
> > perfectly reasonable to me.
> >
> > Thanks,
> > Karen
> >
> > ----- "Robert Soulliere" <robert.soulliere at mohawkcollege.ca> wrote:
> >
> >> Hi All,
> >>
> >> I did a bit of color coding on the outline page at:
> >> http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:outline
> >>
> >> I only did it at the chapter level and they are more like flags
> >> besides the chapter titles. Here is an overview at the colors and
> >> names of the flags:
> >>
> >> GREEN - DONE: This means that most content is in place. "Done"
> >> doesn't
> >> really mean "done" -- Editing and updating is still welcome and
> >> needed!
> >> BLUE - ASSIGNED: Someone has volunteered for this section, but
> >> content
> >> has not been submitted yet
> >> ORANGE - NEEDS WORK: Some content is in place but may need revising,
> >> checking, adding, etc...
> >> RED - NEEDED - Has not been started yet and we are not aware of any
> >> existing content.
> >>
> >> Notes:
> >> - Yellow was too light to be used so I used orange instead.
> >> - I believe the wiki formatting interferes with the html color
> >> formatting which is why I had to use flags and not color the titles
> >> themselves.
> >> - This is an organic outline in that sections may added, removed or
> >> changed as needed. There may be new sections or chapters required as
> >> we discover sections which are not covered.
> >> - Some of the red NEEDED comments have: "Beyond 1.6.1.x" which
> >> indicates features added for 1.6.1+ versions of Evergreen
> >>
> >>
> >> I wonder if we can remove the part "Third Party System Integration"
> >> for 3 reasons:
> >> 1) Some of this is covered by other sections in other parts of the
> >> documentation
> >> 2) No one volunteered for any of these chapters
> >> 3) I wonder if these sections are better covered in the context of
> >> the
> >> documentation (e.g. SIP2 in the context of setting up the SIP server
> >> in Administration or SuperCat in the context of Development which I
> >> would not want to duplicate and maintain in an entirely different
> >> part
> >> of the documentation)
> >> We can add this part for later versions of Evergreen documentation,
> >> but if we do not get volunteers to cover these chapters, then I vote
> >> we leave it out for now.
> >>
> >>
> >> Thanks,
> >> Robert
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> This E-mail contains privileged and confidential information intended
> >> only for the individual or entity named in the message.  If the
> >> reader
> >> of this message is not the intended recipient, or the agent
> >> responsible
> >> to deliver it to the intended recipient, you are hereby notified that
> >> any review, dissemination, distribution or copying of this
> >> communication
> >> is prohibited.  If this communication was received in error, please
> >> notify the sender by reply E-mail immediately, and delete and destroy
> >> the original message.
> >> _______________________________________________
> >> OPEN-ILS-DOCUMENTATION mailing list
> >> OPEN-ILS-DOCUMENTATION at list.georgialibraries.org
> >> http://list.georgialibraries.org/mailman/listinfo/open-ils-
> >> documentation
> >
> > --
> > Karen Collier
> > Public Services Librarian
> > Kent County Public Library
> > 408 High Street
> > Chestertown, MD 21620
> > 410-778-3636
> > www.kentcountylibrary.org
> > _______________________________________________
> > OPEN-ILS-DOCUMENTATION mailing list
> > OPEN-ILS-DOCUMENTATION at list.georgialibraries.org
> > http://list.georgialibraries.org/mailman/listinfo/open-ils-
> > documentation
>
> _______________________________________________
> OPEN-ILS-DOCUMENTATION mailing list
> OPEN-ILS-DOCUMENTATION at list.georgialibraries.org
> http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://list.georgialibraries.org/pipermail/open-ils-documentation/attachments/20100901/510560d2/attachment-0001.htm 


More information about the OPEN-ILS-DOCUMENTATION mailing list