Web Client: deleted records not highlighted on merge screen

Bug #1746611 reported by tji@sitka.bclibraries.ca on 2018-01-31
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Evergreen
Undecided
Unassigned

Bug Description

Web Client EG 3.0.2

On merge record screen via Record Bucket, deleted bibs are no longer highlighted.

On XUL client, the Record Summary (View MARC) line on top of each record has red background.

Elaine Hardy (ehardy) on 2018-02-01
Changed in evergreen:
status: New → Confirmed
Janet Schrader (jschrader) wrote :

One thing I like about merging records in the web client is that you can *select* records to merge while in the xul client it's merge *all* records. Being able to select is nice because you may have forgotten to remove merged records before adding new ones to a bucket.

One thing I do NOT like about merging records in the web client is that there is no indication that a merge has already been done (see above) because there is no indication that one of the set has been deleted. Without the record summary appearing (see bug 1739292), there is no place to indicate the deleted record.

Maybe #1739292 could be merged with this bug as the missing record summary and the red highlighting of the summary for deleted record both have to do with wanting the record summary back in the merge record display.

Web client 3.0.9
Browser Chrome

Janet Schrader (jschrader) wrote :

I added tag regression as this behavior exists in the xul client and but is lost in the web client. Hopefully regressive behavior is addressed sooner.

Janet Schrader (jschrader) wrote :

Also added tag cataloging and webstaffclient.

Janet Schrader (jschrader) wrote :

Okay, added tags again and included 'regression', forgot to save them the first time. :(

tags: added: cataloging regression webstaffclient
Bill Erickson (berick) wrote :

I'll grab this one after bug #1776736 is merged, so I can build atop it / avoid merge conflicts.

Janet Schrader (jschrader) wrote :

Thank you! This one has been bugging me for a long time. :)

Does any of this development include bug #1739292?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers