I'm no acq specialist, but know the basics and have been working with our 
office's acq specialist to learn more.  She and I are willing to work on 
merging the existing documentation in to one chapter.  Others would be welcome 
to join us in this work!

Jenny

Jennifer Turner | PALS, A Program of the Minnesota State Colleges and 
Universities | 507-389-2000



-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of 
Soulliere, Robert
Sent: Friday, May 13, 2011 9:03 AM
To: [email protected]
Subject: [OPEN-ILS-DOCUMENTATION] acquisitions chapters

Hi,

I wonder if it would be possible for acquisitions specialists to form a 
subgroup or have a discussion to merge the various existing acquisitions 
chapters found in the 2.0 documentation into one unified chapter?

See: http://docs.evergreen-ils.org/2.0/draft/html/

We added the acquisitions chapters to the documentation "as is" with the hope 
that they would be merged by those experienced or interested in the 
acquisitions process.

Thanks,
Robert


Robert Soulliere, BA (Hons), MLIS
Systems Librarian
Mohawk College Library
[email protected]
Telephone: 905 575 1212 x3936
Fax: 905 575 2011

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
[email protected]
http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation
_______________________________________________
OPEN-ILS-DOCUMENTATION mailing list
[email protected]
http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation

Reply via email to