Hi, On Wed, Sep 3, 2014 at 8:10 AM, Josh Stompro <[email protected]> wrote: > I think I can figure most of it out by looking at the Zips.pm and from some > comments I can find in IRC archives.
I see that Kathy has sent a link to the archive of John's blog post. A couple things to add: - 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 > If I wanted to document this feature for the official documentation - would > it go in the "System Configuration and Customization" section? +1 > What would the official name of this feature be? "Zip Code Pre-Populate" > "Zip Code Auto-Populate" "Patron Address pre-populate based on Zip Code" I suggest Patron Address City/State/County Pre-Populate by Zip Code. > And a general question - should each feature section state when the feature > was introduced, to make it easier to backport the documentation for previous > versions. Are new documentation additions added to the older documentation > versions? I can't speak to how best to include it DIG's workflow, but if it can be done without becoming an undue burden, I think tagging documentation of a feature with its initial released version would be fantastic. Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: [email protected] direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org _______________________________________________ OPEN-ILS-DOCUMENTATION mailing list [email protected] http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation
