We use a low-tech method: a reoccurring monthly report shows items
needing age protection removed. We import the barcodes into item status
and batch remove the protection. Not fully automated, but takes less
than five minutes and anyone on staff can do it.
CM
On 12/15/2015 11:07 AM, Hardy, Elaine wrote:
Just so you know, there is a reason why the age protection remains, but
it is PINES specific. A PINES library, prior to Evergreen, was returning
items to age protection after it expired so that no other system’s
patrons could place holds. To prevent that, age protection in Evergreen
was designed to remain after expiration so that it could not be
reassigned to an item.
/Elaine/
J. Elaine Hardy
PINES & Collaborative Projects Manager
Georgia Public Library Service
1800 Century Place, Ste 150
Atlanta, Ga. 30345-4304
404.235.7128
404.235.7201, fax
[email protected]
www.georgialibraries.org
www.georgialibraries.org/pines
*From:*Open-ils-general
[mailto:[email protected]] *On Behalf
Of *Tim Spindler
*Sent:* Tuesday, December 15, 2015 10:48 AM
*To:* Evergreen Discussion Group
*Subject:* Re: [OPEN-ILS-GENERAL] Removing Age Protection after expired
We have a cron that runs to do this from an SQL script.
On Tue, Dec 15, 2015 at 10:27 AM, Blake Henderson
<[email protected] <mailto:[email protected]>> wrote:
Josh,
We have a custom made perl cron job to remove the protection. I didn't
realize it was a bug! I would be happy to share the perl script (it is
fairly custom to our needs but it can be adapted easily)
-Blake-
Conducting Magic
MOBIUS
573-234-4513 <tel:573-234-4513>
877-312-3517 <tel:877-312-3517>
On 12/15/2015 9:24 AM, Josh Stompro wrote:
Hello, does anyone else out there remove the age protection from
copies after it has expired. I’ve been asked to set that up, and it
seems like a shame since it was designed to just work automatically,
except that items with expired age protection still show up as age
protected in the catalog. There is a bug open about it at
https://bugs.launchpad.net/evergreen/+bug/1251761
Does anyone currently go through and remove the age protection to
get around that issue? If so do you do it directly at the DB level
or do you use the client? Are there any gotchas about directly
updating asset.copy to change the age protection and also changing
the shelving location at the same time.
If anyone wants to combine resources to get that bug fixed, either
with brain power or development funding let me know also.
Josh
Lake Agassiz Regional Library - Moorhead MN larl.org <http://larl.org>
Josh Stompro | Office 218.233.3757 EXT-139
<tel:218.233.3757%20EXT-139>
LARL IT Director | Cell 218.790.2110 <tel:218.790.2110>
--
Tim Spindler
[email protected] <mailto:[email protected]>
*P** Go Green - **Save a tree! Please don't print this e-mail unless
it's really necessary.*
--
Chauncey G. Montgomery, MLIS
Director/Fiscal Officer | Community Library
44 Burrer Drive | Sunbury, OH 43074
740-965-3901 | http://community.lib.oh.us
