#1 - One example where you'd make IsPrivate=true is if you were to write a

crawler for logs from Event Viewer. You wouldn't want that to be

searchable in general site search. Ideally one would write a new control /

module to search just those by using the SearchAPIs by supplying that

SearchTypeId itself. Default is false, so you are good to go.

#2 Yes you should delete them separatelty by passing the correct UniqueKey

in DeleteSearchDocument API. Just so you know Lucene does not physically

remove the data from Lucne when Delete is issued, it simply flags it that

way. Ideally Host>Compact button should be clicked periodically to reclaim

space.

#3 We don't crawl user details, it's in the road map though. So you'd need

to build a SearchType for Users and index the details. Likewise, another SearchType will be needed for the 3rd party data store.

Basic Search (skin object on top right corner of every page) - I think you can use it as is, it does categorization by itself.

Main Search Page - We don't have a way to display user's bio or thumbnail, however I think you can easily make a copy of the SearchResults module and have your functionality. You need to make sure you make a copy of the WebAPI service as well. The SearchResults module is nothing but JavaScript and a WebAPI backend, you need to tweak both of these. WebAPI is located under DotNetNuke.Web.InternalServices.SearchServiceController, while JS is located under Website\DesktopModules\Admin\SearchResults\dnn.searchResult.js

Answers to other questions:

1. Friendly Display Name for Search Type - This can be set by adding entries in Website\DesktopModules\Admin\SearchResults\App_LocalResources\SearchableModules.resx file you need an entry for Crawler_SearchTypeName.text (e.g. Crawler_custom1.text)

2a. Grouping is strictly done by Url. However, you can have your custom grouping by modifying GetGroupedDetailViews method in the WebApi backend.

2b. That is correct.

3. That's a good question. The framework is extensible and you can certainly create your own module. However, you need make sure you merge the fixes yourself should there be any in future. Given the special grouping you need and additional details about User (bio and image), you are better off creating a copy of the SearchResults module - make sure you give it a different name though.

---

Ash Prasad
Director of Engineering
DNN Corp.

That's correct, if the UniqueKey already exists in the index then we delete the old SearchDocument first and then add new. I'd the intent is Update, make sure you fill I'm all the properties of the SearchDocument, not just the changed properties. E.g. User changed Title of a post, you still need to fill other details that you had in the original doc, such as body, tags, etc, This is different from SQL, where you can update just one column, Lucene is actually NoSql, where Update is different.

---

Ash Prasad
Director of Engineering
DNN Corp.