stompro

I got curious just how far back ZIP lookup goes, and it starts with commit 2ea132cef5bf36106378f8c15943d0acbe443361 from 2006-05-03 ... It's been a thing since since before PINES went live!  Anyone up for retrospectively writing version 0.01 docs?

- only the first five digits in the ZIP code field are considered
- only the city, state, and county fields are used during address prepopulation
- the field after area code can store an alert message.  If that's present, then the patron registration form will display an alert -- this can be useful if (say) a ZIP code is used by more than one town

https://web.archive.org/web/20110417152404/http://dmagick.wordpress.com/2011/01/06/notes-on-installing-zipcode-information/


FWIW, we just used this free listing to pre-populate our code list

stompro

Files involved
Original commit
https://github.com/evergreen-library-system/Evergreen/commit/29a874a1f9c99d2eb69b048631d4e5b0dc51a813


./Open-ILS/src/templates/conify/global/config/barcode_completion.tt2
https://github.com/evergreen-library-system/Evergreen/blob/master/Open-ILS/src/templates/conify/global/config/barcode_completion.tt2

./Open-ILS/web/js/ui/default/conify/global/config/barcode_completion.js
https://github.com/evergreen-library-system/Evergreen/blob/master/Open-ILS/web/js/ui/default/conify/global/config/barcode_completion.js

stompro

Barcode Completion

The Barcode Completion feature gives users the ability to only enter the unique part of patron and item barcodes. This can significantly reduce the amount of typing required for manual barcode input. This feature was also known as Lazy Circ at one point.

This feature can also be used if there is a difference between what the barcode scanner outputs and what is stored in the database, as long as the barcode that is stored has more characters then what the scanner is outputing. Barcode Completion is additive only, you cannot use it match a stored barcode that has less characters than what is entered. For example, if your barcode scanners used to output a123123b and now exclude the prefix and suffix, you could match both formats using Barcode Completion rules.

Because this feature adds an extra database search for each enabled rule to the process of looking up a barcode, it can add extra delays to the check-out process. Ple

stompro

DataExchange patron export MARC format

030 a - Barcode - can repeat
020 a - Unique ID
080 a - Expiration Date
081 a - pcode1 - County Code
082 a - pcode2 - MN System Code
083 a - pcode3 - CME Agency Code
084 a - ptype - Patron Type Code
085 a - Home Library

stompro

Phone Notification System - III to Evergreen

Documenting my experience with setting up a phone notification system for an Evergreen ILS System.

Current Situation

We currently use Teleforms D, a telephone notification product from Innovative Interface Incorportate. It mostly works fine. In my opinion it is way over priced, simply because it is the only option that III gives you for telefone notification that is intigrated with the system. For your large amount of money you get a cheap consumer grade computer with a dual FXO expansion card, with no warranty according to their tech support. If the machine dies you need to re-purchase the system, including the licensing for the priviledge of using the product.

stompro

Including Locally Hosted Content in Your Public Interface

It is also possible to show added content that has been generated locally by placing the content in a specific spot on the web server. It is possible to have local book jackets, reviews, TOC, excerpts or annotations.

File Location and Format

By default the files will need to be placed in directories under /openils/var/web/opac/extras/ac/ on the server(s) that run Apache.

stompro

Info on this feature - to help with documenting the feature.
Release notes - http://docs.evergreen-ils.org/2.5/_administration.html#_purge_holds
Launchpad Bug - https://bugs.launchpad.net/evergreen/+bug/1016058
Working Branch - http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/dyrcona/purge_holds

stompro

Sources for writing documentation for feature.
Release Notes - http://docs.evergreen-ils.org/2.5/_opac_2.html#_opac_maintenance_message
Launchpad Bug - https://bugs.launchpad.net/evergreen/+bug/1132000
Working Branch - http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/dbs/maintenance_message_utf8_cleanliness_no_apache_reload_required

stompro

2.5 Release Notes - http://docs.evergreen-ils.org/2.5/_opac_2.html#_added_content_by_record_id
2.7 Release Notes - http://docs.evergreen-ils.org/2.7/_opac.html#_added_content_by_record_id
LP Bug for 2.5 - https://bugs.launchpad.net/evergreen/+bug/1065378
Working branch for 2.5 - http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/jeff/ac_by_record_id_2013_rebase

LP Bug for 2.7 - https://bugs.launchpad.net/evergreen/+bug/1347793
working branch for 2.7 - http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/tsbere/addedcontent_by_id_tpac

stompro

Pre-Expiration Notice Setup

These instructions will walk you through setting up the Pre-Expiration notice. This notice is intended to be used to notify users 30 days before their accounts expire, so they have time to renew their account before it expires.

The time limits are completely configurable, so you can change the time limits to whatever makes sense for your environment, including notifying the customer after their account has expired.