Batch Importer (Bib/Acq)
(UXPROD-47)
|
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | TBD | Parent: | Batch Importer (Bib/Acq) |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Ann-Marie Breaux (Inactive) | Assignee: | Ryan Taylor |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | data-import, epam-folijet, loc, needs-t-shirt-size-BE | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||
| Potential Workaround: | Use the Q3 2020 functionality of only updating specific fields in the SRS MARC, instead of updating all fields | ||||||||||||
| Release: | Not Scheduled | ||||||||||||
| Epic Link: | Batch Importer (Bib/Acq) | ||||||||||||
| Front End Estimate: | Small < 3 days | ||||||||||||
| Development Team: | Folijet | ||||||||||||
| Kiwi Planning Points (DO NOT CHANGE): | 2 | ||||||||||||
| PO Rank: | 75 | ||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R5 | ||||||||||||
| Rank: Chicago (MVP Sum 2020): | R1 | ||||||||||||
| Rank: Cornell (Full Sum 2021): | R4 | ||||||||||||
| Rank: Duke (Full Sum 2021): | R1 | ||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R3 | ||||||||||||
| Rank: FLO (MVP Sum 2020): | R4 | ||||||||||||
| Rank: GBV (MVP Sum 2020): | R4 | ||||||||||||
| Rank: Grand Valley (Full Sum 2021): | R4 | ||||||||||||
| Rank: MO State (MVP June 2020): | R3 | ||||||||||||
| Rank: TAMU (MVP Jan 2021): | R3 | ||||||||||||
| Rank: U of AL (MVP Oct 2020): | R3 | ||||||||||||
| Description |
|
Split from
Purpose: To import data for Inventory or Acquisitions via a MARC record, but then do not save the MARC record in SRS Sample use cases:
As a staff person working with imported files From 9/23/20 Folijet grooming mtg:
|
| Comments |
| Comment by Ann-Marie Breaux (Inactive) [ 16/Sep/20 ] |
|
Hi Oleksii Kuzminov and Ivan Kryzhanovskyi I split this feature from
|
| Comment by Ann-Marie Breaux (Inactive) [ 04/Feb/21 ] |
|
Hi Karen Newbery, Christie Thomas, Raegan Wiechert I see that your libraries have ranked this as R1 - could you provide an example or two of the most urgent use cases from your library? I'm working on planning for the next round of Data Import work, and trying to understand how to weigh this against other pressing work. Thank you! |
| Comment by Christie Thomas [ 04/Feb/21 ] |
|
Ann-Marie Breaux The first two use cases that come to mind are to create brief record for circulating objects that are not a part of the collection. (Such as laptops, power cords, etc.) We would not want to store the MARC for those, but we would have to load the data via a MARC file. The workaround for this is to create the files manually. The second use case is for batch edits. If I want to add a statistical code or change the instance status for a batch of instance records, I must target the instance records with a MARC import file. If there is already a MARC record associated with the instance, then I can export the MARC record and re-import and overlay the MARC record without making any changes and tack on the batch changes that I need to make for the instance record. If there is no MARC record associated with the instance (such as for orders, circulating objects, etc.) then I would need to create a MARC record for the instance just to be able to make those updates in batch. |
| Comment by Raegan Wiechert [ 04/Feb/21 ] |
|
We have lowered our ranking to R3. We believe the R1 was probably left over from before this was split off of 2338. |