In a recent ingest on the UAT instance of CMR, we got the following error message (line breaks added for legibility):
<?xml version="1.0" encoding="UTF-8"?><result><concept-id>C1216394131-NSIDC_TS1</concept-id>
<revision-id>14</revision-id>
<warnings>After translating item to UMM-C the metadata had the following issue: /LocationKeywords/2/Type string
"Continent > North America > United States Of America > California > Tuolumne River Basin" is too long (length: 89, maximum allowed: 80)
</warnings></result>
Many of the keywords are probably going to be long like this. If the 80-character limit is indeed there, there would need to be a way to break these keywords down. Is there a way to breakdown these multi-level keywords down so that they will fit in the UMM-C field, but still have their order and heirarchy preserved?
Overview
Content Tools
5 Comments
Cathy Fowler
Note that this problem is only occurring in UAT. In OPS the longer keywords ingest into CMR from our ISO correctly.
user-7b92a
I asked Erich Reiter to take a look at this. He's investigating it and says it might be a bug.
Erich Reiter
There are 2 problems that exist in this scenario:
1) The last keyword needs to be changed
2) The CMR translation code needs to be fixed.
For the first problem:
The schema for the location keywords is the following:
The last keyword broken down into the UMM Location Keyword elements is:
Category: Continent
Type: North America
Subregion1: United States of America
Subregion2: California
Subregion3: Tuolumne River Basin
DetailedLocation:
The above is not a valid location keyword as defined by GCMD. The Tuolumne River Basin should be a DetailedLocation instead. To fix this problem add a NONE > in between > and Tuolumne. The corrected third keyword is shown below:
The second problem is a translation issue from ISO to UMM. Issue CMR-3903 has been written to fix this problem. The corrected translation into UMM should be the following:
Scott Lewis
We will modify our code to add the "NONE >" bits for missing subcategories. I did have one question about this, though: these extra bits are only needed if there is actually a DetailedLocation, correct? For instance, if a particular Location Keyword is just the first one in your list above, it would only need to say:
"Continent > North America > United States of America"
Is this correct? IE, the NONE's are only needed to pad between missing parts of the keyword and the DetailedLocation?
Erich Reiter
Yes that is correct.