Evergreen provides multiple options for adding messages and alerts to a patron’s record. The two main message areas are the Alert Message field (accessed through the Edit tab of a patron’s record) and the Message field (located in the Messages tab). Alert Messages result in a highlighted yellow note on the top left corner of a patron’s account, while Messages show up in the middle of the screen when a patron’s account is first loaded.
In order to maintain consistency in the way these different fields are used across the network, NOBLE libraries are expected to adhere to the following guidelines regarding the use of these fields: Alert Messages are used specifically for patron-related information that is intended to stay on a record for a long time, while Messages are used for short-term messages and actions.
Examples of long-term Alert Message content include:
- Who can transact business on the patron’s card (parents, spouses, aides, etc.)
- Distinguishing relatives with the same name
- Account use restrictions
- Equipment use agreements
- Handicaps that staff should be aware of (hearing loss, etc.)
- College blocks
Library staff must add initials, library and date to all Alert Messages.
Examples of short-term regular Message content include:
- Notifications about items left in the library
- Verify telephone number, mailing address, email, etc.
- Check identification
- Record of attempts to contact patron
- Items returned damaged or incomplete
Messages are viewable to all NOBLE libraries by default, but staff members can choose to limit the view to their local libraries only, by selecting this option from the drop-down menu during message creation.
All Messages, Alert Messages and other information entered into patron records are for the use of the staff of NOBLE libraries and subject to NOBLE’s confidentiality practices and procedures. As information entered could become known to the library user, all information should be respectful of library users and be factual, avoiding disparaging language and editorializing.
Approved by Meeting of the Members March 15, 2017
Updated by Meeting of the Members October 19, 2017