Metadata multiplicity

Emanuel

Hi everyone.

My requirement is this:
I need to create n faq entries (the attributes are a question and an answer), and then tag them with 1..* keys, that are related to their argument (for example a faq for a product may be tagged with the following keys "products", "general", "phones").

This is needed to create a dynamic FAQ, that will show to the user only the meaningful entries, depending on his position in the site.

My question is simple:
It seem that tagging (file->tag) means setting Extended Attributes, this means that you can't tag a file more than once, is this correct?

If this is true i will need to create an alternative method for setting and getting metadata.

Thanks!
Emanuel.

Adam Stoller

Hi everyone. My requirement is this: I need to create n faq entries (the attributes are a question and an answer), and then tag them with 1..* keys, that are related to their argument (for example a faq for a product may be tagged with the following keys "products", "general", "phones"). This is needed to create a dynamic FAQ, that will show to the user only the meaningful entries, depending on his position in the site. My question is simple: It seem that tagging (file->tag) means setting Extended Attributes, this means that you can't tag a file more than once, is this correct? If this is true i will need to create an alternative method for setting and getting metadata. Thanks! Emanuel.

This sounds like a TeamSite question rather than a SitePublisher/LiveSite question.

The TeamSite tagging UI allows you to tag files with multiple values (e.g. via a multi-select list) - but the tagging is on the entire file, not just a specific field, so as long as all the Q&A fields for a given DCR are to be associated with the same set of EAs you should have no problem.

If you need to use non-multi-select fields, you'll have to do your own UI for tagging that takes the existing value and appends new values to it (e.g.: comma-separated values) - however that would make it rather difficult to remove an associated tag.

Alternatively, you could extend your notion of a FAQ from Q&A to Q&A&C - where C stands for "classification", and would be a multi-select (or free-text?) field that is captured during content creation, but utilized specially during page generation (perhaps as embedded comments, or maybe as EAs if you actually generate distinct output files for each Q&A)