Evergreen ILS

Open Source Library Software

Search Results for: dokuwiki/listserv.php

Evergreen Documentation Interest Group: Can you DIG it?

This is a summary that was posted to the three Evergreen discussion lists (general, documentation, and development) about the exciting momentum gathering around Evergreen documentation.

The key take-away: the Evergreen community now has a Documentation Interest Group!  There will be an online meeting 3 p.m. Eastern Time Wednesday, June 10, to discuss initial roles and tasks — if you’re interested, sign up.

Most day-to-day discussions about the Evergreen documentation project will take place on the Evergreen documentation list (though news of note may be posted to this blog and other lists on occasion). To subscribe to open-ils-documentation (or other Evergreen lists), see http://evergreen-ils.org/listserv.php

More about the DIG Project
On Wednesday, May 20, 2009, at the Evergreen International Conference, close to two dozen members of the Evergreen community participated in a documentation planning discussion.

Following a presentation about documentation (see notes below), the group took the following actions and (unanimously) made the following commitments:

* Established an Evergreen Documentation Interest Group, aka DIG, or even, the DIGgers
* Agreed to meet regularly to plan and implement the Evergreen documentation project
* Agreed that core Evergreen documentation should be based on one single-source, standards-based, open format
* Agreed that DocBook was the format of choice for Evergreen documentation
* Agreed that community members could contribute documentation in any format, and the DIG would convert to DocBook format as required
* Agreed that the initial organizing meetings should clarify roles and tasks
* Agreed that Karen Schneider and Paul Weiss would lead this project at this point in time

Some of the earliest activities for the DIG will include establishing a timeline and a regular meeting schedule, and identifying initial tasks for project participants and recruiting for each role. Some of the preliminary groundwork for the project, once volunteers have committed to specific areas, will include identifying a core DocBook subset of tags for Evergreen documentation, writing an Evergreen style (markup) guide, developing heavily-annotated model templates, and providing toolset advice.

Documentation News of Note

The evergreen-ils.org website has been updated so that the Documentation list stands on its own, rather than being listed under Development. (See http://evergreen-ils.org/listserv.php )

Slides from the May 20 discussion are also on Slideshare. These slides spell out in greater detail why (and how) the Evergreen community is moving in this direction.  Questions? Post away!

http://www.slideshare.net/evergreenils/evergreen-docs-planning-session-2009 (full set)

http://www.slideshare.net/evergreenils/evergreen-documentation-lightning-talk (short set)

Community Spotlight: Irene Patrick

The Evergreen Outreach Committee is pleased to announce that the Community Spotlight for the 4th quarter of 2021 is Irene Patrick. Irene is the Electronic Resources Librarian at the State Library of North Carolina. In that role she oversees electronic resources for the state and manages the Evergreen ILS for North Carolina’s Government and Heritage Library (GHL). 

Irene has extensive experience  in library automation and ILS management, beginning with the State Library’s implementation of Dynix in 1989. Her background in acquisitions and serials has informed many of her community interests. Irene is a regular presence at Evergreen Serials Interest Group meetings. While the Serials module sometimes doesn’t get the attention of other modules in Evergreen, Irene maintains her strong interest in Serials and is often advocating for Serials end users.

In 2017, Irene led the migration of GHL from a standalone Voyager system to the NC Cardinal Evergreen Consortium. The GHL is a research library, and NC Cardinal is a consortium of public libraries. This involved a lot of complicated work to get records and policies in place for the migration.

“We’re the proverbial square peg in the round hole,” Irene says. “But the migration was successful, and we have been pleased with the many enhancements that have come to Evergreen in the years since.”

She recommends that new community members join the listservs, and find an interest group to join. “Pick [an interest group] that matches your interests, and attend the meetings to learn about the modules and share problems you face,” she says.

Irene also participates with the Cataloging Interest Group, and often chimes in on listserv questions to help share her knowledge with the larger Evergreen community. Irene contributes to discussions that affect front line staff and their use of Evergreen, both on the listserv as well as in the community bug portal Launchpad.

Irene also recommends participating in the annual Evergreen conference. “I miss the in-person conferences, where you could get to know other members of the community,” she notes. “But the online conferences the past couple of years have still provided opportunities for learning and limited ways to meet people.” At the conferences, Irene likes to participate in community brainstorming sessions to share ideas for Evergreen improvements.

When she’s not working, Irene enjoys reading, gardening, and travelling to new places (though the latter has been curtailed the past couple years). She’s also a lifelong Star Trek fan and enjoys keeping up with the new streaming series.

—

Do you know someone in the community who deserves a bit of extra recognition? Please use this form to submit your nominations. We ask for your email in case we have any questions, but all nominations will be kept confidential. Any questions can be directed to the Outreach Committee at evergreen-outreach@list.evergreen-ils.org.

Evergreen Documentation Licensing Terms

The Evergreen Documentation Interest Group (DIG) has voted to accept the following proposals for Evergreen Documentation Licensing. The vote took place December 21, 2009 – January 4, 2010 on the Documentation Interest Group Mailing List. There were 18 yes votes and 0 no votes, for a unanimous decision.

Since these licensing terms affect the entire Evergreen community, and particularly anyone who has contributed to the Documentation Wiki, we wanted to keep everyone informed. Please take a moment to read the licensing terms below (also available on the wiki at http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:documentation_licensing_terms). If you have previously contributed documentation to the Documentation Wiki and do NOT want your contributions to be licensed under these terms, please contact the DIG facilitators or the DIG mailing list and let us know that by Friday, January 29th.

I am crossposting this to several Evergreen related mailing lists and blogs, as well as sending an email about this to anyone with a DokuWiki account, so I apologize for duplicate messages. If you have any questions, feel free to contact the DIG facilitators at docs@evergreen-ils.org.

I hope you’ll agree that this is a positive step forward for the Evergreen community. And, if you find some free time, that you might consider joining the Documentation Interest Group in producing some community-wide documentation.

Thanks,
Karen Collier
Documentation Interest Group Co-Facilitator

1 – Official Evergreen Documentation produced by the Documentation Interest Group should be licensed under the Creative Commons Attribution Share-Alike 3.0 License (http://creativecommons.org/licenses/by-sa/3.0/).

2 – Any code included in the official documentation produced by the Documentation Interest Group should also be made available under the GNU GPL (http://www.gnu.org/licenses/gpl.html).

3 – Official Evergreen Documentation may be made available under another copy-left (http://www.fsf.org/licensing/essays/copyleft.html) open source (http://www.opensource.org/docs/osd) license in the future with a majority vote on the Evergreen Documentation List (open-ils-documentation@list.georgialibraries.org) or comparable indication of the Evergreen community’s wishes.

4 – These same licensing terms should be applied to the Documentation Wiki. Past contributors to the Documentation Wiki should be notified by emails sent to Evergreen community mailing lists and to the email address associated with their docuwiki account of the new licensing terms and given a reasonable amount of time to request that their contributions not be included under those licensing terms.

5 – By submitting documentation to the Documentation wiki or to the Evergreen Documentation List after licensing terms have been decided and publicized, contributors indicate that they (a) agree to these licensing terms, and (b) to the best of their knowledge have the right to do so through copyright ownership, permission from the copyright owner(s), and/or the licensing terms of any documents that were modified or incorporated into their submission.