nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

taxonomy UIDs getting truncated on save

Keywil

Hey all,

TS6.7.1 SP2 P3
Win2K3
MT 4.1.2

I'm trying to implement dc.coverage.spatial metatags in our project. I have a taxonomy of 246 countries which we use to create a browse-only project.

A couple of issues that we're encountering that perhaps someone can point me in the right direction to solve.

1 - Thie minor issue is when clicking the Add/Edit button in the TaggingUI to populate the countries pick-list, the browse-only picker takes quite a long time to render (if it renders at all). Often the only way to get it to render is click "Ok" and then click "Cancel" (which seems to remove any previous values). When the browse-only picker does render, selecting 'All' countries takes a good 45-50 seconds to populate the right hand side.

I believe this to be a resources issue and will have to test on the test production environment with more ram and processing...

2 - The real issue is that when the user selects all of the countries, and (waits 50 secs) then 'Save and Close' on the TagginUI, and 'Finish' on the DCT, the resulting UID string within the DCR's properties is truncated at 4095 characters.

The properties page ofthe DCT would look as follows...


TeamSite/Metadata/descriptive/dc.coverage.international: AFGHANISTAN,ÅLAND ISLANDS,ALBANIA,~242 terms later~,ZIMBABWE 

TeamSite/Metadata/descriptive/dc.coverage.international_codes: DCCOVERAGEINTERNATIONAL::ENG001,DCCOVERAGEINTERNATIONAL::ENG002,DCCOVERAGEINTERNATIONAL::ENG003... ~122 UID's later~ DCCOVERAGEINTERNATIONAL::ENG125,DCC <-- stops right here

I noted that it doesn't truncate clean at the end of a UID but actually into the next one.. 'DCC' The UID String is exactly 4095 characters.

Is there some buffer, or other parameter that I should be looking at? I'd appreciate any advice.

Thank you.

Find more posts tagged with

Comments

Pawan

The performance issue seems to be obvious with such a long list, but 45-50 secs is much more then desirable and are there many more relatively large items in your dct?
Have you tried setting this value of the parameter from the CLT directly from command prompt?
We too set long value through metadata cgi, I am not sure the max length for it as it varies. I try to find out on our box and post it.

Migrateduser

Keywil,
I think the 4095 boundary could very well be a bug, raise a support ticket.

Keywil

Thanks for the replies. We do use browse-only taxonomies for other elements in the taggerGUI but they're all relative small (15-25 items).

The performance issue seems to be obvious with such a long list,

When I look at the task manager during this time (when items are being 'copied over') the CPU is reporting 100%

I think the 4095 boundary could very well be a bug,

Surely this isn't the first time someone has used more than 124 taxonomy items or UID's ?

Migrateduser

A few things:
1. I believe the limit (truncation) is a bug. Please open a case with your supporting information.

2. This is not a MetaTagger issue - MT is responding correctly - look at the values in subjectMetatadata0. This is a TeamSite issue. I will have the moderator move this item.

3. There is a possibility of improving the TagUI's performance . Which TagUI are you implementing? With the release of 6.7.1 SP1 there is a new optional TagUI. Using the new UI could help with performance. On a dev box you might try setting up the new TagUI and running a comparison of the old to the new.

Information on the new TagUI can be found in TeamSite\local\config\tagui. There is also information in the release notes for the 6.7.1 SP1 on support or in the download packed you got from the server in order to install.

Keywil

I'll set up a ticket tomorrow. Thank you.

I should have clarified that we are implementing the next generation taggingUI that's available with 6.7.1

When I was testing again today, I noticed the subjectMetadata0.. I could remove all the values from the browse-only and the subjectMetadata0 was still populated with the old UID's

If I went back to the TaggingUI, the browse-only field was still populated. I'll be testing tomorrow with a smaller taxonomy of values and try to determine whether it's a size thing or if there's something else that seems to trigger the problems.

Migrateduser

SubjectMetadata0 is the response from MetaTagger stored verbatum. If you manually change the values in the TagUI or by CLT using iwextattr on the EAs, only the TeamSite EAs are changed - the values in the SubjectMetadata0 do not change unless MT is invoked.

Pawan

...I should have clarified that we are implementing the next generation taggingUI that's available with 6.7.1.

We hardly set values of length above 3000 characters and are using the old tagger ui, so my case is different from yours. Let us know how you resolve it.

Keywil

We hardly set values of length above 3000 characters and are using the old tagger ui, so my case is different from yours. Let us know how you resolve it.

Well, I did manage a bit of a work around. I reduced the UID from DCCOVERAGEINTERNATIONAL::ENG001 to simply INTL::ENG001 and that removed quite a few characters. 20X246. Selecting all seems to work fine and the UID's don't truncate. the string seems to be short enough. I have submitted a ticket to IWOV.

Regarding performance - I did move the solution to a machine with more resources and have not observed any noticeable improvement in performance of the browse-only pop-up. It still takes a significant amount of time to populate all items.

Subsequently, if one selects all and then saves the TaggerGUI and then tries to 'edit/add' that international field again, the browse-only pop-up will fail. One receives a blank pop-up with two linkable options "Ok" and "Cancel"... that's it...

I appreciate all of your helps folks. Thank you.

Keywil

Worked with Interwoven and apparently this is a known issue that has been addressed in TS 6.7.2
https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=60595

https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=62230

Thanks again folks