I have successfully installed Examine on one of my sites and am able to return results just fine. Here's my config:
<UmbLuceneIndex DefaultIndexSet="NICIndex" EnableDefaultActionHandler="true">
<!-- REQUIRED: MaxResults,IndexPath,SetName -->
<!-- NOT Required: IndexParentId. If not specified then then all documents are indexed, otherwise only documents as children of the id are indexed -->
<IndexSet SetName="NICIndex" IndexPath="~/data/indexes1/" MaxResults="100">
<IndexUmbracoFields>
<add Name="id" /> <!-- REQUIRED -->
<add Name="nodeName" /> <!-- REQUIRED -->
<add Name="updateDate" />
<add Name="writerName" />
<add Name="path" />
<add Name="nodeTypeAlias" /> <!-- REQUIRED -->
</IndexUmbracoFields>
<!-- The User defined fields to be indexed and searched. The UmbracoIndexer has methods to override the fields to be searched. -->
<IndexUserFields>
<add Name="contentPageTitle"/>
<add Name="bodyText"/>
<add Name="sidebarContent"/>
<add Name="adDescription"/>
<add Name="eventDescription"/>
<add Name="eventPrimaryLocation"/>
<add Name="departmentDescription"/>
<add Name="northeastNewsDescription"/>
<add Name="northeastNewsFile"/>
<add Name="dailyNewsClipFile"/>
<add Name="dailyNewsClipDescription"/>
<!-- <add Name="Content"/> Policies content
<add Name="Title"/> Policies title -->
<add Name="umbracoFile"/>
</IndexUserFields>
<!-- IncludeNodeTypes not required. If not specified, the indexer will index ALL document types
<IncludeNodeTypes>
<add Name="" />
</IncludeNodeTypes>-->
<!-- ExcludeNodeTypes not required. If specified, these node types will not be indexed. -->
<ExcludeNodeTypes>
<add Name="Alerts" />
<add Name="Alert" />
<add Name="Blank" />
<add Name="Container" />
<add Name="EmployeCornerLink" />
<add Name="Essential" />
<add Name="HomagepageBox" />
<add Name="QuickLink" />
<add Name="Police" />
</ExcludeNodeTypes>
</IndexSet>
</UmbLuceneIndex>
So, I wanted to add one more field to return in order to be able to link to document types that were returned with a media picker on them. I added 'dailyNewsClipFile' but when I try using it, it keeps throwing the error that this Key was not present??
switch (nodeType)
{
case "DailyNewsClip":
var mediaId = int.Parse(sr.Fields["dailyNewsClipFile"]);
var file = new Media(mediaId);
//url = file.Path;
break;
case "NNArticle":
url = "Northeast News";
break;
default:
url = umbraco.library.NiceUrl(sr.Id);
break;
}//end switch statement
I am obviously missing something. I even tried creating a new path for indexes to "start from scratch" but no luck.
Oooops, I was a little trigger happy with the post. Turns out it was in fact returning the key, but empty fields (empty 'dialyNewsClipFile') throw the ley not found error.
Glad to see you're using Examine and liking it. I know Shan is working very hard on it at the moment and will have a new drop coming soon. He's working on some new features which better handle clustered/ load balanced environments too :)
Sweet, glad to hear that. I know the plan is to have it as part of the 4.1 release which is great. I wish I could find some examples of PDF, and other document indexing for Examine. Does anyone know or care to share their implementation?
Sweet, glad to hear that. I know the plan is to have it as part of the 4.1 release which is great. I wish I could find some examples of PDF, and other document indexing for Examine. Does anyone know or care to share their implementation?
I'll ask Shan about it, but I believe you just have to find an indexer for Lucene which deals with PDF's (or any other file extensions). I haven't done a site which we've indexed PDF's though
As for PDF indexing (word indexing, etc...) This won't be built into Examine directly but Examine is hugely flexible with it's API. I'm not sure what version of Examine you are using but the latest version in the repository handles indexing media as well as content. If you want to index you're PDF info, then you can just attach to one of the Examine events, or create your own indexing provider (events are easier though). With events you can also add additional information to an index for a particular node. For instance you might want to bundle the information for some child nodes into the index for the parent node. Using the Examine events, this is fairly easy. I'm sorry i've been a bit slack with the documentation but I promise I'll have a full documentation suite available in the next month or so.
For examples of events, indexing, searching, config, etc... check out the latest repository check in and see the source code in the test usercontrols.
Key was not present... - Examine
Hi All,
I have successfully installed Examine on one of my sites and am able to return results just fine. Here's my config:
So, I wanted to add one more field to return in order to be able to link to document types that were returned with a media picker on them. I added 'dailyNewsClipFile' but when I try using it, it keeps throwing the error that this Key was not present??
I am obviously missing something. I even tried creating a new path for indexes to "start from scratch" but no luck.
Thanks for your suggestions!
-- Nik
Oooops, I was a little trigger happy with the post. Turns out it was in fact returning the key, but empty fields (empty 'dialyNewsClipFile') throw the ley not found error.
Thanks,
Nik
Glad to see you're using Examine and liking it. I know Shan is working very hard on it at the moment and will have a new drop coming soon. He's working on some new features which better handle clustered/ load balanced environments too :)
Sweet, glad to hear that. I know the plan is to have it as part of the 4.1 release which is great. I wish I could find some examples of PDF, and other document indexing for Examine. Does anyone know or care to share their implementation?
Thanks,
Nik
Sweet, glad to hear that. I know the plan is to have it as part of the 4.1 release which is great. I wish I could find some examples of PDF, and other document indexing for Examine. Does anyone know or care to share their implementation?
Thanks,
Nik
I'll ask Shan about it, but I believe you just have to find an indexer for Lucene which deals with PDF's (or any other file extensions). I haven't done a site which we've indexed PDF's though
So, this would be something that gets installed on the server and configured outside of Examine in other words?
As for PDF indexing (word indexing, etc...) This won't be built into Examine directly but Examine is hugely flexible with it's API. I'm not sure what version of Examine you are using but the latest version in the repository handles indexing media as well as content. If you want to index you're PDF info, then you can just attach to one of the Examine events, or create your own indexing provider (events are easier though). With events you can also add additional information to an index for a particular node. For instance you might want to bundle the information for some child nodes into the index for the parent node. Using the Examine events, this is fairly easy. I'm sorry i've been a bit slack with the documentation but I promise I'll have a full documentation suite available in the next month or so.
For examples of events, indexing, searching, config, etc... check out the latest repository check in and see the source code in the test usercontrols.
Cool, thanks Shannon, I appreciate the direction and will get the latest and give it a whirl.
Cheers,
Nik
Hi guys just wondering if someone had an example of using something like pdfbox and examine?
Hi All,
I am also about to build a client site that will have approximately 3,000 PDF's on launch and hence needs some form of indexing!
Have any of you managed to implement PDF indexing using Examine or Lucene?
Cheers,
Chris
Chris, Did you manage to find an example of PDF Indexing with Examine?
We are currently developing a similar solution and this would be extremely useful.
Thanks,
Chris
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.