Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Lotus > Morning Glory upgrade 

Issue 1: Duplicates created upon importing fileOnly 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
        serverSystem JiraJIRA
        columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyMODSOURMAN-835

Issue 2: The same exact record displays twice due to mapping rules change.  [ Resolve with UXPROD-3911]

Issue 3: Search does not work as expected due to mapping rules change [ UXPROD-3911]

Morning Glory > Nolana upgrade   

Issue 1: Duplicates created upon importing file with duplicates 

Resolution option

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUIDATIMP-1318

ONLY ISSUE: 

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyMODSOURMAN-835

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 

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. Update Release Notes

Nolana > Orchid upgrade

Issue 1: Duplicates created upon importing file with duplicates 

Resolution option

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUIDATIMP-1318

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 

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. Update Release Notes

Orchid > Poppy upgrade

Issue 1: Duplicates created upon importing file with duplicates 

Resolution option

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUIDATIMP-1318

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 

Resolution option

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-36Resolve with UXPROD-3911]

...