I think links to documentation from the release notes would be very useful.

---
Sarah Childs
Technical Services Department Head
Hussey-Mayfield Memorial Public Library
250 North Fifth Street
Zionsville, IN 46077
317-873-3149 x13330
[email protected]

On 2014-06-30 11:27, Kathy Lussier wrote:
Thanks for the reminder Remington! My tasks are done, and I'm
available to help anyone who needs it.

I was thinking it might be nice if we updated the release notes and
linked directly from each entry to the documentation for the new
feature. Would people find this useful? If so, I should be able to
work on it over the next couple of days.

Kathy

Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
[email protected]
Twitter: http://www.twitter.com/kmlussier

On 6/24/2014 9:43 AM, Remington Steed wrote:

Hi DIG,

Just a quick reminder to finish up your Docs 2.6 tasks this week. If you have any questions or need any help, please don't hesitate to email this list. We are all working together to complete the new 2.6 features by July 1, and we can do it! Never give up, never surrender!

Remington

--

Remington Steed

Electronic Resources Specialist

Hekman Library, Calvin College

http://library.calvin.edu/

*From:* [email protected] [mailto:[email protected]] *On Behalf Of *Remington Steed
*Sent:* Tuesday, June 10, 2014 9:20 AM
*To:* Documentation discussion for Evergreen software
*Subject:* [OPEN-ILS-DOCUMENTATION] Progress Report, feedback please

Hi DIG,

Thank you all for your contributions so far to 2.6 features. We are almost done! We only have one more feature that needs to be claimed by someone, and only a few that need to be finished. Our goal is to have everything committed to the master repository by Tuesday, July 1, so I would request that everyone send their finished docs to the DIG mailing list by Tuesday, June 24 so the committers have a week to review and commit everything. These are both arbitrary deadlines, but they are meant to motivate us, so let's go for it! Remember that you can submit your work via GitHub <https://github.com/evergreen-library-system/Evergreen>, or in whatever format is easiest for you. See this wiki page <http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:how-to-contribute-documentation> for detailed instructions.

If your name is on the list below, please reply with a quick update on your progress and whether you need any help. Don't be afraid to ask for help! We are all nice people! You can also update the To-Do list <http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:2.6_needs> directly.

*NEEDING TO BE CLAIMED*

OPAC: Web Content Accessibility Guidelines (WCAG) Compliance

- Simply add a sentence to the TPAC documentation that it is WCAG compliant

*REQUEST FOR PROGRESS REPORT*

[Jennifer] Acquisitions: EDI account set up

[Kate] Administration: Add granular settings for requiring staff initials for notes.

[Remington] Cataloging: marc_export script replacement

-Hoping to finish by tomorrow.

[Elliot] Circulation: User Editor: "Update Expire Date" button

[Kathy] OPAC: Located URI visibility options

[Kathy] Miscellaneous: Removal of open-ils.ingest service

[ESI] Cataloging: Enhancements to Evergreen's MARC Editor Concerning Fixed Fields

[ESI] OPAC: Composite Record Attributes

[ESI] OPAC: Multi-valued Record Attributes and Controlled Record Attributes

[ESI] OPAC: TPAC Metarecord Search and Holds

--

Remington Steed

Electronic Resources Specialist

Hekman Library, Calvin College

http://library.calvin.edu/



_______________________________________________
OPEN-ILS-DOCUMENTATION mailing list
[email protected]
http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation


_______________________________________________
OPEN-ILS-DOCUMENTATION mailing list
[email protected]
http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation
_______________________________________________
OPEN-ILS-DOCUMENTATION mailing list
[email protected]
http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation

Reply via email to