Batch Importer (Bib/Acq) (UXPROD-47)

[UXPROD-1479] Simple UI for edit of the default MARC mapping of bibliographic records Created: 24/Jan/19  Updated: 28/Dec/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: TBD
Parent: Batch Importer (Bib/Acq)

Type: New Feature Priority: P3
Reporter: Charlotte Whitt Assignee: Ryan Taylor
Resolution: Unresolved Votes: 0
Labels: data-import, inventory, marc-bib, marccat, metadatamanagement, migration-load, q4-2019-at-risk, q4-2019-spillover, round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File screenshot-1.png    
Issue links:
Defines
defines UXPROD-47 Batch Importer (Bib/Acq) Analysis Complete
Relates
relates to MODSOURMAN-181 Create CLI way for individual tenant ... Closed
relates to UXPROD-665 Import Inventory Instances and MARCca... Closed
relates to UXPROD-2075 MARC Bib Field Mapping Profiles Detai... Closed
relates to UXPROD-2078 SRS MARC-Inventory Instance relations... Closed
relates to UXPROD-149 Create Instance records from a MARC b... Closed
relates to UXPROD-2207 SRS MARC-Inventory Instance relations... Closed
relates to UXPROD-1860 Migration. Simple UI for edit of the ... Draft
Potential Workaround: Use the CLI mapping tool instead. The UI version feels like more of a "nice to have" than required to me, since the default mapping should only need to be updated once, at the beginning of migration. I don't think it needs to be cap-mvp any more (A-M)
Release: Not Scheduled
Epic Link: Batch Importer (Bib/Acq)
Analysis Estimate: Medium < 5 days
Analysis Estimator: Charlotte Whitt
Front End Estimate: XXL < 30 days
Front End Estimator: Taras Tkachenko
Front-End Confidence factor: Low
Back End Estimate: Large < 10 days
Back End Estimator: Oleksii Kuzminov
Development Team: Folijet
Kiwi Planning Points (DO NOT CHANGE): 7
PO Rank: 69
PO Ranking Note: Lowered the ranking after discussion with Data Import subgroup. CLI tool is a good enough workaround for cap-mvp (MODSOURMAN-180)
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): R2
Rank: FLO (MVP Sum 2020): R1
Rank: GBV (MVP Sum 2020): R5
Rank: hbz (TBD): R4
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R1
Rank: Leipzig (Full TBD): R1
Rank: MO State (MVP June 2020): R1
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): R1

 Description   

Simple UI for libraries to tweak the default MARC mapping, and prepare the conversion of the libraries catalog to Inventory, FOLIO format.
Currently default is documented in spreadsheet form. If easy to reuse the Data Import Field Mapping, then that is good too.

Aleph has a UNIX table, can be edited as text – either a table like this or a spreadsheet would likely be adequate for migration except for complex logic.
Syntax for complex mapping logic should follow syntax being used in Data Import.

For ongoing mapping changes, investigate adapting UI being developed for Data Import.

Documented in:

Ann-Marie Breaux When this feature is worked on, check in with Eric Frierson



 Comments   
Comment by Charlotte Whitt [ 22/May/19 ]

Hi patty.wanninger and Ann-Marie Breaux - this feature might be highly relevant to get into the Q3, or Q4 2019 planning schedule, to support the sandbox work and/or planned migration of bibliographic data for the early implementers. Or what's your thoughts?

CC: Cate Boerema

Comment by patty.wanninger [ 22/May/19 ]

I agree that being able to tweak the map would be great, but I am not sure how it fits in with Ann-Marie Breaux's tool. Alex Soto and I discussed that it will be the old 80-20 rule - 80% of the map will be the same for everybody but they will care about the 20% very much.

Comment by lew235 [ 08/Jul/19 ]

For migration a spreadsheet or table format (text file) might be adequate.
For ongoing mapping editing we will need something more user friendly--the interface being developed for Data Import might be adaptable for this.

Comment by Ann-Marie Breaux (Inactive) [ 08/Jul/19 ]

