Evergreen ILS

Open Source Library Software

Search Results for: downloads/listserv.php/dokuwiki/doku.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)

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.

Evergreen Release 3.6 is off to a Great Start!

Release 3.6 is taking shape quickly in an accelerated timetable

Lots of great features have already been added to the Release 3.6 roadmap. This is the first in a series of biweekly updates as we progress quickly to Evergreen 3.6 which will be released in October.

Release info:

https://wiki.evergreen-ils.org/doku.php?id=faqs:evergreen_roadmap#release_36_october_2020

3.6 Roadmap Highlights:

Angular Acquisitions Rewrite

The Acquisitions Search interface has been rewritten in Angular, replacing the old dojo screens for enhanced functionality and usability.
This development was sponsored by ECDI, the Evergreen Community Development Initiative.

Course Materials Module

On track for Release 3.6 is a built in Course Materials Module, fully and smoothly integrated into Evergreen. In the past, Evergreen libraries have relied on solutions like creative use of bookbags or the separately installed and maintained Syrup application to manage course reserves. Having a fully functional course materials module, smoothly integrated into Evergreen will be an essential tool for academic libraries. Public libraries will also have the opportunity to explore the integrated functionality for Summer Reading materials or Book Groups.
This development is sponsored by Treasure Valley Community College, Linn-Benton Community College, and NOBLE.

Curbside Pickup

Already in use at some libraries, the Curbside Pickup development provides a workflow for appointment based hold pickup. Once patrons are notified that their holds are ready, Curbside Pickup can manage pickup appointments and provide streamlined checkout of held items.
This development is sponsored by PaILS.

Angular Staff Catalog Becoming Default

The experimental Angular staff catalog is slated to become the default in 3.6 for staff-side catalog search. The former AngularJS staff catalog will remain available, but will be marked as the “traditional” staff catalog.

Staff Catalog

Bootstrap OPAC Redesign

The Bootstrap OPAC redesign spearheaded by Chris Burton of the Niagara Falls Public Library is on course to be in 3.6 as an optional public catalog skin parallel to the current TPAC skin. During the development meeting on August 4th, there was a discussion about when to full switch to the new design. The current proposal on the table is to make the Bootstrap skin become the default in 3.7 and deprecate the TPAC skin. When and if to remove the TPAC skin outright remains an open question.

Opac Redesign

Recent Big Changes and Commits

The patches for bug 1864371 were pushed recently. They bump up the version of Angular used by the web staff client from 8 to 10. Bill Erickson supplied the following instructions for developers to update their Evergreen environments:

git pull
# change the OS target as needed
sudo make -f ./Open-ILS/src/extras/Makefile.install ubuntu-bionic-developer
cd Open-ILS/src/eg2/
rm -rf node_modules
npm install
ng build --watch # etc.

How you can help

If you have a feature you’ve been meaning to contribute, now is the time! If your contribution can be ready for review by mid September, there’s still time to add it to the Roadmap.

https://wiki.evergreen-ils.org/doku.php?id=faqs:evergreen_roadmap:3.6

If you are a daily user of Evergreen, get familiar with the feature requests and bug reports on Launchpad. Subscribe to bugs that affect you and you’ll receive progress updates. Add your name to the affected users list on bugs that affect your workflow. Add Comments. Activity on a Launchpad bug increases its “Heat”, which tells the community how important it is to Evergreen users.

Upcoming Events

Feedback Fest week August 17th – August 21st

Feedback Fest focuses attention on Launchpad bugs with code waiting to be tested. The goal is to review every outstanding pull request on Launchpad to help establish a clear path forward, tagging, commenting and rebasing code as necessary.

We want to hear from you!

If you have thoughts, questions, or suggestions you’d like to share, feel free to reach out to the Release team by way of the Evergreen Developer’s List.

The 3.6 Release Team:
Galen Charleton
Jason Boyer
Terran McCanna
Michele Morgan