MARCcat: MARC Bibliographic records
(UXPROD-786)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | MARCcat: MARC Bibliographic records |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Tiziana Possemato | Assignee: | Tiziana Possemato |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | MARCcat-Bib, po-mvp, record_delete | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||
| Epic Link: | MARCcat: MARC Bibliographic records | ||||||||||||||||||||||||
| Development Team: | @cult | ||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R5 | ||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R5 | ||||||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R5 | ||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R5 | ||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R5 | ||||||||||||||||||||||||
| Rank: Lehigh (MVP Summer 2020): | R4 | ||||||||||||||||||||||||
| Rank: MO State (MVP June 2020): | R4 | ||||||||||||||||||||||||
| Rank: TAMU (MVP Jan 2021): | R4 | ||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R4 | ||||||||||||||||||||||||
| Description |
|
Mark a bibliographic record for future deletion in the system. Flag on the record to allow it to be deleted in the future |
| Comments |
| Comment by Kristin Martin [ 14/Aug/19 ] |
|
Chicago requires more information before ranking. Is this about deleting the MARC record without deleting the attached instance record? If it is about deleting the Inventory - SRS MARC - MarcCat triumvirate of records, then that should happen via Inventory and not MarcCat. |
| Comment by Tiziana Possemato [ 05/Sep/19 ] |
|
Hi Kristin Martin, I try to describe the function. In MARCcat I decide to delete a bibliographic record, for any reason. Because the record in MARCcat is linked to other objects (=records) in other components/APPs (Inventory, SRS...), the first step (described in this UXPROD feature) is 'to mark' a bib record available for Deletion. Linked to this is the https://folio-org.atlassian.net/browse/UXPROD-1962, that is the logical 'next step': after marked as 'available for delation' this record can be really deleted. |
| Comment by Charlotte Whitt [ 09/Sep/19 ] |
|
Hi Tiziana Possemato - at the MM-SIG meeting last week (9/5/2019) - https://folio-org.atlassian.net/wiki/display/MM/2019-09-05+Metadata+Management+Meeting+notes - we talked about deletion of instance (bibs) records in Inventntory and maybe in MARCcat.
|
| Comment by Tiziana Possemato [ 09/Sep/19 ] |
|
Hi Charlotte Whitt, thanks. This means that we need to define some use cases in MARCcat to delete a bib records? Consider that this specific issue (
|
| Comment by Annalisa Di Sabato [ 25/Sep/19 ] |
|
Some questions about the check "Mark for deletion": 1. I'm in inventory, on an instance that has a MARC record associated. If I mark the instance record for deletion, should this check be updated and also visible in the related MARC record, in MARCcat? and viceversa 2. I'm in MARCcat, on a MARC record that has an instance record associated. If I mark the MARC record for deletion, should this check be updated and also visible in the related instance record, in Inventory? |
| Comment by Annalisa Di Sabato [ 18/Mar/20 ] |
|
To indicate the deletion of a record in MARCcat we will use the value "d" of the position 5 of the Leader, which means "Deleted". There will be a checkbox in the record to mark the record for deletion. When the user selects it, position 5 of the leader will be automatically updated with the value "d". We postponed this issue to Q4 2020, because at the moment the user is already able to change the position 5 of the leader and update the staus of the record (as workaround). |
| Comment by Ann-Marie Breaux (Inactive) [ 19/Jun/20 ] |
|
Do not clone for holdings or authorities at this time |
| Comment by Ann-Marie Breaux (Inactive) [ 19/Jan/21 ] |
|
As of Jan 2021, development of MARCcat has ceased. Will incorporate some features into quickMARC. |