Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Synchronizing old values with new MT values
ShovelFace
MT4.12
Say we have field dc.field in the TaggingUI (drop-downlist) from which a user selects value ABC.
Now we tie in dc.field with MetaTagger (a Classifier). The classifier contains value ABC.
Now when opening the TaggingUI on the same record, dc.field is blank.
Anyone have suggestions on the best way to synchronize the old value with the new MT-enabled value? Am I missing something here?
Find more posts tagged with
Comments
Migrateduser
It's a similar case to changing the type of field - how the data is stored in the EA's changes. Consider what happens when you change from a drop-down list where the option labels and values are different to a text box - the text box will only display the values, not the labels. Similar issues pop up when you change from single-select drop-down to multiselect drop-down.
MT stores values in two EA's for each field:
[itemname]_labels: labels from the MT Taxonomy
[itemname]_codes: UIDs from the MT Taxonomy
both lists are comma-separated.
To migrate from old values to new values would require a script to convert the drop-down single-select format to the MT Taxonomy format.
ShovelFace
Ok, here is a clearer picture of what is happening:
EA before MetaTagger: /TeamSite/Metadata/ABC: cat,dog
ABC is now managed via MetaTagger as a Classifier. In the ABC Classifier, cat has a UID of MYABC::123, whereas dog has a UID of MYABC::456.
Should "cat" and "dog" be selected as the best fit from the Classifier, the following occurs in the Extended Attributes:
/TeamSite/Metadata/ABC: cat,dog
/TeamSite/Metadata/ABC_codes: MYABC::123,MYABC::456
Additionally, the subjectMetadata0 entry is changed to reflect the new facet, namely MYABC.
Using the CLTs, I've manually created the /TeamSite/Metadata/ABC_codes: MYABC::123,MYABC::456 entry on the record and tried opening it in the TaggingUI, but the box is still empty. Do I need to also change the subjectMetadata0 field? If so, how do I do that?
All I am trying to do is not lose previously entered data, and match it up to the new Classifier as users may not want to trigger the re-tag.
Thoughts?
ShovelFace
Anyone? How have others synchronized old values in the EAs with MetaTagger?
Migrateduser
Yes - subjectMetadata0 needs to be resynched with the MT-enabled fields.