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
- Do not use the default job profile: Default - Create SRS MARC Authority
- Create a new job profile with a Match profile that checks for 010 $a or 001 (whatever the match criteria might be).
- For non-matches set the Action profile to Default - Create MARC Authority" · Create authority
- Example: https://bugfest-nolana.int.aws.folio.org/settings/data-import/job-profiles/view/d3271c74-97ec-4dd9-9470-97b2154d63fd?query=KG&sort=name
- 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
- If you think your authority file may contain duplicates THEN
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?
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
[ Resolve with UXPROD-3911]
Issue 3: Search does not work as expected due to mapping rules change (see above screenshot)
- 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
Morning Glory > Nolana upgrade
Issue 1: Duplicates created upon importing file with duplicates
Resolution option
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
ONLY ISSUE: 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-835
Issue 2: The same exact record displays twice due to mapping rules change. See (or add) Nolana release notes
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Issue 3: Search does not work as expected due to mapping rules change
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Nolana > Orchid upgrade
Issue 1: Duplicates created upon importing file with duplicates
Resolution option
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Issue 2: The same exact record displays twice due to mapping rules change. See (or add) Nolana release notes
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Issue 3: Search does not work as expected due to mapping rules change
Jira Legacy
...