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

Advanced Templating with Metatagger Whats possible

Tim__D

Hello,

I'm curous to know how using metatagger can enhance or integratre with templating and some of the benefits of doing so. What are the common (practical) uses of mettatagger for a websites front-end. Is metatagger taxonomy useful for rendering website navigation or contextual navigation? If so where do I learn? I'm looking at metatagger as a way to solve some of the issues I'm facing regarding content reuse and contextual website navigation.

Any project examples, ideas or applications are appreciated.

Thanks,

- Tim

Find more posts tagged with

Comments

Migrateduser

Tim,

The best way to do this is with callouts and the MetaTagger Java API. I did a webcast that's archived and provided some more generic sample code in July. Check out webcast 526 and http://devnet.interwoven.com/site.fcgi/techlib/54486.

Rgs
Clark

Tim__D

I've reviewed the document. My needs are centered around providing a method where users could potentially publish something abstract like an "article". This article could then be "placed" in a variety of locations on the site all of which have a contexual location and presentation within the site. The site however is not dynamically driven at all though the pages are jsp. Placing the article in a single location is working fine but the marriage between the articles context (Context ID) and the data of the article itself spells trouble for publishing the article in another context within the site. I was hoping that metatagger could be used to abstract the "Context ID" so that I could add the context ID to the output pages. This would leave me with one article DCR being used as the Primary DCR for all the published article locations but the resulting .jsp would be where I attach the Metadata (Context ID) which I would extract during generation and then pass to my component PTS to draw the contextual navigation.

To give an example view any article on the support site and imagine that the sites IA has many as 4 levels of nested navigation. The article when shown would display all 4 levels of nested navigation with each level "Highlighed" giving the article "Context" within the sites IA. What I need is the ability to do that as may times as needed to so that multiple places on the site can link to the same basic article but show it in the context of the related navigational path. To do this I have currently devised a system where users attach a context ID to the article which is used by component PTS to render the article in context rendering the highlighted Category, subcategory, topic and subtopic where the article instance lives. I need a way to abstract this data (Context) so that it is not part of the DCR and allows the user to reuse the content within the DCR but render pages which have multiple contexts and multiple file locations.

Can metatagger do this. Again this is basically a static site and need to be regenrerated for changes to me made to the pages.

Edited by Tim__D on 09/08/05 10:56 AM (server time).

Migrateduser

Tim,

Not sure I followed the description of what you're trying to do, but here's some thoughts for what it's worth:

a) Metadata-driven site layout is a very good way to go
b) You can do metadata-driven site layout with TeamSite using extended attributes (EA's) and presentation templates.
c) You can populate the EA's manually or use MetaTagger to infer EA values automatically based on the content on each article.

Does that help?

rgs
Clark

Tim__D

Thanks for your comments. If metadata driven navigation is recommended then are there any documents I can reference to archive this. I don't wish to reinvent the wheel. Can you give examples of the types of EA's one may need in order to achieve this.

Tim__D

Another question I have is about the process of using metadata for website navigation.

If a user is building a page and wishes to generate an page of abstract content someplace within the sites IA. They must first generate the output file and then attach metadata to that file. Initially without the metadata I dont see how preview and generation will be possible.

Migrateduser

One possible way is to store a big directory of articles and use a "categories" EA to determine which category to place the article in and "Summary" and "Title" EA's to form the index entries on the target pages. You'd need presentation templates to generate the article pages and index pages. Presentation templating is a rich topic, so you might start with the online tutorial on your system
iw-home/examples/Templating/templatedata/tutorials/

Rgs
Clark

Tim__D

I have more than a few Templating projects under my belt and understand the concept <iw_perl> component PTS data base integration etc.. Your right Templating is a huge topic so I would never claim to be an expert.

The reason for this post is to see how metatagger when combined with FormsPublisher may be of help in solving my problem of content reuse, and multiple location placement of abstract data "articles" within a single static(generated) website.

Are there any articles on integrating metatagger with templating or using metatagger for website navigation?

Edited by Tim__D on 09/12/05 08:44 AM (server time).

Migrateduser

MetaTagger's key value is that it can analyze the content and generate a metadata record with summaries/categories/keywords/entities/etc automatically. Building a site from this includes for phases:

1 - Extracting the "squib" or short version to place on a topic page. This can be using the MT-extracted extracted title and summary.

2- Identifying the topic pages the each squib should appear on. MT can do this using the auto-categorization capabilities (recognizer & classifier).

3 - Creating a site-index containing all the keywords and extracted entities (person names, dates, etc) and listing the titles underneath them. This is particularly usefull if you don't have a taxonomy to start with.

Current OOTB integration between MetaTagger and TeamSite runs the content (in this case DCR) through MT and stuffs the XML metadata record into an EA, then unravels the XML into name/value pairs that can be edited using TS Tag UI. The PT can then use these EA's in generating the squibs on the appropriate pages from a big directory o'DCR's.

No articles directly on integrating with templating, though most of the servlet stuff in Webcast 526 can be used in the context of callServer().

Sorry if this is too abstract, but metadata-driven layout is by nature somewhat abstract.