[OPEN-ILS-DEV] particular areas of mystery from action item at last community meeting

[Soulliere, Robert]

Some documentation areas of mystery or areas needing enhancement:

Reports section needs improvement: – The Reports Task Force brought it to our attention that the section should be enhanced or improved. I replied by asking the  Reports Task Force if they could take a big role in the reports section by enhancing the documentation directly in the repository or proving some documentation in other formats given that the greatest amount of reports expertise is on the task  force. Moreover, some folks on the task force are also on the DIG.

Limits of vandelay (staff client importer): I was wondering if there are any general guidelines we can provide for how many records vandelay can import at one time to help users decide the size of MARC files to divide there records into or to decide when to use optional external scripted approaches. I understand that some of the vadelay limits are dictated by system capacity etc, but general guidelines would be great and require feedback from developers or very experienced users of the staff client importer.

Importing Authority Records: Again, providing guidelines for Vandelay would be nice here. Also, an up-to-date best method using an external approach would be great.

Permissions Descriptions: Jenny brought up the need for better permission descriptions in Evergreen in the documentation.  This is essential. I believe the starting point is to update the permission.perm_list database table in Evergreen to include more descriptions since some description fields are blank. Once the description fields are updated in the base Evergreen database, the DIG could develop a script to generate an up-to-date permissions list based on the table to add to the documentation.

There was also the case of missing permissions which were left out of the perm_list table but are applicable in 1.6.1? Could we get a complete list of these to add to the documentation? We will try to add the procedures to activate these.

Adding languages in 1.6.1: To encourage international growth for Evergreen, we need a step by step procedure for adding a new language which do not currently exist and define which languages are supportable (e.g. right-to-left issues language issues).

Adding formats in SuperCat in 1.6.1: Dan Scott wrote something up in his Coffee Code blog in January 2009:
http://coffeecode.net/archives/181-Adding-a-new-metadata-format-to-Evergreen-in-a-dozen-lines-of-code.html
Is this still applicable in 1.6.1?


Is that what we had in mind for particular areas of mystery or are these topics too broad?

Thanks,
Robert


Robert Soulliere, BA (Hons), MLIS
Systems Librarian
Mohawk College Library
robert.soulliere at mohawkcollege.ca
Telephone: 905 575 1212 x3936
Fax: 905 575 2011
________________________________________
From: open-ils-documentation-bounces at list.georgialibraries.org [open-ils-documentation-bounces at list.georgialibraries.org] On Behalf Of Karen Collier [kcollier at kent.lib.md.us]
Sent: November 23, 2010 3:43 PM
To: open-ils-documentation at list.georgialibraries.org
Subject: [OPEN-ILS-DOCUMENTATION] DIG Update, Volunteer Requests, & More

Hi Everybody,

I just got done giving an update on what DIG has been doing at the Evergreen Community IRC Meeting (IRC Log and Minutes to be posted at http://evergreen-ils.org/dokuwiki/doku.php?id=community:meetings).  By the way, the next Community Meeting is scheduled for Tuesday, December 21 at 2 PM EST for anyone who wants to mark their calendars to attend.

This update inspired me to do a much overdue update on the DIG list, so here goes.  (And thank you to Robert Soulliere who reminded me of much of this.)

The version 1.6 documentation is nearing completion (Yay!)  A big thank you to everyone who has contributed!  Most of the chapters in version 1.6 have been completed or assigned as shown in the outline linked to from our main wiki page:
http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:dig

BUT we need reviewers to read through the documentation at http://docs.evergreen-ils.org/ and provide feedback and corrections.  Please let me know if you're interested in helping out in this way.  You can submit bug reports on the documentation via Launchpad.  There are links throughout the documentation to do this.  Or submit feedback directly to this mailing list.

We're also looking for volunteers who have access to a 2.0 installation of Evergreen and would be interested in helping produce documentation covering features new and different to version 2.0.  Any format is okay.  Any takers?

During the discussion at today's Community Meeting, a member of the reports task force suggested that DIG may want to cover SQL reporting in our documentation.  Anyone interested in working on that topic?

Also from today's meeting, Dan Scott asked if there are any particular areas of mystery, where documentation writers might like to pick the brains of the people who are in the know.  He suggested that if we could come up with some topics we want to know more about, we could use some time at the next meeting to try to identify who could help us with those topics.  Sounds like a great idea to me!  Any suggestions on topics of this sort?

And last but not least (sorry for the lengthy email), who feels it's time to schedule another DIG meeting, and would be likely to attend?  It's been quite a while.  We could try to set up another GoToMeeting meeting like we've done before, or possibly consider an IRC chat format meeting.  Any thoughts?

Thanks,
Karen

--
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

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.