Update 005 field when set MARC for deletion

Description

In current implementation when Instance is set for deletion it is:

  • Set instance flag for Staff suppress

  • Set instance flag for Suppress from discovery

  • If source = MARC, set Leader byte to d

Export deleted MARC bib records retrieves deleted records based on LDR05 and 005.date values based on results of MARC Search

As 005 field is not updated when MARC set for deletion => That MARC does not appear in MARC Search for the date then it was set for deletion => That MARC does not appear in export of deleted MARC bib records for the date then it was set for deletion

Steps to reproduce (Sprint testing environment):

  1. Go to “Inventory“ app

  2. Find MARC Instance that is not deleted

  3. Click Actions > View source

  4. Check 005 field

  5. Click Actions > Set record for deletion

  6. Click Confirm

  7. Click Actions > View source

  8. Check 005 field

Expected result: LDR05 set to “d“. Field 005 updated with current date

Actual result: LDR05 set to “d“. Field 005 is NOT updated

Additional information:

MARC Search doesn’t search MARC set for deletion on current date

Potential Workaround

None

CSP Request Details

None

CSP Approved

None

CSP Rejection Details

None

Attachments

6

Checklist

hide

Activity

Show:

Ryan Taylor August 1, 2024 at 3:47 PM

Confirmed to be working as expected in Snapshot. Closing ticket.

Maksym Ishchenko July 30, 2024 at 10:54 AM

Hi

Ticket verified on snapshot env. Now 005 updating after deleting record. Moving ticket further

Before delete:

After delete:

cc:

Ryan Taylor July 24, 2024 at 3:47 PM

- Confirming that we should move forward with Natural Numerical ordering (i.e. 001,005,006,007,008 etc), Thank you!

Volodymyr Rohach July 19, 2024 at 11:53 AM

Hello ! I have a question about this ticket. So where should the 005 field situated after setting MARC-record for deletion? I placed in the natural order (001,005,006,007,008 etc) BUT it seems like we have another order in for example, update MARC imports (the imports where MARC-records should be updated in Job Profiles). So which way should I choose? The natural ordering(with sorting), or without ordering, but consistency via MARC-update functionality (001,006,007,008,005 etc) ? I attached 2 screenshots. Thank you in advance!

CC:

 

 

Done

Details

RCA Group

Incomplete/missing requirements

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Folijet

Fix versions

Release

Ramsons (R2 2024)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created July 1, 2024 at 2:39 PM
Updated October 28, 2024 at 5:09 PM
Resolved August 1, 2024 at 3:47 PM
TestRail: Cases
TestRail: Runs