Single MARC Record Integration with OCLC
(UXPROD-211)
|
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | TBD | Parent: | Single MARC Record Integration with OCLC |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Ann-Marie Breaux (Inactive) | Assignee: | Ryan Taylor |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | epam-folijet, inventory-single-record-import | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||
| Release: | Not Scheduled | ||||||||||||||||||||
| Epic Link: | Single MARC Record Integration with OCLC | ||||||||||||||||||||
| Development Team: | Folijet | ||||||||||||||||||||
| Kiwi Planning Points (DO NOT CHANGE): | 15 | ||||||||||||||||||||
| PO Rank: | 0 | ||||||||||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R5 | ||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R2 | ||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R2 | ||||||||||||||||||||
| Rank: MO State (MVP June 2020): | R2 | ||||||||||||||||||||
| Rank: TAMU (MVP Jan 2021): | R2 | ||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R1 | ||||||||||||||||||||
| Description |
|
Initial work was completed in
Some proposed additional functionality:
NOTE: Any of these refinements need to be coordinated with Data Import Dev Team to ensure the supporting work is coordinated |
| Comments |
| Comment by Tom Wilson [ 12/Mar/21 ] |
|
"See linked stories"? Where are the links? |
| Comment by Ann-Marie Breaux (Inactive) [ 15/Mar/21 ] |
|
Hi Tom Wilson So far there's only one -
|
| Comment by Jennifer Eustis [ 15/Jun/22 ] |
|
It would be great to have the instance HRID messaged back to Connexion after export so that Connexion can display this in the Export Results window. For push, how will duplicate OCLC numbers be handled? Will the export just fail? |
| Comment by Lynne Fors [ 15/Jun/22 ] |
|
I agree with Jennifer Eustis that having the Instance HRID sent back to Connexion would be great. It definitely would save time doing a search in Inventory by title/author to find the record if all I had to to was copy the HRID and paste it into the search box. For duplicate OCLC numbers, it would be great if Folio could pass back a message saying something along the lines of Failed - Multiple matches detected. I know that other systems (ex. Alma) do this and it's extremely helpful in troubleshooting why the import failed. |
| Comment by Ann-Marie Breaux (Inactive) [ 15/Jun/22 ] |
|
Hi Jennifer Eustis and Lynne Fors All good questions and suggestions. Good to have them here in the Jira for when this work may be prioritized. Currently, I don't see it targeted for a specific release by the development team. |
| Comment by Ann-Marie Breaux (Inactive) [ 16/Jun/22 ] |
|
Additional info from a convo on Slack: Jennifer Eustis: Jessica Janecki Ann-Marie Breaux Charlotte Whitt Ann-Marie Breaux |
| Comment by Molly Driscoll [ 05/Aug/22 ] |
|
Additional information from conversation on Slack: Molly Driscoll: Does anyone know if the Library of Congress Z39.50 target profile can be configured to import only if the entered value appears in the 010$a? I've had some occurrences of it importing a record where the LCCN value I enter is in the 010$z. Jakub Skoczen: I don't think so because the z3950 configuration is done via Bib1 attributes and how those attributes are mapped to MARC fields is controlled internally in the LoC z3950 server
Adding this here in case this feature leaves room for additional investigation.
|
| Comment by Lisa Sjögren [ 08/Feb/23 ] |
|
One enhancement that many libraries I've spoken, who are using Single Record Import to pull records into FOLIO, to is to be able to perform a search and select the record to import from a result list in the SRI dialogue. Currently, a librarian needs to first go into the interface of the catalog from which they wish to import the record, perform a search to identify a suitable record, copy the unique identifier, and then paste this into the identifier box in Single Record Import. The workflow would be much more efficient if the library could search for, select from a list, and import record within FOLIO. This functionality exists in other common ILSs such as Koha and III Sierra. |
| Comment by Charlotte Whitt [ 05/Dec/23 ] |
|
Hi Ann-Marie Breaux- I removed Mjolnier as development team, and assigned this to feature to the FOLJIET dev team |
| Comment by Ann-Marie Breaux (Inactive) [ 05/Dec/23 ] |
|
Hi Charlotte Whitt That's fine - no worries. We'll just put it in the Folijet backlog for now. Thank you! cc: Ryan Taylor |