Charlotte Whitt and Ann-Marie Breaux to figure out whether this can be accommodated by Core-Fxn or Folijet once Folijet field mappings have been completed (in Q3); aim for early Q4 at the latest, at least for CLI version

Comment by Ann-Marie Breaux (Inactive) [ 10/Jul/19 ]

Hi Charlotte Whitt I think this fits with my work better than Inventory. At our ACT mtg earlier this week, we talked about having this be in MARC settings or something like that, rather than anywhere in Inventory settings. OK if I change it to me? And I'll probably split this into 2 features: 1 for CLI, 1 for UI

Comment by Ann-Marie Breaux (Inactive) [ 02/Oct/19 ]

Slack Conversation:

Ann-Marie Breaux:
We are in the process of building a CLI tool for adjusting the default MARC-to-Instance mappings, and should have it completed in this sprint or next. It will be a little tricky because the default mappings setup document is pretty huge, so picking your way through to make some adjustments will take some effort. BUT: we expect that an individual tenant would only have to do this work once during initial FOLIO setup, when they are establishing their MARC-Instance preferences.

There is a separate feature ( UXPROD-1479 Draft ) which is a simple UI for changing those mappings. That was ranked highly and go-live by many institutions. My inclination is to deprioritize the UI, because we'll have the CLI and because it's probably only going to be used once per tenant.

What do you think?

+100 reaction from Jenn Colt, Jennifer Eustis, Christie Thomas, Colin Van Alstine

Comment by Ann-Marie Breaux (Inactive) [ 13/Dec/19 ]

Cate Boerema Hkaplanian Holly Mistlebauer I'm taking this out of cap-mvp/po-mvp. The CLI tool is a good enough workaround, IMO.

Comment by Ann-Marie Breaux (Inactive) [ 09/Mar/20 ]

Ann-Marie Breaux make clear how this differs from UXPROD-2152 Draft

Comment by Jacquie Samples [ 23/Sep/20 ]

What is the CLI tool? Since we are far past CAP-MVP, how long will this work-around be in place? What is the status of the CLI tool now?

Comment by lew235 [ 24/Sep/20 ]

Jacquie Samples Postman is one option I'm aware of

Comment by Jacquie Samples [ 24/Sep/20 ]

Hi lew235, Postman is an alternate work-around for the CLI tool? Just want to make sure I'm understanding this! I have used Postman a little bit, so I may be wrong here, but it doesn't strike me as a simple UI for doing MaRC mapping. That may be because I'm still in the learning curve, maybe it gets more intuitive?

Comment by lew235 [ 24/Sep/20 ]

Jacquie Samples Postman is the CLI tool. It's definitely not a simple UI.

Comment by Ann-Marie Breaux (Inactive) [ 25/Sep/20 ]

Hi Jacquie Samples The CLI tool was created in MODSOURMAN-181 Closed and works just fine for editing the default MARC-to-instance map. For most libraries, you'll only update that MARC-to-instance map once or twice, at the very beginning of your FOLIO work, when you're deciding if you'll set any mappings differently from the default. You may update it if new MARC fields/subfields are created, but in general, it's not something you're going to be tinkering with on a regular basis. Because the CLI tool is a decent workaround, having a UI for editing it is a lower priority than much of the other functionality that data import still needs. Please let me know if any questions. Thank you!

Comment by Charlotte Whitt [ 25/Sep/20 ]

Hi Ann-Marie Breaux, would you mind share again the GitHub documentation for the CLI tool. I remember seeing the CLI tool demoed but have lost the bookmark. Thanks much.

Comment by Ann-Marie Breaux (Inactive) [ 25/Sep/20 ]

Hi Charlotte Whitt No problem - it's linked from the Inventory documentation: https://folio-org.atlassian.net/wiki/display/FOLIOtips/MARC+Mappings+Information

Comment by Charlotte Whitt [ 25/Sep/20 ]

Oh I looked for it under Data Import. Thanks Ann-Marie Breaux

Generated at Fri Feb 09 00:15:55 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.