evergreen-docs:3.0_needs
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
evergreen-docs:3.0_needs [2017/11/17 09:15] – [Upgrade notes] sandbergja | evergreen-docs:3.0_needs [2022/02/10 13:34] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | =====Evergreen 3.0 Documentation Needs===== | + | <del>Evergreen 3.0 Documentation Needs</ |
Documentation needs based on the [[https:// | Documentation needs based on the [[https:// | ||
- | |||
- | Also, based on earlier release notes. | ||
Copy the HTML code below to update the status of an item: | Copy the HTML code below to update the status of an item: | ||
Line 22: | Line 20: | ||
These are the high-level steps we take to document new features: | These are the high-level steps we take to document new features: | ||
- Look at the new feature docs to do list (this page) and sign yourself up for documenting a new feature | - Look at the new feature docs to do list (this page) and sign yourself up for documenting a new feature | ||
- | - You will need a EG community wiki account to edit wiki pages, just email docs@evergreen-ils.org for access. | + | - You will need a EG community wiki account to edit wiki pages, just email [[docs@evergreen-ils.org]] for access. |
- Look over the release notes entry for the feature you picked and decide | - Look over the release notes entry for the feature you picked and decide | ||
- if the feature warrants a new section in one or more of the official manuals (http:// | - if the feature warrants a new section in one or more of the official manuals (http:// | ||
Line 30: | Line 28: | ||
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. | 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. | ||
+ | |||
+ | ==== Style Guide ==== | ||
+ | |||
+ | * Remember to follow (and improve) the [[evergreen-docs: | ||
+ | |||
+ | ===== Bugs/Minor Problems in the Documentation ===== | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | |||
+ | ===== Web Client docs needs ===== | ||
+ | * [[evergreen-docs: | ||
===== 3.0 documentation needs ===== | ===== 3.0 documentation needs ===== | ||
Line 69: | Line 78: | ||
==== Circulation ==== | ==== Circulation ==== | ||
- | * Batch Editing of Patron Records | + | * Batch Editing of Patron Records |
+ | * NOTE: Seems to be finished | ||
+ | * CONSIDER removing earlier draft section: [[http:// | ||
* Honor timezone of the acting library | * Honor timezone of the acting library | ||
* Enhancements to Hard Due Date Functionality | * Enhancements to Hard Due Date Functionality | ||
Line 298: | Line 309: | ||
==== Older or Unknown Release ==== | ==== Older or Unknown Release ==== | ||
+ | |||
+ | * Inventory | ||
+ | * Elaine Hardy of PINES wrote [[http:// | ||
+ | * Patron penalty color-codes (colored border around patron name) ([[https:// | ||
+ | * Cataloging (needs to be reorganized) | ||
+ | * < | ||
+ | * Need a new " | ||
+ | * Intro to SQL (Based on Dan Scott content) Yamil still needs to make some edits like proper attribution, | ||
+ | * Library Settings Editor - (Lynn Floyd, SCLENDS is working on it) | ||
+ | * OpenSRF/ | ||
+ | * http:// | ||
+ | * Archiving of Circulation Transactions (new section) | ||
+ | * Addresses on Routing List (missing?) | ||
* Administration | * Administration | ||
Line 330: | Line 354: | ||
* A great start in the wiki by phasefx - http:// | * A great start in the wiki by phasefx - http:// | ||
* There is a presentation by Equinox - http:// | * There is a presentation by Equinox - http:// | ||
+ | |||
+ | ==== Non-Docs Tasks ==== | ||
+ | * Setup a mechanism for testing/ | ||
+ | * yboston will email Dev list for feedback on this preliminary plan | ||
+ | * include [[http:// | ||
+ | * Improve the PDF version of the built documentation (ask community for usage, ideas, etc.) | ||
+ | * Setup/use Google analytics to improve docs website design | ||
+ | * Incorporate relevant docs links into Web Staff Client screens (i.e. contextual help) | ||
+ | * UI improvements | ||
+ | * [[http:// |
evergreen-docs/3.0_needs.1510928147.txt.gz · Last modified: 2022/02/10 13:34 (external edit)