nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Not able to search content using LSCS

SwatiM

Hi

We are trying to do content search over DCRs using LSCS.

We are able to do document and metadata search, but content search is unsuccessful.

Any help, would be appreciated.

Thanks

Find more posts tagged with

Comments

nipper

What URI are you using ?

Can you share that and share a query by doc ID ?

Binettoid

As far as I recall, you can't query the actual content of a DCR using LSCS but only the Extended Attributes. E.g. you can query LSCS for DCRs tagged with an EA called e.g "Sport" that matches your search term "golf" but you can't find all DCRs that have the word "golf" in their content fields.

A full-blown version of IDOL transcends this limitation and then some, but unless things have changed dramatically since TS & LS 7.1x, you would need to build or overlay another layer of text analysis to query the DCRs by content.

Rick Poulin

you would need to build or overlay another layer of text analysis to query the DCRs by content.

Not quite.. using PLC configuration, you can add extraction beans to have the LSCS deployment process map xpaths in your DCR to LSCS attributes at deployment time, without ever writing them as EAs on the TeamSite copy.

Rob76

Not quite.. using PLC configuration, you can add extraction beans to have the LSCS deployment process map xpaths in your DCR to LSCS attributes at deployment time, without ever writing them as EAs on the TeamSite copy.

Is this documented? Where?

The beans you speak of, is this adding items to a configuration file or are you talking about writing code?

OEQTR.pdf

Rick Poulin

Is this documented? Where?

The beans you speak of, is this adding items to a configuration file or are you talking about writing code?

*giggles* @ "documentation". Smiley Happy

Without getting into a rant, the lack of documentation combined with the fact that iwov used Spring, a framework whose whole point is uber-configuration, my thought was always that Spring is the "UITK" for LiveSite, and as such, is the supported way of customizing the platform. But none of this is explicitly documented, so you be the judge of whether you consider this approach supported enough to use in your implementation.

In customer-teamsite-resource-config.xml, add

[PHP]

class="com.interwoven.livesite.lscs.impl.LSCSDeploymentDescriptor">

factory-method="create">

.*templatedata/Intranet/Article/data/.+$

class="com.interwoven.livesite.lscs.processor.ContentAttributeProcessor">

class="org.springframework.beans.factory.config.ListFactoryBean">

[/PHP]

This is all "documented" in the iw-preview.war/WEB-INF/conf/livesite/resources/*config.xml. The first bean creates a deployment descriptor that says "when regex matches on vpath, apply this extraction file". The second bean defines the extraction processing class to use, and where to find the mapping file. The third bean registers our new descriptor with the PLC.

Then, create the mapping file. In this case (per the properties of the second bean), you want to create it at livesite_customer_src/etc/conf/livesite_customer/fieldmappings/ArticleFieldMappings.xml. For samples, look in iw-preview.war/WEB-INF/conf/livesite/fieldmappings, but it looks like this:

[PHP]

[/PHP]

Bowker

Rick -

This was very helpful thank you. It worked perfectly on our development server.

We copied the jar and war files

TeamSite\local\config\lib\content_center\livesite_customer_out\livesite_customer.tk.war & livesite_customer.jar

to our production server, did an iwreset -ui and iwreset -a but the metadata is not being produced.

The regular expression for the folder is correct (production folder names are the same as development). Any guess what is missed by this approach?