You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dear Sirs,
I have this XML structure in my IDOL Content XML database: (see 1st image "XML_DOCUMENT.jpg")
But in Find, Expanded View, "ADVANCED" Metadata I can only see "flattened" fields (see 2nd image "ADVANCED_METADATA.jpg")
Is there in FInd a way, or configuration, to show XML data in their original (parent/children) structure?, ie:
LUOGO
COMUNE Salemi
ENTITAID 3
INDIRIZZOCOMPLETO Salemi, Trapani
LUOGOESTEROFLAG false
NAZIONE Italia
PESO 1
PROVINCIA Trapani
REGIONE Sicilia
LUOGO (again the field structure)
["XML_DOCUMENT.jpg"]
["ADVANCED_METADATA.jpg"]
The text was updated successfully, but these errors were encountered:
ciroppina
changed the title
How Idol/FIND visualizes (shows) Xml Filelds structures in "Advanced Metadata" view
How Idol/FIND visualizes (shows) Xml Fields structure in "Advanced Metadata" view
Jan 11, 2022
I undertand that Find metadata visualization (in Document expanded view) is a kind-of "ResponseFormat=FLATMAP"; it means that when a structured-XML field occurs more-than-once in a XML indexed DOCUMENT, Find shows it as a "one-to-many" fashion (field: name, values: [s1, s2, ...sn] ) removing parental structure
I need to show/view such fields in a "ResponseFormat=json" way instead. I mean:
"PERSONA": [
{
"COGNOME": "Civelli",
"ENTITAID": "22",
"NOME": "Giorgia",
"NOMINATIVO": "Giorgia Civelli",
"PESO": "1",
"SESSO": "F"
},
{ next PERSONA structure... }
]
Dear Sirs,
I have this XML structure in my IDOL Content XML database: (see 1st image "XML_DOCUMENT.jpg")
But in Find, Expanded View, "ADVANCED" Metadata I can only see "flattened" fields (see 2nd image "ADVANCED_METADATA.jpg")
Is there in FInd a way, or configuration, to show XML data in their original (parent/children) structure?, ie:
LUOGO
LUOGO (again the field structure)
["XML_DOCUMENT.jpg"]
["ADVANCED_METADATA.jpg"]
The text was updated successfully, but these errors were encountered: