Page Comparison

...

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

• Workaround options
  
  • Option A: Wipe out Authority records and re-upload?
  • Option B:  Update records via data import?
  • What about this?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

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

...

• • 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   

...

• • 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

Resolution option

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 

...