Table of Contents

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:

TIPS

Check Sitka's documentation, especially when documenting older features
Regular Manual and Acquisitions Manual

High level workflow for documenting new EG features

These are the high-level steps we take to document new features:

  1. Look at the new feature docs to do list (this page) and sign yourself up for documenting a new feature
    1. You will need a EG community wiki account to edit wiki pages, just email docs@evergreen-ils.org for access.
  2. Look over the release notes entry for the feature you picked and decide
    1. if the feature warrants a new section in the official manual (For 9/10/2015, see: http://docs.evergreen-ils.org/dev/) to explain the new feature
    2. or just a bit of new content in an existing section that is related to the new feature.
    3. Maybe what is needed is to replace an existing screenshot in the docs with a newer screenshot that shows off or demonstrates the new feature
  3. Once you decide how the new feature should be documented follow the standard steps to contribute documentation to DIG

NOTE: Sometimes you can reuse almost all of the text in the new feature release note for use in the official docs, but sometime you have to come up with significant edits to the original release notes text.

Acquisitions

Administration

Cataloging

Circulation

Client

OPAC

Needs From Previous Versions

Remove items from the list below as they are completed (or confirmed to be already complete).

Borrow Chapters from Evergreen In Action (from EG 2.2)

https://en.flossmanuals.net/evergreen-in-action/

2.9

General

2.8

2.7

2.6

2.5

2.4

Older or Unknown Release