External metadata working for Date but not Title

[lh435]

I created a external_metadata.cfg file for a PDF. Its contents look like this

example.com/directoryname/ t:"Page title" d:19110101
example.com/directoryname/nameofpdf.pdf t:"Page title" d:19110101

I tried pointing to the directory and the file itself, first individually, then together, for testing.

After the index is updated, this configuration works well for the the date field; I can see it and facet on it in the search results. However, the title is not picked up. Instead, the search results show a garbled string (presumably OCR'd) where the title should be.

Thanks very much for any help.

[plevan]

Hi Laura,

Unfortunately the metadata t field isn't the same as the title element in the data model.

If you want to display the metadata t value you will need to update your results template to display this instead of s.result.title. A good idea for this is to use conditional logic to display it, falling back to the normal title if metadata t doesn't exists.

Something like

<#if s.result.metadata["t"]??>${s.result.metadata["t"]}<#else>${s.result.title}</#if>

You will also need to ensure that metadata t is configured to return in your result packet by setting/adding it to the SF query processor option.

[lh435]

Hi Plevan,

It's not that I want to display the metadata t value; it's that I want to change the search results, so that the PDFs listed have meaningful titles.
How do I do this please?

In external_metadata.cfg, I have tried the
example.com/directoryname/nameofpdf.pdf t:"Page title" d:19110101
example.com/directoryname/nameofpdf.pdf title:"Page title" d:19110101
example.com/directoryname/nameofpdf.pdf name:"Page title" d:19110101
example.com/directoryname/nameofpdf.pdf Title:"Page title" d:19110101

But no joy. Thanks very much for any help.

[hdilusha]

Hi Laura,

First you would need to map the meta class that you are using in the external_metadata.cfg in to the metadata-mapping.cfg. You can do it via the admin ui.

If we leave meta_t since you said it wasn't working, let's consider the meta class 'name';

In external_metadata.cfg,
example.com/directoryname/nameofpdf.pdf name:"Page title" d:19110101
Read: https://docs.funnelback.com/15.24/customise/metadata-customisation/external-metadata.html

Then in the metadata configuration map, map a new meta field and assign it to 'name'. Say 'pdfname' is the one you are creating in the metamap. Then pdfname=name
Read: https://docs.funnelback.com/15.24/customise/metadata-customisation/configuring-metadata.html

After that in the collection.cfg reveal the new meta class in the json reponse as well. You just need to add the new meta class to the query_processor_options under -SF.
e.g. query_processor_options=-stem=2 -SM=both SF=[pdfname]
Read: https://docs.funnelback.com/15.24/more/extra/padre_query_processor_options.html

Then when you check the said pdf's in the json output, you would be able to see the titles assigned to the new meta class. You'd then need to use the same in your template as Pete has mentioned above.
If you are not using meta_t, then you'd probably need to use some logic to apply the newly defined title classes to be used in the template as well.

Once you get confident on this process, you can try to assign the 'name' to meta_t in the meta map.
Hope this helps.
Thanks.

[lh435]

Thank you so much for this detailed explanation, and the links! The titles are appearing now, as expected. Thanks again.