history:feature_list_2_0
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| feature_list_2_0 [2010/10/29 16:39] – gdunbar | history:feature_list_2_0 [2022/02/10 13:34] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | **Circulation:** (please note that a few of these features may have found their way into 1.6) | + | ====== |
| - | *There is backend code support for a method to allow patrons to link their records in a way that grant privileges. | + | Please note: Some of these features |
| - | *Evergreen has the ability to retrieve users by numberic ID (separate from the barcode) in the staff client. This functionality is optional and set to " | + | ==== Patron Registration Enhancements ==== |
| - | *Patron passwords are now more flexible in length | + | * Zip code information can be added to a local table which will pre-populate the City/State fields during patron registration. [[http:// |
| + | * Added the ability to delete patrons by anonymizing the patron' | ||
| + | * Supports the ability to merge patrons; when it is determined that more than one account exists for a single patron. There is an interface for side-by-side comparison of the records; ability to delete addresses | ||
| + | * Added quick links for staff to copy and paste patron address information. Information will paste in a standard mailing format. | ||
| + | * Patrons | ||
| + | * Patrons may create library accounts through | ||
| + | * The system recognizes certain categories of patrons like Card Canceled, Deceased, etc. and will not place holds for these categories. | ||
| + | * The patron record screen obscures certain information | ||
| + | * Evergreen has the ability to automatically enter date, user, and location | ||
| - | *Patrons can select a username, which can then be used to access OPAC and self check-out stations. | + | ==== Item Checkout enhancements ==== |
| - | *Added the ability to pre-define messages, populated in a drop-down menu, to be applied to patron accounts. | + | * During check-out, the patron' |
| + | * Evergreen has the ability to track hourly checkout stats. Self-check now operates by workstation and it's possible | ||
| + | * Audible cue support, for successful | ||
| + | * Evergreen has fast-add capability. During check-out, if an item is found not to be cataloged, | ||
| + | * The system supports sets or kits of items and has the ability to display | ||
| + | * Evergreen allows patrons to renew a title as long as they have not exceeded the allowed number of renewals and there are more available items than there are unfrozen holds. This is an administration setting. | ||
| - | *Under grocery billings in Evergreen, billing type can be pre-populated with a list of common fine events (such as types and costs).\\ | + | ==== Self Check module enhancements ==== |
| - | + | ||
| - | *Zip code information can be added to a local table which will pre-populate the City/State fields during patron registration.\\ | + | |
| - | *My Account can allow patrons | + | * In self check and SC, if a staff member checks out an item to a patron that is already checked out to that patron, the item will simply renew. This does have configurable age-based parameters to prevent a double scan at checkout resulting in a renewal. |
| + | * For self check receipts, receipts include the same information for renewal as checkouts | ||
| + | * In the self-check UI, patrons can view holds and patron position vs. the number of circulating copies. | ||
| + | * The self check-out station displays holds ready for pickup, then removes each hold as the item is checked out. | ||
| + | * Evergreen supports the ability to pay fines with a credit card at self check-out stations. This requires | ||
| - | *In My Account | + | ==== Item Check-in enhancements ==== |
| - | *From the My Account interface, patrons | + | * Evergreen supports a set number of claim returns allowed; beyond that, additional claim returns require supervisor authorization. This is based off the claims returned counter. This only blocks another claim returned, and circulation |
| - | + | * There' | |
| - | *Added the ability | + | * When marking an item damaged, several library settings are checked |
| - | *Supports the ability to merge patrons; when it is determined that more than one account exists for a single patron. | + | ==== Holds Enhancements ==== |
| - | *Added quick links for staff to copy and paste patron | + | * Evergreen allows |
| + | * Evergreen supports behind the desk indicator printing on holds slip for patrons who have this flag in their patron record. (This would be for libraries with public hold shelves.) | ||
| + | * In Evergreen, between the time that a hold is checked in and a hold is placed on the hold shelf, there is a configurable delay before the status is changed to On Hold Shelf. | ||
| + | * Evergreen has the ability to ensure that manually edited copies (either deleting or changing to a non-holdable status) will have their holds retargeted. | ||
| + | * In Evergreen, between the time that a hold is checked in and a hold is placed on the hold shelf, there is a configurable delay before the status is changed to On Hold Shelf. | ||
| + | * The system supports a Clear Hold Shelf process. First, it removes holds from items that have expired on the hold shelf, and generates a report (aka clear hold shelf report) listing items to be cleared from hold shelf. Then staff can print the list, go out and physically pull the items off of the hold shelf. Next, staff scan the items in EG to either reset the items to the correct shelving location, capture the next hold or put the items in transit to the correct owning location. | ||
| + | * Staff can extend pickup deadlines for holds. | ||
| + | * In the patron view in the SC (staff client), you can select multiple holds in actions for selected holds and choose to change the pickup location. Evergreen has the ability to change the pickup location for all of a patron's holds in a single process. Additionally, | ||
| + | * Evergreen allows patrons with specific permissions to place holds on items they have already checked out. All other patrons cannot. This works by warning the user that the item is already checked out to them and, if they have the permission, the system gives them the ability to override. | ||
| + | * The system supports the ability to place holds on titles with status on-order. For additional | ||
| + | * Evergreen has the ability to designate specific org units that will not trigger a hold upon check-in. | ||
| + | * Evergreen added logic to hold targeting to skip branches that are closed at the time of hold placement and ' | ||
| + | * There are more options now for hold settings. One option is library weighting as well as looping. If looping is set, the holds targeter will skip any libraries that it targeted in a previous loop and will continue doing so until it has tried all libraries at which point it will start the process over again. If max loops are being used in hold management, at the end of the last determined loop, if there are no copies that could potentially fill a hold, the hold may be canceled. If there are checked-out copies, the hold stays in queue; otherwise, the hold is canceled and a cancellation notice is sent to the patron. | ||
| + | * The system offers the ability to secondarily sort the Holds Pull List by physical shelving location within the library. | ||
| + | * The system offers the ability to distinguish between staff-placed holds and patron-placed holds through a column in the holds interface. | ||
| + | * Hold cancellation can be displayed, along with information regarding the cancellation (e.g., cause, cancellation type, date, item, patron, etc.) | ||
| + | * There is support now in the system to allow configuration to disallow holds for items that are on the shelf at the location from which the patron is searching. | ||
| + | * The system supports patron specific hold notes that can display in the OPAC and print in the hold notice, but do not necessarily print on hold slips. | ||
| + | * The system supports ability for staff to move someone to the top of the holds queue. This was developed due to cases where a patron picked up a hold but the item was damaged. Since the patron had picked up the hold, it was considered filled. | ||
| + | * The patron can change the pickup location before the hold is ready for pickup. Then, the item is put in transit & a new holds slip is printed with a special symbol to indicate that the pickup location has been changed. If the location is changed while the item is in transit, than at next checkin the item is put in transit to the new location. A new holds slip is printed. | ||
| + | * The system supports a separate hold note field for staff use that can print on hold slip. | ||
| + | * Ability for patrons to view recently canceled holds and easily re-place holds. | ||
| - | *Evergreen includes color-coding into staff view of patrons when there is a bad or invalid address. | + | ====== Staff Client Interface Enhancements ====== |
| - | *Evergreen | + | * Evergreen |
| + | * Ability to have the staff client automatically minimize after a settable period of inactivity to protect patron privacy. This is controlled through an org unit setting. | ||
| + | * Summary of bills, checkouts, and holds are visible from all of the patron screens. | ||
| + | * Historical summary of paid fines is sortable by column and displays sub-totals for each column; also allows the ability to limit by voided/ | ||
| + | * More streamlined display of copy information including number of copies, copy status, and number of holds in both staff client interface and patron OPAC. | ||
| + | * The system | ||
| + | * From holding maintenance or item status by barcode, you can retrieve more item details. For example, total circulations by current and previous year, last status change, last checkout date & works station, last checkin time and workstation, and more. | ||
| + | * The system includes a separate date field for the last change to the item in the item record. | ||
| + | * In the item record, the system displays total check-outs | ||
| + | * There is better audio signal handling now. An example of how to customize the audio is at: [[http:// | ||
| + | * In Evergreen, there is an org setting to disable all staff client circ popups unless an unhandled exception occurs. The exception handling has been automated as much as possible, based in settings, to prevent the amount of popups that require staff attention at the circ desk. Alerts | ||
| + | * The system supports two views of patron information: | ||
| + | * From the patrons screen, under holds, clicking place hold will bring up an embedded catalog. Placing a hold from the embedded catalog will automatically generate a hold for the current account of the patron you are viewing. | ||
| + | * The system supports a new messages (notes) UI in the info tab of the patron screen. | ||
| + | * The system supports a new interface that shows the most recent activity on the workstation (checkout/ | ||
| + | * Backend support is complete for locally customizable documentation and help on each page in the SC. More information: | ||
| + | * The system now captures and displays check-in and workstation history. | ||
| + | * Added the ability to pre-define messages, populated in a drop-down menu, to be applied to patron accounts. Includes: the ability to configure the message to act as a penalty (if desired), record the date and staff who applied the message, include a flag to mark item as resolved. If item is marked as resolved it will not display as an alert. | ||
| + | * Under grocery billings in Evergreen, billing type can be pre-populated with a list of common fine events (such as types and costs). | ||
| + | * Evergreen has the ability to retrieve users by numberic ID (separate from the barcode) in the staff client. This functionality is optional and set to false by default. | ||
| + | * Backend support for other types of receipts (like holds/ | ||
| - | *Patrons can title their bookbags (aka reading list) and place holds from it.\\ | + | ====== OPAC and My Account Enhancements ====== |
| - | *Ability for patrons to view recently cancelled holds and easily re-place holds.\\ | + | * There is backend |
| - | + | * Patron passwords are now more flexible | |
| - | *Ability to have the staff client automatically minimize after a settable period of inactivity to protect patron privacy. This is | + | * Patrons |
| - | + | * My Account can allow patrons | |
| - | *Summary of bills, checkouts, and holds are visible from all of the patron screens.\\ | + | * From the My Account |
| - | + | * Patrons | |
| - | *Historical summary of paid fines is sortable by column and displays sub-totals for each column; also allows the ability to limit by voided/ | + | * Backend support has been developed to allow patrons to waive certain kinds of notices. |
| - | + | * The system supports combining multiple notices of the same type to the same patron into one event, so long as the system is configured to batch notices on an approximately daily basis. | |
| - | *Fines consistently link to item record details.\\ | + | |
| - | + | ||
| - | *Patrons with an " | + | |
| - | + | ||
| - | *Patrons may create library accounts through the OPAC. These are set as pending until they can be confirmed by staff. The backend support for this is done. \\ | + | |
| - | + | ||
| - | *More streamlined display of copy information including number of copies, copy status, and number of holds in both staff client interface and patron OPAC.\\ | + | |
| - | + | ||
| - | *The system supports the ability to edit item records from any item record access point.\\ | + | |
| - | + | ||
| - | *The system supports sets or kits of items and has the ability to display the number of items and a list of descriptions.\\ | + | |
| - | + | ||
| - | *From holding maintenance or item status by barcode, you can retrieve more item details. | + | |
| - | + | ||
| - | *The system now captures and displays check-in and workstation history.\\ | + | |
| - | + | ||
| - | *The system includes a separate date field for the last change | + | |
| - | + | ||
| - | *In the item record, the system displays total check-outs and renewals for year-to-date, previous year, and lifetime.\\ | + | |
| - | + | ||
| - | *The system supports a separate hold note field for staff use that can print on hold slip. \\ | + | |
| - | + | ||
| - | *The patron can change the pickup location before the hold is ready for pickup. | + | |
| - | + | ||
| - | *The system supports ability for staff to move someone to the top of the holds queue. | + | |
| - | + | ||
| - | *The system supports patron specific hold notes that can dipslay | + | |
| - | + | ||
| - | *The system recognizes certain catergories of patrons, like Card Canceled, Deceased, etc. and will not place holds for these categories. \\ | + | |
| - | + | ||
| - | *There is support | + | |
| - | + | ||
| - | *Hold cancellation can be displayed, along with information regarding the cancellation | + | |
| - | + | ||
| - | *The system offers the ability to distinguish between staff-placed holds and patron-placed holds through a column in the holds interface. \\ | + | |
| - | + | ||
| - | *There | + | |
| - | + | ||
| - | *The system offers the ability to secondarily sort the pull list by physical shelving location within the library.\\ | + | |
| - | + | ||
| - | *If max loops are being used in hold management, at the end of the last determined loop, if there are no copies that could potentially fill a hold, the hold may be canceled. | + | |
| - | + | ||
| - | *Evergreeen added logic to hold targeting to skip branches that are closed at the time of hold placement and ' | + | |
| - | + | ||
| - | *Evergreen allows for hold slips to be customized to include any field from the patron record and/or item record, | + | |
| - | + | ||
| - | *Evergreen supports " | + | |
| - | + | ||
| - | *In Evergreen, between the time that a hold is checked | + | |
| - | + | ||
| - | *Evergreen has the ability to ensure that manually edited copies | + | |
| - | | + | |
| - | *The system supports a Clear Hold Shelf process. | + | |
| - | + | ||
| - | *Staff can extend pickup deadlines for holds. \\ | + | |
| - | + | ||
| - | *In the patron view in the SC, you can select | + | |
| - | + | ||
| - | *" | + | |
| - | + | ||
| - | *Leave unset to ignore this entirely.\\ | + | |
| - | + | ||
| - | *Evergreen allows patrons with specific permissions to place holds on items they have already checked out. All other patrons cannot. | + | |
| - | + | ||
| - | *The system supports the ability to place holds on titles with status on-order. | + | |
| - | + | ||
| - | *Evergreen has the ability to designate specific org units that will not trigger a hold upon check-in.\\ | + | |
| - | + | ||
| - | *During check-out, the patron' | + | |
| - | + | ||
| - | *Evergreen has the ability to track hourly checkout stats. | + | |
| - | + | ||
| - | *Evergreen has fast add capability. | + | |
| - | + | ||
| - | *In self check and SC, if a stff member checks out an item to a patron that is already checked out to that patron, the item will simply renew. | + | |
| - | + | ||
| - | *For self check receipts, receipts include the same information | + | |
| - | + | ||
| - | *Audible cue support, for successful and unsuccessful check-out, at self check-out stations has been added. | + | |
| - | + | ||
| - | *In the self-check UI, patrons can view holds and patron position vs. the number of circulating copies. | + | |
| - | + | ||
| - | *The self check-out station displays holds ready for pickup, then removes each hold as the item is checked out.\\ | + | |
| - | + | ||
| - | *Backend support for other types of receipts (like holds/fines) is also complete. \\ | + | |
| - | + | ||
| - | *Evergreen supports the ability | + | |
| - | + | ||
| - | *Evergreen supports a set number of claim returns allowed; beyond that, additional claim returns require supervisor authorization. | + | |
| - | + | ||
| - | *There is a new permission to allow changing the claims returned count for a patron. | + | |
| - | + | ||
| - | *Evergreen supports the ability to waive fines during check-in. This option covers waiving | + | |
| - | + | ||
| - | *There's a new calendar widget in the backdating function in the item check-in module. \\ | + | |
| - | + | ||
| - | *The system has the ability to select items already checked in and retroactively backdate those items, using a button with a calendar selector. Any fines resulting from original | + | |
| - | + | ||
| - | *When a check-in is backdated, the item record retains both the actual date of check-in and backdate used. This information will display in the copy details | + | |
| - | + | ||
| - | *When marking an item damaged, several library settings are checked to determine whether the patron should be charged the copy price and/ | + | |
| - | + | ||
| - | *The system has the ability to run a report of accounts with users with overall negative balances, including the balance owed and last billing activity | + | |
| - | + | ||
| - | *The system supports setting the maximum fine based on item type (e.g. generic=.50) AND not to exceed | + | |
| - | + | ||
| - | *The fine record includes a comments field, editable by staff. | + | |
| - | + | ||
| - | *A new penalty type of PATRON_IN_COLLECTIONShas been added. It's set when the collections agency puts the patron into collections, | + | |
| - | + | ||
| - | *Staff | + | |
| - | + | ||
| - | *There is better audio signal handling now. An example of how to customize the audio is at: | + | |
| - | http:// | + | |
| - | For a more comprehensive example of how to customize the audio for check-in see: | + | |
| - | http:// | + | |
| - | + | ||
| - | *In Evergreen, there is an org setting to disable all staff client circ popups unless an unhandled exception occurs. | + | |
| - | + | ||
| - | *Backend support has been developed to allow patrons to waive certain kinds of notices. | + | |
| - | + | ||
| - | *The system supports combining multiple notices of the same type to the same patron into one event, so long as the system is configured to batch notices on an approximately daily basis. | + | |
| - | + | ||
| - | *The system has the ability to cancel unsent notices before they are sent and the ability to search pending notices by item barcode. \\ | + | |
| - | + | ||
| - | *Action Triggers (AT) support many new notices for events such as items that are about to expire off of the hold shelf; items that are on hold and are about to reach the max hold time (if one is set); courtesy notices that are prior to due date. AT also logs all notices sent to patrons and this is accessible to staff in the SC to view all notices or cancel all pending notices. | + | |
| - | + | ||
| - | *Administrators can choose to implement a collections warning prior to sending patrons to collections. | + | |
| - | + | ||
| - | *The system supports two views of patron information: | + | |
| - | + | ||
| - | *From the patrons screen, under holds, clicking place hold will bring up an embedded catalog. | + | |
| - | + | ||
| - | *The system supports a new messages (notes) UI in the info tab of the patron screen.\\ | + | |
| - | + | ||
| - | *The system supports a new interface that shows the most recent activity on the workstation (checkout/ | + | |
| - | + | ||
| - | *The patron record screen obscures certain information which can be considered sensitive. | + | |
| - | *Evergreen has the ability to automatically enter date, user, and location in messages | + | ====== Billing, Collections |
| - | *Backend support is complete for locally customizable documentation | + | * Fines now consistently link to item record details |
| + | * The fine record includes a comments field, editable by staff. Staff can annotate payments | ||
| + | * Staff and users can now only pay using the latest user data, which prevents accidental/ | ||
| + | * The system supports setting the maximum fine based on item type (e.g. generic=.50) AND not to exceed the cost of item. This works as an inheritable OU setting, circ.max_fine.cap_at_price, | ||
| + | * The system has the ability to run a report of accounts with users with overall negative balances, including the balance owed and last billing activity time, optionally filtered by home org. There is an option for issuing refunds for selected accounts on the resulting list. The report also captures patrons with any refundable transaction. | ||
| + | * Evergreen provides 3 distinct and independent types of blocks: system, manual and collections. Manual and collections are set manually by staff. | ||
| + | * A new penalty type of PATRON_IN_COLLECTIONShas been added. Its set when the collections agency puts the patron into collections, | ||
| - | \\ | + | ====== Action/ |
| - | \\ | + | |
| - | \\ | + | |
| + | * Action Triggers (AT) support many new notices for events such as items that are about to expire off of the hold shelf; items that are on hold and are about to reach the max hold time (if one is set); courtesy notices that are prior to due date. AT also logs all notices sent to patrons and this is accessible to staff in the SC to view all notices or cancel all pending notices. | ||
| + | * The system has the ability to cancel unsent notices before they are sent and the ability to search pending notices by item barcode. | ||
| + | * Administrators can choose to implement a collections warning prior to sending patrons to collections. When the account balance of the patron meets a certain threshold, they are sent a bill notice. This is driven by the total amount owed, not by individual bills. The patron is sent to collections after a configurable number of days since the bill notice was sent. The billing notice is handled with a new PATRON_EXCEEDS_COLLECTIONS_WARNING penalty. Files can be sent via SCP and FTP. | ||
| - | **Acquisitions**\\ | + | ======Acquisitions====== |
| *From within the general acquisitions search page, users are able to search on many fields in the acquisitions /serials workflow. For example on attributes of invoices, purchase orders, selection lists, bib records, etc.\\ | *From within the general acquisitions search page, users are able to search on many fields in the acquisitions /serials workflow. For example on attributes of invoices, purchase orders, selection lists, bib records, etc.\\ | ||
| Line 248: | Line 173: | ||
| *Deleted bibs, callnumbers, | *Deleted bibs, callnumbers, | ||
| - | *The system supports shared and floating items by collection. | + | *The system supports shared and floating items by collection. |
| *ACQ permissions control which workgroups have view/edit access to lineitem and catalog records while PO/PL and copy-level ownership and permission depths affect viewing in other, more location-specific interfaces. \\ | *ACQ permissions control which workgroups have view/edit access to lineitem and catalog records while PO/PL and copy-level ownership and permission depths affect viewing in other, more location-specific interfaces. \\ | ||
| Line 346: | Line 271: | ||
| *Staff can add regular, supplemental, | *Staff can add regular, supplemental, | ||
| - | *The system supports | + | *The system supports |
| - | + | ||
history/feature_list_2_0.1288384789.txt.gz · Last modified: 2022/02/10 13:34 (external edit)