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)
Extended attrbutes
conman
I´m wondering about the scope of the extended attributes I can change or look up using iwextattr.exe.
Is there a defined set of attributes that the different Interwoven products use and that can be looked up?
What is the most common custom use of extended attributes?
Is there any direct relation between these attributes and the Administration Properties in the IIS Metabase?
Find more posts tagged with
Comments
jorge1
The extended attributre are also known as metadata. They are used by TeamSite (i.e. templating) and also for custom metadata definitions.
Adam Stoller
Is there a defined set of attributes ...?
Well, TeamSite Templating uses a specific set of extended attributes, that are documented in the manual, for indicating the category/data-type/DCR/PT, etc. associated with either the DCR or files generated from the DCR using iwgen.
Visual Annotate uses extended attributes to store annotation information.
I don't remember if TeamXML uses extended attributes for internal cross-referencing (it might, it might not - I'd have to check the manual and I don't have it handy right now).
What is the most common custom use of extended attributes?
Probably the tagging of launch and/or expiration dates on assets.
Though they could be used for almost any purpose in which it would make sense to have metadata associated with an asset within the development environment.
Is there any direct relation ... [to] Administration Properties in IIS Metabase?
Not that I can think of - I'm sure one could
make
relationships or associations between the two - but they are distinct products / product features. TeamSite (et al) does not require IIS - IIS does not require TeamSite.
--fish
(Interwoven Information Guy)
smenon
To answer the question about whether TeamXML uses extended attributes for internal cross-references : No, it doesn't. The cross-references are all maintained and managed within the server and are not visible as EAs/Metadata on the assets. And you should be able to set EAs/Metadata on TeamXML assets just like you can for TeamSite assets even though the TeamXML assets appear to be read-only from the file-system.