Evergreen

Add Copy Active Date to Staff Client Display

Bug #1366026 reported by Jason Boyer
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Wishlist
Unassigned
Evergreen 2.8-beta

Bug Description

There is an option for age protection to use the active date for a copy rather than the create date, but there is no good way to see what this date is when looking at the opac in the staff client. If the gap between the create and active date is large this can cause confusion for staff when trying to determine when a hold might no longer be prohibited due to age protection. I'm already working on a branch that will display the active or create date based on the copy's circ lib circ.holds.age_protect.active_date setting.

Revision history for this message
Jason Boyer (jboyer) wrote :

Branch here: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/jboyer/lp1366026_active_date

It's been tested on a 2.5.2 system, but the changes apply cleanly to master also. If an active date doesn't exist for an item the create date is used anyway.

Revision history for this message
Kathy Lussier (klussier) wrote :

Hi Jason,

Could you add a release notes entry for this?

Thanks!
Kathy

Changed in evergreen:
status: New → Triaged
importance: Undecided → Wishlist
tags: added: needsreleasenote
Revision history for this message
Michele Morgan (mmorgan) wrote :

Tested this in stock Evergreen and with production data and it works as described. We may consider a catalog customization to break the Active and Create dates out into separate columns, but this is a great help when items have age hold protection.

Here's my signoff:
http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/mmorgan/LP1366026_Active_Date_signoff

Our libraries will really appreciate this!

tags: added: signedoff
Revision history for this message
Ben Shum (bshum) wrote :

Waiting for the release note before pulling into master.

Changed in evergreen:
milestone: none → 2.next
status: Triaged → Incomplete
Revision history for this message
Kathy Lussier (klussier) wrote :

I added a release notes entry and also rebased the branch to resolve a conflict in copy_table.tt2

Changed in evergreen:
status: Incomplete → Triaged
tags: added: pullrequest
removed: needsreleasenote
Galen Charlton (gmc)
Changed in evergreen:
milestone: 2.next → 2.8-beta
assignee: nobody → Galen Charlton (gmc)
Revision history for this message
Galen Charlton (gmc) wrote :

Pushed to master for inclusion in the 2.8 beta. Thanks, Jason!

Changed in evergreen:
status: Triaged → Fix Committed
assignee: Galen Charlton (gmc) → nobody
Evergreen Bug Maintenance (bugmaster)
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.