Evergreen DokuWiki - evergreen-docs

2.4_needs

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:57+00:00

Evergreen 2.4 Documentation Needs Below are new 2.4 features that need documentation. If you volunteer to create documentation, add your name in blue. Additional information about each of these features may be available in the 2.4 release notes. Acquisitions * Acquisitions Inline Item Detail View -

2.5_needs

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:57+00:00

Evergreen 2.5 Documentation Needs Documentation needs based on the 2.5 Release Notes Copy the HTML code below to update the status of an item: * Assign yourself: [your name] () * Add a status: COMPLETE!

2.6_needs

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:57+00:00

Evergreen 2.6 Documentation Needs Documentation needs based on the 2.6 Release Notes. Copy the HTML code below to update the status of an item: * Assign yourself: [your name] () * Add a status: COMPLETE!

2.7_needs

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:57+00:00

Evergreen 2.7 Documentation Needs (deprecated, see 2.8_needs) Documentation needs based on the 2.7 Release Notes. Copy the HTML code below to update the status of an item: * Assign yourself: [your name] () *

2.8_needs

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:58+00:00

Evergreen 2.8 Documentation Needs (deprecated, see 2.9_needs) Documentation needs based on the Release Notes entries that were submitted with new features during the 2.8 release cycle. Copy the HTML code below to update the status of an item: * Assign yourself:

2.9_needs

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:57+00:00

Evergreen 2.9 Documentation Needs (deprecated, see 2.10_needs) Documentation needs based on the Release Notes entries that were submitted with new features during the 2.9 release cycle. Copy the HTML code below to update the status of an item: * Assign yourself: [your name]

2.10_needs

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:58+00:00

Evergreen 2.10 Documentation Needs (deprecated, see 2.11_needs) Documentation needs based on the Release Notes entries that were submitted with new features during the 2.10 release cycle as well as Launchpad bugs targeted to 2.10. Also, based on the Release notes for 2.9.2 Copy the HTML code below to update the status of an item:

2.11_needs

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:58+00:00

Evergreen 2.11 Documentation Needs (deprecated, see 2.12_needs) Documentation needs based on the Release Notes entries that were submitted with new features during the 2.11 release cycle as well as Launchpad bugs targeted to 2.11. Also, based on the Release notes for 2.10 Copy the HTML code below to update the status of an item:

2.12_needs

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:58+00:00

Evergreen 2.12 Documentation Needs (deprecated, see Evergreen 3.0 Documentation Needs) Documentation needs based on the Release Notes entries that were submitted with new features during the 2.12 release cycle as well as Launchpad bugs targeted to 2.12. Also, based on earlier release notes. Copy the HTML code below to update the status of an item:

3.0_needs

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:58+00:00

Evergreen 3.0 Documentation Needs (deprecated, see Evergreen 3.1 Documentation Needs) Documentation needs based on the Release Notes entries that were submitted with new features during the 3.0 release cycle as well as Launchpad bugs targeted to 3.0. Copy the HTML code below to update the status of an item:

adding_documentation

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:58+00:00

