Folks,

I need to implement a module-specific search function and I'm wondering what the DNN best practice is for this.  The application is a media library where users want to search for media based on keywords they provide.

My module will implement ISearchable, which will get its data into the site-wide search.  I'm wondering what DNN search facilities are available that will allow me to restrict the search results to the content I report over the ISearchable interface?  So far, I see 2 alternatives:

1. Use whatever facilities DNN provides to help me.  So far, I haven't found any, but I'm assuming there must be a full text catalog somewhere for the DNN db.  Is there?
2. Create my own full text catalog just for the tables I need.  Then I can use SQL to query the appropriate tables against my own full text catalog.  Is this the best practice?  It doesn't leverage DNN facilities at all, though.
3. And I guess there is a 3rd alternative -- use Google.  But I haven't looked too deeply into this.  In this case, I would restrict Google results to my domain and tab ID (can I do this?  I know I can restrict to domain, but I would need to target specific pages that house my module), but if the admin moves the module around, the tab ID would not be fixed.  I'm assuming this would not be considered a DNN best practice, but it's worth throwing out there.

Which strategy best leverages the framework?  Or did I miss one altogether?

Thanks for your help!

AldenG

Thanks Sebastian!  You know, for my module, a LIKE statement is probably sufficient.  Thanks for your response!

AldenG