Many search engines (e.g. the SWISH family, namazu [See
SearchAttachments]) supply a mechanism for searching within http metadata. How about adding some facility for
exposing the TWiki forms metadata as
HTML metadata.
In
VariableForCategoryDropdown topic
AdrianLynch mentions a mechanism for accessing specific metadata. With that mechanism,
this functionality could be added without too much trouble by adding:
%META{field="TopicStatus" format="<META NAME=\"TopicStatus\" CONTENT=\"$item\">"}%
But this may be too much for a new twiki'er. It also may have a problem in producing null metadata content tags (
not sure of this is really a problem but) if its used in a template. Maybe better would be a new variable
%EXPORTMETA{field="TopicStatus"}%
Comments?
--
JohnRouillard - 21 Jan 2002
The ability to expose TWiki form metadata as
HTML metadata would be useful in searches. The simpler the mechanism to do so, the better.
--
RandyKramer - 22 Jan 2002
FormattedTWikiFormDataInTopicText has been implemented; will it render correctly in templates, too?
--
WillNorris - 24 Mar 2004
I think that there is some confusion here; maybe it is my confusion. The original topic is discussing
html metadata, and somehow it ended up at
TWiki metadata. Near as I can tell, there is no way--short of writing a plugin--to get stuff into the <head> section. There is the %HTTP_EQUIV_ON_VIEW% variable, but it doesn't appear that I can do something like (commented out, just in case):
* #Set HTTP_EQUIV_ON_VIEW = %HTTP_EQUIV_ON_VIEW% 
 <meta name="keyword" content="Twiki">
In other words, I want to keep the global setting, and add my stuff to it. Even if I don't keep the global settings, it is pretty tricky to a variable to span multiple lines (the fancy html entities in the example above don't actually work).
Am I wrong, or is it difficult/impossible to add html meta data to TWiki pages? Since our search engine likes to look at the
html metadata to index pages, this turns out to be pretty important for getting more eyes on our TWiki pages.
09 May 2006 addendum: Turns out the above fails because "Max recursive depth reached". Makes sense...
Thanks,
--
DougClaar - 08 May 2006
I'm using the following on a single TWiki web to build a
HTML style of <META> tag that ends up looking like:
<meta name="topicparent" content="[[Codev.WebHome][WebHome]]" />
-
http-equiv meta tags for view script:
* Set HTTP_EQUIV_ON_VIEW = <meta name="topicparent" content="%META{"parent" dontrecurse="on"}%" />
To keep the global settings I manually add the HTTP_EQUIV_ON_VIEW to my individual
WebPreferences topic. I end up with three META tags strung together and it works fine.
--
RandyJankin - 09 May 2006
Hmm. If I set HTTP_EQUIV_ON_VIEW in both
WebPreferences and in my topic, I only get the one from my topic in the header. Which is actually rather what I expected, in that I didn't think that variable settings were cumulative.
In my topic, I have:
* Set HTTP_EQUIV_ON_VIEW = <meta name="topicparent" content="%META{"parent" dontrecurse="on"}%" />
In
WebPreferences, I have:
* Set HTTP_EQUIV_ON_VIEW = <link rel="alternate" type="application/rss+xml" title="RSS Feed" href="%SCRIPTURLPATH{"view"}%/%WEB%/WebRss" />
BTW, I'm on Dakar. What am I missing?
--
DougClaar - 09 May 2006
Well, couldn't figure out what I was missing, so I scratched that itch:
HtmlMetaPlugin
--
DougClaar - 31 May 2006