Webstaff: z39.50 doesn't stay up-to-date on which record is marked for overlay

Bug #1710401 reported by Jane Sandberg
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Low
Unassigned
3.1
Fix Released
Undecided
Unassigned

Bug Description

Steps to recreate in Evergreen 2.12:

1) In tab 1, Mark a record for overlay (say TCN 123) in the Web staff client.
2) In tab 2, go to Cataloging > Import Record from Z39.50. This screen will note that TCN 123 is marked for overlay.
3) In tab 1, Go to a different record (say TCN 456) and mark it for overlay.
4) In tab 2, the Z39.50 screen will still think 123 is marked for overlay.
5) In tab 2, click Overlay. Record 123 will be overlaid with the z39.50 record, instead of 456.

It would be preferable if the Web staff client offered some warning somewhere in step 5 that it's not overlaying the record that was most recently marked for overlay.

tags: added: webstaffclient
Revision history for this message
Elaine Hardy (ehardy) wrote :

In order to get the Z39.50 tab to update the newly marked for overlay target, you have to refresh the tab. If you have already searched, you lose your search.

Would also like the record to be unmarked for overlay once it has been overlaid, as it currently does in the XUL client. The record marked persists across sessions.

Revision history for this message
Andrea Neiman (aneiman) wrote :

3.0 beta, confirmed as outlined by Jane.

Elaine, the record-unmarking issue is discussed in bug 621459.

Changed in evergreen:
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Elaine Hardy (ehardy) wrote :

Andrea that bug is from 2010 and isn't for the web client...

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

Bug 621459 was indeed filed in 2010, but discussion about the web client behavior begins in comment 3.

Revision history for this message
Andrea Neiman (aneiman) wrote :

I linked it because there is relevant discussion in the comments, starting with Jane's comment #3

Revision history for this message
Sarah Childs (sarahc) wrote :

This really screws with my workflow, which is to search the local catalog and OCLC simultaneously via z39.50, examine any local records, and then I almost always overlay them with the OCLC record. I show in catalog, and mark for overlay. In the web client, I have to refresh the screen and perform the search again before I can overlay. This pretty much renders the simultaneous search pointless, since I have to do almost every search twice anyway.

Revision history for this message
Elaine Hardy (ehardy) wrote :

In the web client, rather than keeping a tab open for Z39.50, I close it as soon as I overlay and only open it after I mark a record. It slows down my workflow considerably but does prevent that second search.

There are times however, when I I am making changes to different iterations of the same title where it would be preferable to do one search to find OCLC records for multiple records for overlay within my local system. For example, if both the print and audio versions of a title need updated records, in the XUL client, I could do one search and them overlay the print record first. Then mark the audio record for overlay and go back to my Z30.50 tab, choose the correct audio record and overlay. Cannot do that in the web client.

Revision history for this message
Mike Rylander (mrylander) wrote :

I've pushed a branch to address this here: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/miker/lp-1710401-z3950-overlay-record

From the commit message:

Currently, we record the overlay target at UI startup and use that going forward until the interface is reloaded. This commit inspects the local storage version of the target for changes and offers the user the chance to proceed with the new target or cancel the action. If the target has been unset, the user is given the option of proceeding with the load-time target.

tags: added: pullrequest
Revision history for this message
Mike Rylander (mrylander) wrote :

I've added this to the bugsquash server https://dev-bugsquash.equinoxinitiative.org/eg/staff/ (egadmin/dem0123!).

Revision history for this message
Elaine Hardy (ehardy) wrote :

Chris added to PINES test server and I tested there.

Tab 1: Search for record and mark for overlay​​ [keep tab open]
Open Z39.50 in Tab 2​ Search for record in OCLC and overlay [keep tab open]

Tab 1​ : Search for another record and mark for overlay [keep tab open]
Tab 2 : Note for record marked still 1st one. Search for record in Z39.50 interface, highlight and choose Actions -- overlay. Dialog box informing me that overlay target changed, with correct Record IDs. Have option to continue or cancel. Continue. Correct record is overlaid [keep tab open]

Tab 1 search and retrieve another record. Mark for overlay [keep tab open]
Tab ​​​2: Search for record in Z39.50. Choose overlay. Dialog box informs that target has been changed, however If I click OK/continue expected record is in target position and overlay is correct.

Target in Z39.50 does update if tab is reloaded, or Z39.50 closed and reopened.

(stray " at end of target record note on Z39.50 interface: Record with TCN 5058389 marked for overlay.")

Revision history for this message
Elaine Hardy (ehardy) wrote :

I also tried this using the bugsquash server and got the same results.

Revision history for this message
Mike Rylander (mrylander) wrote :

Hi Elaine,

Just to be clear, am I correctly reading your test description as successful?

Note: we cannot currently notice, immediately, when the target is changed in another tab -- we have to wait for user action, but we check then and present the prompts you saw.

Revision history for this message
Elaine Hardy (ehardy) wrote :

Yes, it was successful -- overlays were for the correct records. I just did 3 in a row but they all were successful, both in terms of the prompts and in the record overlaid.

Just to note, I would prefer that the TCN be used rather than the record ID, as in the XUL client.

Revision history for this message
Chris Sharp (chrissharp123) wrote :

Works for us!

Pushed to master, rel_3_0, and rel_3_1.

Changed in evergreen:
status: Confirmed → Fix Committed
milestone: none → 3.0.10
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.

Other bug subscribers

Remote bug watches

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