No subject

Fri Dec 14 15:48:43 EST 2012

re were the ones who relied more on hand on practice with Evergreen rather =
than reading the docs.. =C2=A0(ie, very few of my staff accessed the end us=
er docs when we migrated. =C2=A0I used them to create training lesson plans=
 and exercises, and they got comfortable practicing on our installation..).=

Thanks. 
 
Joe 
 
Joseph Knueven 
Director 
Germantown Public Library 
51 N. Plum St. 
Germantown, OH 45327 
<a href=3D"tel:937-855-4001" value=3D"+19378554001" target=3D"_blank">937-8=
55-4001</a> 
<a href=3D"mailto:knuevejo at oplin.org" target=3D"_blank">knuevejo at oplin.org<=
/a> 
 
On 8/1/2013 2:14 PM, James Keenan wrote: 
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I prefer having the information all in one place. When I was first learning=
 to install Evergreen (and before a bunch of doc work was done), it seemed =
pretty =C2=A0inconvenient for me to search around for various bits of knowl=
edge here and there in different docs on the same topic.

<br>
Jim<br>
<br>
Jim Keenan<br>
Library Applications Supervisor<br>
<a href=3D"mailto:jkeenan at cwmars.org" target=3D"_blank">jkeenan at cwmars.org<=
/a><br>
<a href=3D"tel:508-755-3323%20x23" value=3D"+15087553323" target=3D"_blank"=
>508-755-3323 x23</a><br>
=C2=A0 C/W MARS<br>
67 Millbrook St., Suite 201<br>
Worcester, MA 01606<br>
<br>
=EF=81=90 =C2=A0 Save a tree! Please don&#39;t print this e-mail unless it&=
#39;s really necessary.<br>
Currently reading Zen at War by Brian Victoria<br>
Just finished World War Z by Max Brooks<br>
<br>
-----Original Message-----<br>
From: <a href=3D"mailto:open-ils-documentation-bounces at list.georgialibrarie=
s.org" target=3D"_blank">open-ils-documentation-<u></u>bounces at list.georgia=
libraries.<u></u>org</a> [mailto:<a href=3D"mailto:open-ils-documentation-b=
ounces at list.georgialibraries.org" target=3D"_blank">open-ils-<u></u>documen=
tation-bounces at list.<u></u>georgialibraries.org</a>] On Behalf Of Kathy Lus=
sier<br>

Sent: Thursday, August 01, 2013 2:03 PM 
To: Documentation discussion for Evergreen software 
Subject: [OPEN-ILS-DOCUMENTATION] Including technical information in end-us=
er docs 
 
Hi all, 
 
This question came up during some recent discussions I had with Equinox reg=
arding some documentation they were doing for one of our development projec=
ts, and it seemed like a topic that DIG might want to discuss. It relates t=
o how much technical documentation should be included in the end-user docs =
that are created for a feature in Evergreen. In this case, it is a new feat=
ure, but I suppose the question relates to any functionality we want to doc=
ument for Evergreen.

<br>
We&#39;ve seen documentation come in various forms when a new feature is<br=
>
introduced:<br>
<br>
* The release notes include a description of the new feature and, ideally, =
also include any new settings or permissions associated with the feature.<b=
r>
* The docs include information for end users to use the new feature. It als=
o sometimes contains information on settings and permissions.<br>
* There is also a TechRef directory that is available with the code that co=
ntains more technical information on some features.<br>
<br>
The question is how much technical information should be included in those =
end-user docs?<br>
<br>
My personal opinion is that any information in the Release Notes should als=
o be included in the docs because there are many people who probably never =
look at the release notes. However, should end-user docs include informatio=
n on library settings and permissions that are usually configured by the ad=
min, not the end-user? Should a separate technical details section be inclu=
ded in the end-user docs?<br>

<br>
What structure do you think would work best for the community?<br>
<br>
Kathy<br>
<br>
--<br>
Kathy Lussier<br>
Project Coordinator<br>
Massachusetts Library Network Cooperative<br>
<a href=3D"tel:%28508%29%20343-0128" value=3D"+15083430128" target=3D"_blan=
k">(508) 343-0128</a><br>
<a href=3D"mailto:klussier at masslnc.org" target=3D"_blank">klussier at masslnc.=
org</a><br>
Twitter: <a href=3D"http://www.twitter.com/kmlussier" target=3D"_blank">htt=
p://www.twitter.com/<u></u>kmlussier</a><br>
<br>
______________________________<u></u>_________________<br>
OPEN-ILS-DOCUMENTATION mailing list<br>
<a href=3D"mailto:OPEN-ILS-DOCUMENTATION at list.georgialibraries.org" target=
=3D"_blank">OPEN-ILS-DOCUMENTATION at list.<u></u>georgialibraries.org</a><br>
<a href=3D"http://list.georgialibraries.org/mailman/listinfo/open-ils-docum=
entation" target=3D"_blank">http://list.georgialibraries.<u></u>org/mailman=
/listinfo/open-ils-<u></u>documentation</a><br>
______________________________<u></u>_________________<br>
OPEN-ILS-DOCUMENTATION mailing list<br>
<a href=3D"mailto:OPEN-ILS-DOCUMENTATION at list.georgialibraries.org" target=
=3D"_blank">OPEN-ILS-DOCUMENTATION at list.<u></u>georgialibraries.org</a><br>
<a href=3D"http://list.georgialibraries.org/mailman/listinfo/open-ils-docum=
entation" target=3D"_blank">http://list.georgialibraries.<u></u>org/mailman=
/listinfo/open-ils-<u></u>documentation</a><br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
OPEN-ILS-DOCUMENTATION mailing list<br>
<a href=3D"mailto:OPEN-ILS-DOCUMENTATION at list.georgialibraries.org" target=
=3D"_blank">OPEN-ILS-DOCUMENTATION at list.<u></u>georgialibraries.org</a><br>
<a href=3D"http://list.georgialibraries.org/mailman/listinfo/open-ils-docum=
entation" target=3D"_blank">http://list.georgialibraries.<u></u>org/mailman=
/listinfo/open-ils-<u></u>documentation</a><br>
</blockquote></div><br><br clear=3D"all"><br>-- <br>Ruth Frasur<br><br><br>

--001a1133046c0bd3e704e2e763f3--