[OPEN-ILS-DOCUMENTATION] DIG roles follow up

[Soulliere, Robert]

Hi All,

At the DIG meeting we introduced a few potential roles for DIG members to volunteer for. Below is the overview of the roles we discussed. I would like to open these up to DIG members and see if anyone is interested in any of these.

First, it is important to clarify a few things:

1) These roles are coordinating, communicating and possibly research roles and not necessarily writing roles.

2) These do not replace the idea of having individuals sign up for writing specific sections of the documentation. If you just want to write a specific section, please continue to use the outlines for signing up to write, edit, or review specific sections of the documentation. Add your names to outlines here or send the titles or sections you will work on to this list and we will add your names for you:
http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:outline
http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs_2.0:outline
- If you have access to 1.6 and 2.0 and feel comfortable, you can sign up for the topic for both documents. In fact, it is probably advisable given that content from 1.6 can be pulled into 2.0 with minimal tweaking.

3) The Content Coordinator roles do not require DocBook or any other specialized technical skills. The key skills required are basically an idea of how the documentation should be, how it should be organized as well as some ideas of how to find existing documentation already written.

4) The idea of the Content Coordinator roles is not to give a lot of work to a few people but to coordinate efforts to reduce redundancy in writing through better communication of groups working on specific parts of the documentation. One important aspect of this roles is to "update the DIG at the DIG meeting". This will allow us to know how things are progressing and perhaps realign resources to fill in glaring gaps in the documentation.

5) The idea behind the way the coordinator roles is based on assumed  comfort levels We can divide these into smaller groups but just remember that one of the objectives of these roles is to coordinate efforts not write the entire part of the documentation. This may also be determined the the # of active DIG members we have.

Public OPAC/staff tasks Content Coordinator could be someone who understand the daily tasks of the system (cataloging, circ, OPAC searching etc...) and understand the needs of those users in regards to documentation.

Administration/Development Content Coordinator could be a system administrator or Developer who knows the inner workings of the system, has worked on the back-end and can work with System Admin and Developer groups.

Reports Coordinator would be a perfect fit for someone on the the Reports Task Force who discuss these issues at their meetings.

DocBook Conversion Coordinator would require more specialized technical skills. It would be the person who the content coordinators contact if they have content but need it converted to DocBook.

Style Coordinator might be even more specialized and requires experience with style sheets. (This could be combined with the DocBook Conversion Coordinator role if needed).


Public OPAC/staff tasks Content Coordinator (Should be someone experienced with end patron needs and common staff client tasks)
role:
 - locate existing content for section under their area
- help coordinate writing where needed. Ensure that there is minimal duplication of work.
- update the DIG at the DIG meeting regarding progress made on  "public OPAC", "Staff Tasks" and "Appendices" parts of the documentation

Administration/Development Content Coordinator (Should be someone experienced in Evergreen Administration and/or Development)
role:
 - locate existing content for section under their area
- help coordinate writing where needed. Ensure that there is minimal duplication of work.
- update the DIG at the DIG meeting regarding progress made on  public "Development", "Administration" and "3rd Party Integration" parts of the documentation

Reports Coordinator (Should be a member of the Evergreen Reports Task Force)
role:
 - locate existing content for section under their area
- help coordinate writing where needed. Ensure that there is minimal duplication of work.
- update the DIG at the DIG meeting regarding progress made on  Reports part of the document

DocBook Conversion Coordinator (experience with DocBook XML)
role:
- Convert documentation to DocBook
- recruit and train others for the conversion team

Style Coordinator (experience with DocBook style sheets and HTML/PDF presentation issues)
- Update DocBook HTML and PDF style sheets as needed for improved presentation.
-Troubleshoot stylesheet issues.
-Enhance presentation of documentation


Robert Soulliere, BA (Hons), MLIS
Systems Librarian
Mohawk College Library
robert.soulliere at mohawkcollege.ca
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.