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; } } }

Leveraging MetaTagger, Search, and Suggestions in a DCT

System

Hello,

I'm looking into an option to be able to leverage the MetaTagger vocabularly integration that is found in the TagUI inside an actual TeamSite Data Capture Template.

For example, having the integrated search and multiple section functionalities found out of the box between TeamSite TagUI and MetaTagger inside the actual DCT as a field, or multiple fields.

Is this possible? Any known hacks to get this to function properly?

Thanks,

Find more posts tagged with

Comments

Scott_G

Any update to this? I am trying to implement a similar feature.

I was hoping something as simple as placing the same configuration from the metatagger configuration file into a DCT would work, but had no luck.

Its looking like I'm going to need to input this data into a database or deploy our vocabularies as a TeamSite managed file which we can pull in from a perl script / java code and then process...

nipper

There are no good out of the box solutions. You will end up writing your own code to do this.

Now the big question is why ? It is a really bad idea and wll be a kludge at best if you implement it. Is there a reason you cannot use the EA approach to the MT data ?

What is the use case you need ?

Scott_G

Not sure about parent, but we have the desire to create some dynamic pages which will surface content based upon tags.

The desire is to allow the users to create dynamic page based upon selected metadata values (i.e. they want to show content which is based upon location_A and keywords B and C, etc...).

We can do this utilizing the tagui, but this isn't really Metadata at this point. Using the values selected is how we are going to get content onto the page.

nipper

How are you generating dynamic pages ? Putting the info in a DB ? Generating a ASP/JSP with a TPL or XLST ?

DB is easy with the tagui, so is TPL

Scott_G

We will deploy this information to a database. We utilize the MVC architecture for our site, so the Model will be responsible for querying the database to determine what content will be delivered to the View, which is then be responsible for displaying the information. Thus these pages will always be up to date, without the need for regenerating / publishing the page.

The problem isn't getting the information to the database. Our problem is that we would like to utilize something familiar to our content producers, which is having a pop-up window which will allow them to select information in the same manner they do when tagging content.

It's not that we can't whip up some custom code to give them a presentation similar to what's they would see in the tagui, that isn't too difficult. We felt there was no need to re-invent the wheel if we didn't need to.

Wheels are great things to study... when you want to learn more about wheels.

Scott_G

We ended up creating a window which looks like metatagger. The number of tags was simply too large to adequately be displayed in a drop down list. There were over 2000 values that needed to be converted to Options and then put into an item. Needless to say TeamSite will choke when you try to throw that many values in a select box dynamically. Firefox and IE both think that the script has frozen.

Instead we'll pop up a window and allow for some autocomplete features and the like.