Need Evergreen to capture who and where patrons are registered

Bug #1607827 reported by Blake GH on 2016-07-29
This bug affects 12 people
Affects Status Importance Assigned to Milestone
Michele Morgan

Bug Description


We have a need for the software to capture the org unit that the patrons was registered (not home library). We also would like to capture the staff client user that registered the patron. Might as well grab the workstation as well.

Chris Sharp (chrissharp123) wrote :


Could this be achieved by improvements to the auditor schema that would record the creation of user records (and not just updates), or would this information need to be visible in the client?


Blake GH (bmagic) wrote :


This information needs to be visible in the staff client. At least that is the intent from our libraries.

Michele Morgan (mmorgan) wrote :

I would be in favor of recording the following in the actor.usr table:

create date
edit date

This is in keeping with the asset.call_number and asset.copy tables.

Mike Rylander (mrylander) wrote :

While it's not spelled the same, we do have an edit date field on actor.usr called last_update_time which is maintained by a trigger. And there is create_date.

For creator and editor, what values would we supply to existing records? Or would those be NULLable?

And, for "creating org unit" from Blake's original request, how would that be populated, if it were? Perhaps by home_ou?


Blake GH (bmagic) wrote :


Perhaps the upgrade sql could use a value of "1" for editor and creator for those pre-existing actor.usr rows? Or not.

I believe the new editor and new creator columns should be a SQL foreign key references to, don't you agree? Null might be OK actually, now that you mention it.

Upon row insert, the creating_workstation column could be populated with The creating org unit could be equal to the actor.workstation.owning_lib.

Is there an issue with these ideas?

Michele - actor.usr already has create_date and last_edit_date.

Michele Morgan (mmorgan) wrote :

I would say the existing create_date and last_edit_date fit the bill.

As for the existing records, I'm leaning toward NULL for the creator and editor. I would agree with Blake that the creator and editor should reference, and that the creating_workstation should reference

As for the "creating org unit", do we actually need that if it would capture actor.workstation.owning_lib, since we'll already be capturing the workstation?

And while we're at it, would it be useful to capture the last_last_edit_workstation?

Joan Kranich (jkranich) wrote :

Both the creating_workstation and last_edit_workstation columns would be helpful.

Michele Morgan (mmorgan) on 2019-02-08
Changed in evergreen:
status: New → Confirmed
assignee: nobody → Michele Morgan (mmorgan)
Elaine Hardy (ehardy) on 2019-03-07
tags: added: patron wishlist
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers