Metadata Record Export (UXPROD-652)

[UXPROD-2413] Metadata Export - Mapping Profile - support transformations for Inventory Instances - records on the fly Created: 28/Apr/20  Updated: 21/Oct/20  Resolved: 19/Oct/20

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q3 2020
Parent: Metadata Record Export

Type: New Feature Priority: P3
Reporter: Magda Zacharska Assignee: Magda Zacharska
Resolution: Done Votes: 0
Labels: cap-mvp-split, data-export-q3-2020
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by MDEXP-141 Applying mapping profile - Instance -... Closed
is defined by MDEXP-142 Applying mapping profile - some tran... Closed
is defined by MDEXP-150 Mapping profile - transformations - r... Closed
is defined by MDEXP-210 Mapping profile - provide instance fi... Closed
is defined by MDEXP-216 Mapping profile - provide holdings fi... Closed
is defined by MDEXP-217 Mapping profile - provide field name ... Closed
is defined by MDEXP-218 Mapping profile - provide items field... Closed
is defined by MDEXP-227 Mapping profile - provide field name ... Closed
is defined by MDEXP-228 Mapping profile - provide field name ... Closed
is defined by MDEXP-229 Mapping profile - provide field name ... Closed
is defined by MDEXP-230 Mapping profile - provide field name ... Closed
is defined by MDEXP-231 Mapping profile - provide field name ... Closed
is defined by MDEXP-237 Applying mapping profile - Holdings -... Closed
is defined by MDEXP-238 Applying mapping profile - Item - sel... Closed
is defined by MDEXP-239 Applying mapping profile - Combinatio... Closed
is defined by MDEXP-243 Applying mapping profile - Combinatio... Closed
is defined by MDEXP-248 Mapping profile - provide field name ... Closed
is defined by MDEXP-249 Applying mapping profile - Item - eff... Closed
is defined by MDEXP-251 Mapping profile - provide field name ... Closed
is defined by MDEXP-252 Applying mapping profile - location f... Closed
is defined by MDEXP-266 Generate MARC record- Holdings and it... Closed
is defined by MDEXP-280 Mapping profile - provide field name ... Closed
is defined by UIDEXP-53 Settings - information about profiles Closed
is defined by UIDEXP-69 Mapping profile – add transformations... Closed
is defined by UIDEXP-70 Mapping profile – transformation – se... Closed
is defined by UIDEXP-71 Mapping profile – add transformation ... Closed
is defined by UIDEXP-73 Mapping profile – add transformation ... Closed
is defined by UIDEXP-75 Mapping profile – actions button Closed
is defined by UIDEXP-77 Mapping profile – cancel adding new ... Closed
is defined by UIDEXP-92 Mapping profile – transformation – po... Closed
is defined by UIDEXP-99 Mapping profile – add transformation ... Closed
is defined by UIDEXP-103 Mapping profile - transformations - c... Closed
is defined by UIDEXP-104 Mapping profile - Settings - adding t... Closed
is defined by UIDEXP-130 Mapping profile - transformations - s... Closed
is defined by UIDEXP-131 Mapping profile - transformations - edit Closed
is defined by UIDEXP-132 Mapping profile - edit profile Closed
is defined by UIDEXP-133 Mapping profile - delete profile Closed
is defined by UIDEXP-134 Mapping profile - duplicate profile Closed
is defined by UIDEXP-135 Mapping profile - transformations - s... Closed
is defined by UIDEXP-138 Mapping profile - validation between ... Closed
is defined by UIDEXP-140 Provide translation file for the fiel... Closed
is defined by UIDEXP-149 Mapping Profile- Edit transformations... Closed
is defined by UIDEXP-180 Modify transformation form to ensure ... Closed
Relates
relates to MDEXP-271 Differentiate "displayNameKey" for en... Closed
relates to UXPROD-2153 Metadata Export - Mapping Profile - i... Closed
Epic Link: Metadata Record Export
Front End Estimate: XXXL: 30-45 days
Front End Estimator: Viktor Soroka
Front-End Confidence factor: Low
Back End Estimate: XXXL: 30-45 days
Back End Estimator: Kruthi Vuppala
Development Team: Concorde
PO Rank: 120
PO Ranking Note: Implementing this feature will eliminate need for UXPROD-1396, will cover most of the work related to UXPROD-142 and export to non-MARC format that is currently covered by UXPROD-2224, UXPROD-2225, UXPROD-977)
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R2
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R2
Rank: TAMU (MVP Jan 2021): R2

 Description   

This is split of UXPROD-2153 Closed

In Q2 we support transformation only for selected holdings and items fields with the whole instance record being always a part of the export. This feature will allow user to determine which fields from the inventory records should be included in the export.

The user needs to have a flexibility in determining the fields and their transformations in setting up their export in MARC format. The inventory fields for instances, holdings and items will provide the data that will populate MARC fields as specified by the user in the mapping profile transformations. If the transformation is not provided but the field is selected then for the inventory instance record the default mapping profile (used also for generating MARC records on the fly) will map the inventory instance fields to MARC. If the filed is not a part of the mapping, then it will be ignored during the export. The overview of the specific scenarios: https://docs.google.com/spreadsheets/d/1dMYG1CGwIteskagS1gYcq640gxQU4eif/edit#gid=1340790654

The priority of adding the support for the instance, holdings and item fields is determined according to the MM SIG Data Export subgroup provided feedback and represented in: https://docs.google.com/spreadsheets/d/1XvHmToGQwhzmMNlQ5-l1QTEDyUtDpdn_/edit#gid=1869895650

The library can set up multiple mapping profiles. The mapping profile will be associated with the export through the job profile and the same mapping profile can be associated with multiple job profiles.

The high level flow will be as follows:

  1. The user provides the list of instance UUIDs to be included in the export
  2. While triggering the export, the user selects the job profile that is associated with a mapping profile.
  3. The mapping profile specifies which FOLIO record types will be included in the export.
  4. The transformations specify which fields should be included and their MARC target fields

Metadata Export Subgroup use cases: https://folio-org.atlassian.net/wiki/display/MM/Export+Use+Cases?src=contextnavpagetreemode.
Link to the mockups: https://drive.google.com/drive/folders/1qUP38ooZ_ZqW9RNH-53j65sZv6jSiZhx



 Comments   
Comment by Karen Newbery [ 05/Jun/20 ]

Duke - can't go live without this.

Comment by Holly Mistlebauer [ 17/Jun/20 ]

Chicago comment from Round IV Outliers spreadsheet: When we export MARC records, we need to delete and transform data that we cannot share. -Tod Olson

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