Added a days_back parameter to

Bug #985670 reported by Steve Callender on 2012-04-19
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

Currently would only work if providing a range of id's, an individual record, or specifying all. I have added a days_back option so that you can just specify how many days back you want to go and it will process any newly created or changed bibs from that point on.

A good use for this option is to allow the ability to easily run in cron as a nightly process to process bibs changed that day.

Patch is in collab/Callender/authority_control_fields_days_back;a=shortlog;h=refs/heads/collab/Callender/authority_control_fields_days_back



Gordana Vitez (gvitez) wrote :

The patch Steve created has been working for the Niagara Evergreen Consortium and we'd like to see it included in future versions. We really missed it when we upgraded to 2.2 last week.


Hi Gordana and Steve,

I'm sorry this didn't get attention earlier than this. It looks good for master, and I've merged Steve's work there. However it's too late for new features in the 2.2 series.


(of course any given site can easily adopt master's version of this script on their own)

Changed in evergreen:
status: New → Fix Committed
milestone: none → 2.3.0-alpha
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers