Sarah, Thanks for volunteering. I'll try to contact you and the other volunteers for organizing documentation soon, maybe today or Monday.
If you already know some HTML, I think you're right that that'll be a huge step up in picking up Docbook and that the templates will probably be enough to get you started, once we get those put together (any volunteers for putting together some templates?). On the other hand, if you want to contribute in Word that's cool too. I just hope we have enough volunteers to work on converting to Docbook. :) As for who to contact to have specific features clarified, some options include the other mailing lists (http://evergreen-ils.org/listserv.php), either general or development depending on the question, and the IRC channel (http://evergreen-ils.org/irc.php) if you're comfortable with that mode of communication. Does anyone else have any other suggestions? Thanks, Karen ----- [email protected] wrote: > Hello, > I would be willing to help with planning how the staff user > documentation should be organized. > > I also wanted to say that Indiana has moved to 1.6, and I've been > working > on our local cataloging documentation. I've done the chapter on > Z39.50 > (chapter 12), which is posted to the Indiana State Library website, so > if > anyone wants to take a look, I'd welcome feedback. It's linked on the > documentation scan page in the DIG wiki. I expect to get most of our > cataloging manual updated in the next month. > > When I talked about doing cataloging documentation for 1.6, Karen > Schneider suggested I just keep doing these in Word and we'd have > someone > convert it to DocBook. I could take the Word file I have and > generalize it > so that it's not so Indiana specific, or that could be done when it's > converted to DocBook. > > I haven't used DocBook before, and I don't currently have any software > for > it. I'd be willing to learn it, but frankly I don't really have time > right > now. I do think if someone got basic template documents set up, I > could > probably write documentation in DocBook. I can code in HTML, so I > don't > think it would be too much of a learning curve. > > Finally, when I have questions about the new features I'm trying to > document, where should I direct those? For instance, what's the > purpose > of this query function in Record Buckets? I've played around with it > a > little, but I haven't thought of a way it would be useful to me > personally. I'm assuming someone must have wanted it to be written, > so > they must have had a purpose in mind. > > Sarah > > > Sarah Childs > Senior Cataloger > Hussey-Mayfield Memorial Public Library > Zionsville, Indiana > 317-873-3149 ext. 13330 > > > _______________________________________________ > OPEN-ILS-DOCUMENTATION mailing list > [email protected] > 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 _______________________________________________ OPEN-ILS-DOCUMENTATION mailing list [email protected] http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation
