Hi Jim,
It's likely that this information is not available in the documentation,
but if anyone has the inclination to essentially copy what Jason said
into Asciidoc so that it can be included, I'm sure others would
appreciate it!
If anyone is interested, I would happy to work with you on it to point
you in the right direction for how the documentation gets done.
Have a nice weekend!
Kathy
On 09/01/2017 05:41 PM, Jim Taylor wrote:
Thank you very much. This is very helpful. Wish I could have found
it in the documentation and not bothered anyone. One day I will
figure out how to find stuff in the documentation 😊
Jim
-----Original Message-----
From: Open-ils-general
[mailto:[email protected]] On Behalf
Of Jason Stephenson
Sent: Friday, September 1, 2017 4:15 PM
To: [email protected]
Subject: Re: [OPEN-ILS-GENERAL] Aged_Circulation
On 09/01/2017 04:50 PM, Jim Taylor wrote:
> Okay. Thanks.
>
>
>
> So there is no duplication? Everything in aged_circulation was once in
> circulation and is moved, not copied, to aged_circulation? It just
> loses some of the info? Or is it copied and everything in
> aged_circulation is still in circulation, assuming one hasn’t deleted
> rows in circulation?
There is no duplication. The action.aged_circulation is for
statistical reporting while breaking the link to the patron who had
the item checked out.
Circulations get moved under three circumstances in stock Evergreen:
1. A patron is deleted. This moves all of the patron's circulations
from action.circulation to action.aged_circulation
2. A row or row(s) in action.circulation are deleted. The
action.age_circ_on_delete trigger moves deleted action.circulations to
action.aged_circulation.
3. The action.purge_circulations function is run. This function is
meant to be run periodically to enforce patron privacy. It's behavior
is controlled by two internal flags: history.circ.retention_age and
history.circ.retention_count. The purge_circulations function is often
run from cron via the purge_circulations.srfsh script. NOTE: This
function will take a *long* time to run for the first time on a system
that has had much activity. The srfsh script will likely time out
before the database function finishes and nothing will get moved.
If you have not been doing 2 or 3, then the aged_circulation entries
you see are likely because of 1.
You can delete rows from action.aged_circulation if you wish. Keep in
mind that this could lead to the loss of statistical information
depending on what reports you use.
HtH,
Jason
>
>
>
> Jim
>
>
>
> *From:* Open-ils-general
> [mailto:[email protected]] *On Behalf
> Of *Rogan Hamby
> *Sent:* Friday, September 1, 2017 1:54 PM
> *To:* Evergreen Discussion Group
> <[email protected]
<mailto:[email protected]>>
> *Subject:* Re: [OPEN-ILS-GENERAL] Aged_Circulation
>
>
>
> Hi Jim, Benjamin,
>
>
>
> There are a number of differences that touch on aged versus not-aged
> circulations. It's certainly true that circulations can be moved out
> of action.circulation to keep that table size down and that can be
> useful when we discuss things like tablespaces and Postgres.
>
>
>
> However, to me the major difference is that the action.circulation
> table attaches back to the actor.usr table, i.e. there is a link
> between the patron and the circulation. That link goes bye bye when a
> circ is moved to action.aged_circulation. Some patron information is
> recorded in aged circulations for future statistical reporting
> purposes such as the user's post code, home org unit, profile group
> and birth year but the patron themselves is no longer identifiable.
> Obviously, this can be of significant value for patron privacy.
>
>
>
>
>
>
> Rogan Hamby
>
> Data and Project Analyst
>
> Equinox Open Library Initiative
>
> phone: 1-877-OPEN-ILS (673-6457)
>
> email: [email protected] <mailto:[email protected]>
> <mailto:[email protected]>
>
> web: http://EquinoxInitiative.org
>
>
>
> On Fri, Sep 1, 2017 at 1:15 PM, Murphy, Benjamin
> <[email protected] <mailto:[email protected]
<mailto:[email protected]%20%3cmailto:[email protected]>>>
wrote:
>
> I’d love to see this as well if it exists.
>
>
>
> Benjamin
>
>
>
> Benjamin Murphy
>
> Manager, NC Cardinal Program
>
> NC Dept. of Natural and Cultural Resources
>
> 919.807.7424 <tel:(919)%20807-7424 <tel:%28919%29%20807-7424>>
>
> [email protected] <mailto:[email protected]>
<mailto:[email protected]>
>
>
>
> Mail: 4640 Mail Service Center, Raleigh, NC 27699 | Office: 109 East
> Jones St. Raleigh, NC 27601
>
>
>
> /Email correspondence to and from this address is subject to the
> North Carolina Public Records Law and may be disclosed to third
> parties./
>
>
>
>
>
>
>
> *From:* Jim Taylor [mailto:[email protected]
> <mailto:[email protected]>]
> *Sent:* Friday, September 01, 2017 12:20 PM
> *To:* 'Evergreen Discussion Group'
> <[email protected]
> <mailto:[email protected]>>
> *Subject:* [OPEN-ILS-GENERAL] Aged_Circulation
>
>
>
> I am looking for a link to documentation that explains the purpose
> of each table. I have found the schema documentation but nothing
> that explains the purpose. Currently I am trying to determine the
> relationship of aged_circulation to circulation. Since circulation
> contains records that are older than aged_circulation I assume it
> isn’t what the name might imply?
>
>
>
>
>
> Thank you.
>
>
>
> Jim
>
>
>
--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
[email protected]
Twitter: http://www.twitter.com/kmlussier