Adding Local Documentation to the Official Documentation * Add proposed or in process documentation to the outline in blue. * Complete your documentation and makes the documentation available to appropriate open-ils mailing lists and (module) content coordinator. (The contact information for coordinators can be found

adding_indexterms

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:58+00:00

Index features in the Evergreen Manual Each manual has an index, based on the contents of the manual. Here's an example from the Acquisitions manual: What To Add The docs can be searched by keyword, so we don't need to index every concept. Our index is most useful for words or spellings that don't exist within the text. This might be synonyms, aliases, abbreviations, acronyms, etc. Some examples:

deliver_orientation_basic_training

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:58+00:00

These links and suggested readings provide general to specific information about XML, DocBook, and their use in libraries and software documentation. We hope you find them useful and welcome your recommendations. Email Shannon Dineen, Sitka Lead Trainer and Help Desk Coordinator, at sdineen@sitka.bclibraries.ca

dig_activities

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:58+00:00

Evergreen Documentation Interest Group Activities, Goals, and Timelines Initial 3-month timeline Proposed goals, objectives, and milestones, annotated Resources about documentation Initial goals These are the tasks we committed to for the summer of 2009: * determine a meeting schedule * establish an initial timeline * write a scope/purpose statement

dig_hack-a-way

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:58+00:00

DIG hack-a-way 2014 - Agenda/Goal Ideas Date: Friday, September 12, 2014 * Focus on new 2.7 features * DIG hack-a-way 2013 - Agenda/Goal Ideas Date: Friday, November 15, 2013 Agenda/Ideas * Docs Bitesize Bugs (helpful for newcomers to practice on)

dig_hackfest_20170502

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:57+00:00

DIG Hackfest Agenda - Tuesday, May 2, 2017 This is a day-long event (come and go as you need) intended to focus on documentation needs for the current version of Evergreen (2.12) and the major revisions necessary for the upcoming release of the web client (3.0). All are encouraged to attend. DIG members will be available to answer questions. For updates, notifications, and discussion please sign up for the

dig_hackfest

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:57+00:00

DIG Conference Hackfest Project Ideas - Evergreen Conference 2014 * Before hack-fest * AsciiDoc "question and answer" online session? (Yamil) * Hack fest * Plan introduction meeting * break off into groups (training vs working groups)

dig_meeting

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:57+00:00

DIG Conference Meeting Agenda Ideas - Evergreen Conference 2014 DIG Conference Meeting Agenda Ideas - Evergreen Conference 2013 * AsciiDoc training - taught by Yamil (proposed by Yamil) * Election of DIG facilitator (proposed by Yamil) * Idea sharing (proposed by Yamil)

dig_meetings

Anonymous (anonymous@undisclosed.example.com) — 2026-04-02T17:03:19+00:00

Documentation Interest Group Meetings Next meetings Meetings are held via video conference. Current and future DIG participants are encouraged to attend, and any interested members of the Evergreen Community are welcome as well. For updates, notifications, and discussions please sign up for the

dig_participants

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:58+00:00

The volunteers for these initial tasks are also listed in the timeline.

dig_participation

Anonymous (anonymous@undisclosed.example.com) — 2025-06-05T16:18:06+00:00

How to Participate in the Evergreen Documentation Interest Group Contributing to documentation is an excellent way to support Evergreen, even if you are new to documentation. In fact, beginners often have a distinct advantage over the experts, more easily spotting the places where documentation is lacking or where it is unclear.

dig_proof_of_concept

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:58+00:00

DIG Proof of Concept in DocBook Tina Ji, Karen Collier, Jeremy Buhler Update The proof of concept below was superseded by Sitka's published Evergreen documentation, available under a Creative Commons license in HTML and PDF: * HTML version * PDF version For more information about Sitka's DocBook including a zip file with source xml see the following messages to the OPEN-ILS-DOCUMENTATION list:

dig_style_guide

Anonymous (anonymous@undisclosed.example.com) — 2025-11-06T19:50:51+00:00

DIG AsciiDoc Style Guide New AsciiDoc Style Changes for Antora As of the 3.6 release of Evergreen, we are using Antora as a new "framework" for the Evergreen docs. Antora requires some changes to the directory structure, and it reveals some AsciiDoc syntax errors (since it uses the more strict AsciiDoctor for converting to

dig_terms_of_reference

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:58+00:00

Evergreen Documentation Interest Group Terms of Reference Mission Statement The Evergreen Documentation Interest Group (DIG) plans, facilitates, produces, manages, and provides access to online documentation about the Evergreen ILS. Scope * Administers a framework for documentation, inclusive of timelines, a style guide, software tools, and DIG member training and support

dig_test

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:58+00:00

page for testing meeting notes,

dig_toolset

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:58+00:00

Initial DocBook Tools Jeremy Buhler, Karen Schneider, Tina Ji Creating valid DocBook XML files: authoring tools Basically any text processor that can save plain text files can be used as a DocBook authoring tool. Professional XML editors will help you to write error-free XML documents, validate your XML against a DTD or a schema, and force you to stick to a valid XML structure.

dig--scope

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:58+00:00

Evergreen Documentation Interest Group Terms of Reference Mission Statement The Evergreen Documentation Interest Group (DIG) plans, facilitates, produces, manages, and provides access to online documentation about Evergreen. Scope * Administers a framework for documentation, inclusive of timelines, a style guide, software tools, and DIG member training and support

digparticipants

Anonymous (anonymous@undisclosed.example.com) — 2024-04-25T20:08:39+00:00

DIG Roles (Draft) Facilitator ( Debbie Luchenbill ) * Provide update for DIG activities at Evergreen community meetings and other community events. * Facilitate discussion on DIG email list * Facilitate DIG meetings * Coordinate training for DIG members

digresources

Anonymous (anonymous@undisclosed.example.com) — 2025-11-11T20:20:39+00:00

Documentation Resources: General * basic concepts * document development life cycle * documentation issues in open source (archived) * evaluation Documentation Resources: Technology DIG Test Server Community demo servers: These are community Evergreen servers available for testing procedures and learning. Documentation repository * Evergreen git repository * Get a free github account Contribution tools

digtest

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:58+00:00

Evergreen Documentation Interest Group DIG was established in May 2009 to help move Evergreen toward a single-source, standards-based documentation format. The facilitators are Karen Schneider (Equinox Software) and Paul Weiss (Consultant/Sage Library System).

docs_hackfest_eic18_20180430-agenda

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:58+00:00

Documentation Hackfest Agenda - Monday, April 30, 2018 Meeting Room 103, 2018 Evergreen International Conference, St. Charles, Missouri This is a day-long event (come and go as you need) intended to focus on documentation needs for the current version of Evergreen.

docsagenda061009

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:58+00:00

moved to 20090610-agenda

documentation_licensing_terms

Anonymous (anonymous@undisclosed.example.com) — 2025-06-05T15:46:06+00:00

Documentation Licensing Terms Between December 21, 2009 and January 4, 2010 the Evergreen Documentation Interest Group unanimously voted to accept the following licensing terms for official Evergreen Documentation. 1 - Official Evergreen Documentation produced by the Documentation Interest Group should be licensed under the Creative Commons Attribution Share-Alike 3.0 License (

documentation_needs

Anonymous (anonymous@undisclosed.example.com) — 2026-02-05T19:42:28+00:00

Evergreen Documentation Needs High level workflow for documenting new EG features 1. Choose a Task 2. Read Release Notes 3. Update the Docs - Look at the task list below and add your name next to a task - Need a wiki account? Just ask. - Review the release notes entry for the feature (and/or the Launchpad bug)

drupal_web_portal

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:58+00:00

Drupal Web Portal * site map - The obvious 1st step, what is here now? * About us * FAQs - wiki * Documentation - wiki * Blog - wordpress * Chat - IRC * Mailing Lists - mailman * Evergreen Blogs - member blogs? * Downloads - source repository

evergreen_documentation_project

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:58+00:00

moved to dig

existing_docs_survey

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:57+00:00

Survey of existing documentation Existing documentation on the web Source Author/contact info Licensed? (copyright,CC, GPL, ?) Date written/revised Version (1.2.3.1, 1.4, unknown?) Format (Word doc, PDF, wiki, text, video (format)

github-workflow

Anonymous (anonymous@undisclosed.example.com) — 2024-07-10T12:03:23+00:00

Docs GitHub Workflow When someone submits a change via GitHub, an Evergreen developer should follow these steps to review it: Reviewing the pull request * Log in to Github * Open the pull request in the Github web interface. * Open the Files Changed tab * Make sure the asciidoc changes look good

glossary

Anonymous (anonymous@undisclosed.example.com) — 2023-08-21T16:59:09+00:00

Glossary THIS PAGE IS DEPRECATED. See the glossary.adoc file in the documentation repository. Please send edits to the DIG email list, or submit then via GitHub. * Main version: glossary.adoc * Evergreen 3.4: glossary.adoc

how-to-contribute-documentation

Anonymous (anonymous@undisclosed.example.com) — 2025-07-25T19:46:14+00:00

How to Contribute Documentation to the Repository First of all, you are welcome to email the Documentation Listserv () with problems you find in the documentation. However, we welcome you to participate in the process of improving things. Below are various ways you can contribute your time and skills.

lp_docs

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:58+00:00

Submitting Documentation Bugs in Launchpad (DRAFT) The Documentation Interest Group (DIG) is exploring the use of Launchpad to track documentation needs for the Evergreen project. Please follow the below guidelines for Launchpad documentation bugs.

newwebsitesurvery

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:58+00:00

Collection of Responses to Analyze EG Website Migration to Drupal Why replace the current evergren-ils.org platform with Drupal? Mark Jordan - Drupal offers a solid platform for managing websites that are maintained by multiple people, that require integration with external data sources, and that need to be flexible enough to respond to changes in requirements in the future. Karen Schneider - Right now the website is a handful of static

outline

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:58+00:00

Book of Evergreen 1.6: Outline and Assignments Below is a working outline for organizing the Documentation Interest Group's Book of Evergreen into Parts, Chapters, Sections, and Sections within Sections as deeply as needed. If you wish to make changes to the outline at the Part or Chapter level or that affect an area others are working on, please discuss your proposed changes on the

quickstarts

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:58+00:00

Evergreen Quick Starts This project was discussed at the 2019 Northwest Evergreen Users Symposium and Evergreen International Conference Documentation Hackfest. Andrea Buntz Neiman thought of the name! The goal is to meet the needs of volunteers, student workers, and others without a library background who find themselves using Evergreen. Each quickstart consists of a jargon-free video and an accompanying one-page reference sheet. Ideally, we would have a quickstart for each of the most com…

release_notes_process

Anonymous (anonymous@undisclosed.example.com) — 2024-02-12T20:55:42+00:00

Release Notes Process for DIG Release Coordinator Major Release Notes => See also the release notes section of the release process page Preparing for the release Before the beta is cut, periodically review Launchpad Wishlist bugs with a pullrequest tag to see if they have the necessary release notes. If they don't, add the needsreleasenotes

reorg

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:58+00:00

Docs Reorganization Project This page provides a place to discuss how to organize the official documentation. Please add ideas, suggest a new approach, or create a new structure by copying the Table of Contents from below. Share your changes via your own wiki page, or send a text file (or Word Doc, etc.) to the DIG mailing list (

test-dig-frontpage

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:58+00:00

Evergreen Documentation Interest Group (DIG) The Evergreen DIG was established in May 2009 at the first Evergreen International Conference, where members of the Evergreen community committed to developing single-source, standards-based documentation for Evergreen. Since then, the DIG has been actively working toward that goal.

todo

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:58+00:00

All Outstanding Documentation Needs Style Guide * Remember to follow (and improve) the DIG Style Guide Bugs/Minor Problems in the Documentation * Bitesize (simple) documentation bugs on Launchpad * All documentation bugs on Launchpad New Features Needing Documentation * Evergreen Documentation Needs (includes remaining issues from previous versions)

web_staff_client_workflow_and_label_changes

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:57+00:00

Web Staff Client Workflow and Label Changes Copy the HTML code below to update the status of an item: * Assign yourself: [your name] () * Add a status: COMPLETE!

webclient

Anonymous (anonymous@undisclosed.example.com) — 2023-04-27T19:38:57+00:00

Web Staff Client Documentation Project Priorities * Focus Area: * Focus Area: How to Help * Edit on GitHub * Write documentation in any format! We prefer AsciiDoc, but we can convert whatever you send us. * If you want more guidance, check out our documentation style guide * Take updated screenshots of the demo web client (see login details below)