Evergreen

Holding maintenance bug when going from Item Status > View In Catalog > Holding Maintenance

Bug #829630 reported by Steve Callender on 2011-08-19

This bug affects 4 people

	Status	Importance	Assigned to
Evergreen	Invalid	Medium	Unassigned
2.3	Won't Fix	Medium	Unassigned
2.4	Won't Fix	Medium	Unassigned

Bug Description

I tested this on 2.0.7. Ways to duplicate the problem,

Load a couple items into the item status screen, highlight both of them and select "Show In Catalog". Two new tabs will open with catalog views of each item, as expected. Then on each tab, go to "Actions for this Record" and select "Holdings Maintenance".

The first tab that opened for the catalog view (The one on the left) will have a proper holding maintenance screen. The second one, will load a maintenance screen with nothing in the location box. The header of the screen and information up top will be present, but no locations will load.

It looks like when doing multiple items, whatever it is behind the scenes that the system holds onto for holdings information is saved only for the first item that opens.

Revision history for this message

Steve Callender (stevecallender) wrote on 2012-01-13:

I can also make this happen with record buckets. When I have items in a record bucket, and choose to "Show All in Catalog" the same behavior happens. Looking at the items in the OPAC view, only the first item will have title information and subject information. Only the first item will have holdings information when going to the holdings screen.

Revision history for this message

Chris Sharp (chrissharp123) wrote on 2012-01-13:

We can confirm this behavior in PINES. We can provide more details if desired.

EG 2.1.1
PG 9.1
Debian squeeze

Revision history for this message

Sarah Childs (sarahc) wrote on 2012-01-26:

Yes, we're seeing this in Indiana, too. Also, I've noticed the same behavior with the View Holds screen. When you "Show in Catalog" from Item Status, the holds display for the first item shown, but they don't show for the other records.

EG 2.1.1

Jason Stephenson (jstephenson) on 2012-02-21

Changed in evergreen:
status:	New → Confirmed
importance:	Undecided → Medium

Revision history for this message

James Fournie (jfournie) wrote on 2012-07-23:

Here's a fix courtesy Steven Chan of Sitka

user/jamesrf/lp829630_show_in_catalog

tags:

added: pullrequest

Revision history for this message

Lebbeous Fogle-Weekley (lebbeous) wrote on 2012-07-30:

Thanks all.

Steven, this is the second commit of yours I've merged recently. I'm glad to see a bigger set of names in the commit log. Going forward, remember to sign-off your own commits, and also, why not get a Launchpad account and comment here directly?

I have merged this to master, rel_2_2 and rel_2_1.

Changed in evergreen:
status:	Confirmed → Fix Committed
milestone:	none → 2.3.0-beta1

Revision history for this message

Sarah Childs (sarahc) wrote on 2012-09-19:

We went live with 2.2 this week in Indiana, and I'm still experiencing this same issue. Any thoughts?

Jason Stephenson (jstephenson) on 2012-09-19

Changed in evergreen:
status:	Fix Committed → Fix Released

Revision history for this message

Lebbeous Fogle-Weekley (lebbeous) wrote on 2012-10-03:

It seems when I committed the patch offered, I tested it based on the expectations set in the commit message, which states that it aims to fix this error message only in the patron bills interface, not in the holdings maintenance interface or the view holds interface.

The problem is definitely fixed in the patron bills interface, but may persist in the other places, in which case we'll need a different patch.

Changing status of this bug back to incomplete.

Changed in evergreen:
status:	Fix Released → Incomplete

Jason Stephenson (jstephenson) on 2012-12-12

Changed in evergreen:
status:	Incomplete → Triaged

Ben Shum (bshum) on 2012-12-23

tags:

removed: pullrequest

Ben Shum (bshum) on 2013-01-16

Changed in evergreen:
milestone:	2.3.0-beta1 → 2.4.0-alpha

Ben Shum (bshum) on 2013-03-03

Changed in evergreen:
milestone:	2.4.0-alpha1 → 2.4.0-beta

Ben Shum (bshum) on 2013-03-17

Changed in evergreen:
milestone:	2.4.0-beta → 2.4.0-rc

Ben Shum (bshum) on 2013-04-27

Changed in evergreen:
milestone:	2.4.0-rc → none

Ben Shum (bshum) on 2013-08-22

no longer affects:	evergreen/2.1
no longer affects:	evergreen/2.2

Revision history for this message

Remington Steed (rjs7) wrote on 2013-11-27:

I am not able to reproduce this in 2.5. Is anyone else still seeing this bug?

Revision history for this message

Michele Morgan (mmorgan) wrote on 2014-11-10:

Unable to reproduce this on 2.6 either.

Jason Stephenson (jstephenson) on 2014-11-10

Changed in evergreen:
status:	Triaged → Invalid

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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