Can i handle position element(containerName/0/itemName to containerName/itemName) in nextGenTagUI

Hi,

I am using TS-7.4.1 and i am recently moved old tagui to next gen tagui.

When i was using old tagui it was working fine(TeamSite/Metadata/containerName/itemName) but now when i am using next gen tagui that’s added positioning element into container and item

and get path TeamSite/Metadata/containerName/0/itemName while should be path TeamSite/Metadata/containerName/itemName .

I want to removed '0' from there path(TeamSite/Metadata/containerName/0/itemName to TeamSite/Metadata/containerName/itemName ).

Old tagui structure.

<container name="ContainerName" location="ContainerName" max="1" min="1" default="1">
<item name="ContainerNameType" pathid="ContainerNameType">
<label>ContainerNameType</label>
<description>ContainerNameType</description>
<select multiple="t" required="t">
<option label="A" value="A"/>
<option label="B" value="B"/>
<option label="C" value="C"/>
</select>
</item>
</container>

--------------------

get metadata path when we are using old tagUI :

TeamSite/Metadata/containerName/ContainerNameType:

------------------------------------------------------------------------

Now In Next TagUI: When i am using same stuctured

---------------------------------------------------------------------

Then get metadata Path:

TeamSite/Metadata/containerName/0/ContainerNameType while it should be TeamSite/Metadata/containerName/ContainerNameType

How i can get TeamSite/Metadata/containerName/ContainerNameType structure

Please help me.

Find more posts tagged with

Comments

Adam Stoller

I'm not sure if it will make any difference (theoretically it shouldn't) but try changing:

to just:

and see if that makes any difference.

If it doesn't, then there isn't too much you can do other than post-processing as part of the tagging operation or pre-processing as part of whatever is attempting to consume the EAs - or adjust the code that is attempting to consume the EAs to use the new pathing.

But try the above change first - since it is a minimal change that might save you a bunch of other work.

jatin

thanks for reply.

I did try <container name="ContainerName" location="ContainerName"> senario but result could not change.

I want to remove positoning value from EA's(containerName/0/itemName) because tagging is lost from existing old documents.

Can i maintain tagging value on existing documents?.

Adam Stoller

Any EAs on existing assets, set via the old tagging UI, should remain as-is.

[Apparently] Any EAs set on assets using the new tagui will contain a positional element.

If you take those as "givens" - there are various things that you can do to unify the information. You need to consider the pros and cons of these various approaches and then develop (or re-develop) your customization(s) to provide the desired end-result.

You can contact Support if you want - but my guess is that they will, essentially, tell you the same thing.

jatin

if we will use eaSaveFormat="withoutInstanceNums" attributes then we can avoid added positioning element.