Newbie question: I think I saw this referenced somewhere, but I can't locate it now…
Is there a "trick" or additional step that has to be performed after installing a custom content model such that properties designated as "Indexed" will actually be indexed and searchable through the default share "keywords" and "simple searchbox"?
It seems like none of my custom properties are searchable even if I designated them to be indexed in the content model.
Do I have to reset the FT Index somehow so it rebuilds its schema or something like that?
If there's a link that explains it, I will be happy to "RTFM". Sorry I couldn't locate it myself, so I'm asking here.
-AJ
Is there a "trick" or additional step that has to be performed after installing a custom content model such that properties designated as "Indexed" will actually be indexed and searchable through the default share "keywords" and "simple searchbox"?
It seems like none of my custom properties are searchable even if I designated them to be indexed in the content model.
Do I have to reset the FT Index somehow so it rebuilds its schema or something like that?
If there's a link that explains it, I will be happy to "RTFM". Sorry I couldn't locate it myself, so I'm asking here.
-AJ
1 ACCEPTED ANSWER
It turns out this has gotten easier in Alfresco 4. The "search template" has been moved to a config file, so you do not have to override the entire search.lib.js file, which is a Good Thing.
So, if you are using Alfresco 4, here are the steps:
1. Copy $TOMCAT_HOME/webapps/alfresco/WEB-INF/classes/alfresco/templates/webscripts/org/alfresco/slingshot/search/search.get.config.xml to $TOMCAT_HOME/webapps/alfresco/WEB-INF/classes/alfresco/extension/templates/webscripts/org/alfresco/slingshot/search/search.get.config.xml
2. Edit $TOMCAT_HOME/webapps/alfresco/WEB-INF/classes/alfresco/extension/templates/webscripts/org/alfresco/slingshot/search/search.get.config.xml
3. Add your custom properties to the default-query-template element. For example, suppose I want to add sc
roduct and sc:version to the list of properties that are searched by default. My default-query-template element would look like this:
4. Save the file, restart Tomcat, & search!
If you are using a release older than Alfresco 4, the concept is the same, but instead of overriding search.get.config.xml you will override search.lib.js and change the QUERY_TEMPLATES constant.
Jeff
So, if you are using Alfresco 4, here are the steps:
1. Copy $TOMCAT_HOME/webapps/alfresco/WEB-INF/classes/alfresco/templates/webscripts/org/alfresco/slingshot/search/search.get.config.xml to $TOMCAT_HOME/webapps/alfresco/WEB-INF/classes/alfresco/extension/templates/webscripts/org/alfresco/slingshot/search/search.get.config.xml
2. Edit $TOMCAT_HOME/webapps/alfresco/WEB-INF/classes/alfresco/extension/templates/webscripts/org/alfresco/slingshot/search/search.get.config.xml
3. Add your custom properties to the default-query-template element. For example, suppose I want to add sc
roduct and sc:version to the list of properties that are searched by default. My default-query-template element would look like this:<search>
<default-query-template>%(cm:name cm:title cm:description sc:product sc:version ia:whatEvent ia:descriptionEvent lnk:title lnk:description TEXT TAG)</default-query-template>
</search>4. Save the file, restart Tomcat, & search!
If you are using a release older than Alfresco 4, the concept is the same, but instead of overriding search.get.config.xml you will override search.lib.js and change the QUERY_TEMPLATES constant.
Jeff
