bib record merges should mark bib inactive

Bug #1771386 reported by Rogan Hamby
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Medium
Unassigned
3.1
Won't Fix
Undecided
Unassigned
3.2
Won't Fix
Undecided
Unassigned
3.3
Won't Fix
Undecided
Unassigned
3.4
Fix Released
Medium
Unassigned

Bug Description

When the biblio record entry delete command is issued the bib is both flagged as deleted and inactive. The asset.merge_record_assets function is only marking it deleted but not inactive. Both should be done for consistency.

Changed in evergreen:
assignee: nobody → Rogan Hamby (rogan-hamby)
Revision history for this message
Garry Collum (gcollum) wrote :

While confirming this bug I found a related issue that may require a separate LP entry.

If you undelete a bib in the xul client, active is set to true, deleted is set to false. If you undelete a bib in the web client, active remains false, deleted is set to false.

Changed in evergreen:
status: New → Confirmed
Revision history for this message
Rogan Hamby (rogan-hamby) wrote :

Branch for this issue at user/rogan/lp1771386_merged_bib_should_be_inactive, 7df1f00a2466324feee56cf0ca89a4d82023dcbf

Garry, did you file a launchpad bug for the webclient undelete behavior?

tags: added: pullrequest
Kathy Lussier (klussier)
Changed in evergreen:
assignee: Rogan Hamby (rogan-hamby) → nobody
tags: added: cataloging
Revision history for this message
Michele Morgan (mmorgan) wrote :
Changed in evergreen:
milestone: none → 3.3-rc
Changed in evergreen:
milestone: 3.3-rc → 3.3.1
Revision history for this message
Beth Willis (willis-a) wrote :

 I have tested this code and consent to signing off on it with my name, Beth Willis and my email address, <email address hidden>

tags: added: signedoff
Changed in evergreen:
milestone: 3.3.1 → 3.3.2
Changed in evergreen:
milestone: 3.3.2 → 3.3.3
Changed in evergreen:
milestone: 3.3.3 → 3.3.4
Changed in evergreen:
milestone: 3.3.4 → 3.3.5
Changed in evergreen:
milestone: 3.3.5 → 3.4.2
Changed in evergreen:
milestone: 3.4.2 → 3.4.3
Changed in evergreen:
milestone: 3.4.3 → 3.4.4
Changed in evergreen:
milestone: 3.4.4 → 3.5.1
importance: Undecided → Medium
Changed in evergreen:
milestone: 3.5.1 → 3.5.2
Revision history for this message
Jane Sandberg (sandbergja) wrote :

Thanks for the patch, Rogan, and for the testing, Beth. It works well for me also.

I'll be happy to merge this, but it's missing a few things:
* Rogan's signoff is missing from the original commit
* Commit message should start with the bug number
* Upgrade script should be wrapped in a transaction, with the evergreen.upgrade_deps_block_check line included

Revision history for this message
Rogan Hamby (rogan-hamby) wrote : Re: [Bug 1771386] Re: bib record merges should mark bib inactive

Time is my enemy and git amend is not cooperating for --signoff so since no
one actually signed off in git to the previous branch just via launchpad ...

https://git.evergreen-ils.org/?p=working/Evergreen.git;a=commit;h=465b55bfb71ec70675d8e969d1134c726aeccdee

On Thu, Aug 20, 2020 at 12:15 PM Jane Sandberg <email address hidden>
wrote:

> Thanks for the patch, Rogan, and for the testing, Beth. It works well
> for me also.
>
> I'll be happy to merge this, but it's missing a few things:
> * Rogan's signoff is missing from the original commit
> * Commit message should start with the bug number
> * Upgrade script should be wrapped in a transaction, with the
> evergreen.upgrade_deps_block_check line included
>
> --
> You received this bug notification because you are a member of Evergreen
> Bug Wranglers, which is subscribed to Evergreen.
> https://bugs.launchpad.net/bugs/1771386
>
> Title:
> bib record merges should mark bib inactive
>
> Status in Evergreen:
> Confirmed
> Status in Evergreen 3.1 series:
> Won't Fix
> Status in Evergreen 3.2 series:
> Won't Fix
> Status in Evergreen 3.3 series:
> Won't Fix
> Status in Evergreen 3.4 series:
> Confirmed
>
> Bug description:
> When the biblio record entry delete command is issued the bib is both
> flagged as deleted and inactive. The asset.merge_record_assets
> function is only marking it deleted but not inactive. Both should be
> done for consistency.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/evergreen/+bug/1771386/+subscriptions
>

Changed in evergreen:
status: Confirmed → Fix Committed
Revision history for this message
Jane Sandberg (sandbergja) wrote :

Forgot to comment that I had merged this to rel_3_4, rel_3_5, and master. Thanks, Rogan and Beth.

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.