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: | P3 |
| Reporter: | Annalisa Di Sabato | Assignee: | Tiziana Possemato |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | MARCcat-Bib, data-import, fields_protection, round_iv | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||
| Epic Link: | MARCcat: MARC Bibliographic records | ||||||||||||||||||||
| Development Team: | @cult | ||||||||||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R5 | ||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R4 | ||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R4 | ||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R1 | ||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R1 | ||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R5 | ||||||||||||||||||||
| Rank: hbz (TBD): | R1 | ||||||||||||||||||||
| Rank: Lehigh (MVP Summer 2020): | R1 | ||||||||||||||||||||
| Rank: MO State (MVP June 2020): | R1 | ||||||||||||||||||||
| Rank: TAMU (MVP Jan 2021): | R2 | ||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R1 | ||||||||||||||||||||
| Description |
|
Must be able to protect institutional selected/allocated fields from being overwritten when marc records are overlayed. |
| Comments |
| Comment by Jason Kovari [ 21/Aug/19 ] |
|
Field protection should governed by data import for batch processes / operations. Would individual OCLC pushes not be part of that mapping logic? OR can we define when MARCcat would have different logic from other import functions? Ann-Marie Breaux : Is this a correct assumption re: data import? |
| Comment by Ann-Marie Breaux (Inactive) [ 19/Jan/21 ] |
|
As of Jan 2021, development of MARCcat has ceased. Will incorporate some features into quickMARC. |