Page Comparison

Lotus > Morning Glory

...

upgrade 

Issue 1: Duplicates created upon importing file with duplicates Only use  Default - Create MARC Authority when you are 100% sure there are no duplicates. 

• Workaround: 
  • If you think your authority file may contain duplicates THEN
    1. Do not use the default job profile: Default - Create SRS MARC Authority
    2. Create a new job profile with a Match profile that checks for 010 $a or 001 (whatever the match criteria might be).
    3. For non-matches set the Action profile to Default - Create MARC Authority" · Create authority
    4. Example: https://bugfest-nolana.int.aws.folio.org/settings/data-import/job-profiles/view/d3271c74-97ec-4dd9-9470-97b2154d63fd?query=KG&sort=name
    5. Only issue 

       Jira Legacy
       server System JiraJIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODSOURMAN-835

Issue 2: The same exact record displays twice due to mapping rules change. See Morning Glory release notes

Image Removed

• Workaround options
  
  • Option A: Wipe out Authority records and re-upload?
  • Option B:  Update records via data import?
  • Option C:  

    Jira Legacy
    server System Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODDATAIMP-669

    • It should be run on non-working hours. Takes some time because records are updated one by one. 
    • Sequence: Run after mapping rules changes - See wiki page - MODDATAIMP-669: Script to refresh Authorities against an updated MARC-Authority map

 [ Resolve with UXPROD-3911]

Issue 3: Search does not work as expected due to mapping rules change (see above screenshot) 

Problems 

• • Jira Legacy
    server System Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODSOURMAN-805

  • Jira Legacy
    server System Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODSOURMAN-755

• Option A: Wipe out Authority records and re-upload?
• Option B:  Update records via data import?
• What about this? 

  Jira Legacy
  server System Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODDATAIMP-669

Next steps for Issue 2 and 3

1. Upgrade mod-source-record manager
2. Update mapping rules/marc-authority
3.  Off hours - run script to update existing authority records MODDATAIMP-669: Script to refresh Authorities against an updated MARC-Authority map
4. Apply this to Michigan State (dry-run) and then get Mich State verification
5. Ask Kyle/KG will inform Michigan State about running this script and then inform Sobha. KG will update Rally ticket with Michigan State confirmation. 
6. Need to update release notes 

Morning Glory > Nolana upgrade   

Issue 1: Duplicates created upon importing file with duplicates 

Resolution option

ONLY ISSUE: 

Issue 2: The same exact record displays twice due to mapping rules change. See (or add) Nolana release notes

Issue 3: Search does not work as expected due to mapping rules change 

Problems 

• • Jira Legacy
    server System Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODSOURMAN-805

  • Jira Legacy
    server System Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODSOURMAN-755

Next steps for Issue 2 and 3

1. Upgrade mod-source-record manager
2. Update mapping rules/marc-authority
3. Off hours - run script to update existing authority records MODDATAIMP-669: Script to refresh Authorities against an updated MARC-Authority map
4. Spitfire will test on rancher (Spitfire needs to create a user story) 
5. Then apply this to Nolana bugfest – coordinate with Kitfox (Spitfire needs to create a user story)
6. Need to update Release Notes

Nolana > Orchid upgrade

Issue 1: Duplicates created upon importing file with duplicates 

Resolution option

Issue 2: The same exact record displays twice due to mapping rules change. See (or add) Nolana release notes

Issue 3: Search does not work as expected due to mapping rules change 

Jira LegacyserverSystem JiracolumnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionserverId01505d01-b853-3c2e-90f1-ee9b165564fckeyARCH-36[ Resolve with UXPROD-3911]

...