7 messages in com.googlegroups.google-enterprise-developerRe: Overwriting document title with feed| From | Sent On | Attachments |
|---|---|---|
| Robert Crowe | 10 Jun 2007 10:55 | |
| Colin Neale | 10 Jun 2007 13:33 | |
| tm | 10 Jun 2007 22:41 | |
| Robert Crowe | 11 Jun 2007 09:08 | |
| Colin Neale | 11 Jun 2007 15:58 | |
| Colin Neale | 11 Jun 2007 16:06 | |
| John Bailey | 12 Jun 2007 09:36 |
| Subject: | Re: Overwriting document title with feed![]() |
|---|---|
| From: | John Bailey (jbai...@baileysc.com) |
| Date: | 06/12/2007 09:36:14 AM |
| List: | com.googlegroups.google-enterprise-developer |
The issue with the title isn't just with getting the title in the results. The issue is when using queries such as intitle:[Title Name] where the [Title Name] is text from your title, it would be better if you could get the appliance to use the title you pass if present rather than the one it parses from the document.
Certainly, this can be coded around, but it would be nice if you could just use the built in Google syntax.
I like the idea of just including the <T> element in the feed, but it is not specified in the DTD so where exactly would you put this element?
Thanks John Bailey
On Jun 11, 7:06 pm, "Colin Neale" <neal...@gmail.com> wrote:
Hi Robert,
Thanks Colin! We'll give that a try and report back. Could we also simply include a "*T*" element in the feed itself, and if so, which would take precedence; the one from the feed, or the one from tha document parser?
-- Im not actually sure about that as I have not tried it, -- but personally I would always want to retain Google's values alongside my own for discovery purposes at least. The GSA will extract your document properties as it builds these fields, so whilst the values may or may not be of interest to you, there's no harm in keeping them just in case. At least with the approach below, you know that you are only changing the presentation.
Regards Colin..
On 12/06/07, Robert Crowe <rob...@ourwebhome.com> wrote:
Thanks Colin! We'll give that a try and report back. Could we also simply include a "*T*" element in the feed itself, and if so, which would take precedence; the one from the feed, or the one from tha document parser?
On Jun 10, 1:34 pm, "Colin Neale" <neal...@gmail.com> wrote:
Hi Robert,
You can create your own front end, and edit the stylesheet to add your own meta title in place of the default one (which I think is simply "*T*").
The change you will need to make to the stylesheet is around line 2290. Change the line to look something like this.
*<xsl:with-param name="orig_string" select="MT[@N='METAFIELD']/@V"/>*
Replace METAFIELD with your own meta name.
You will also need to enable metatags by setting the *show_meta_tags*variable to " *1*" and use the *&getfields=* parameter in the search url to ensure they fields you want are returned from the search.
Note: The change is needed to a part of the stylesheet that Google say do not customise, but if you create your own front end and use that, there should be no problems and you can always restore the default at any time anyway.
Regards Colin..
On 11/06/07, Robert Crowe <rob...@ourwebhome.com> wrote:
We're feeding documents (.doc, .pdf, .ppt, .xls) and specifying a title. The problem i'm seeing is that the appliance is parsing the title out of the document properties and using that to replace the title we give it in the feed. This is a problem because the title in the document properties is usually different, and usually wrong, and then searches using intitle: don't work right.
Is there a way to cause the appliance to use the title we give it instead?
-- Regards Colin
-- Regards Colin- Hide quoted text -
- Show quoted text -




