Comment 18 for bug 1387722

Interesting. I’ll take another look at this with 856s.

On Wed, May 2, 2018 at 01:17 Ben Shum <email address hidden> wrote:

> Okay, I reverted this change because it was causing unexpected problems
> elsewhere with the perl livetests.
>
> Apparently, the URI triggers are seemingly being run twice. This led to
> concerto dataset getting busted with extra rows for call numbers, which
> shifted all the copies, making all the live tests unhappy. I don't
> think we want the database to be churning extra runs of the asset.uri
> creation/deletion, so let's look at this more closely.
>
> Removing pullrequest and adding repatch note.
>
> --
> You received this bug notification because you are subscribed to
> Evergreen.
> Matching subscriptions: evergreenbugs
> https://bugs.launchpad.net/bugs/1387722
>
> Title:
> Bibliographic record merging should update the MARC leader when
> deleting a record
>
> Status in Evergreen:
> Incomplete
>
> Bug description:
> Evergreen version: 2.6
>
> When merging bib records, in the Leader, position 05 - Record Status
> of the deleted record, the code is not changed to "d," for deleted, as
> it is when a record is simply deleted within the client.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/evergreen/+bug/1387722/+subscriptions
>