Savitha,
ok.
You seem to have a lot of styles in there... really needed?
The search field customization UI is something new to me.
What do you plan beyond an ability to tune the schema.xml file?
(so basically, what you should do is write a comment-rich schema that sticks to the way
things will come from XWiki)
Your current implementation seems to consider the content only inside pages.
The big big strength of XWiki is in objects and properties. You should jump to tutorials
and see how different applications use that. One that I can tell you all details about is
Curriki but that is not the simplest!
Moreover, attachments, and their indexing, should be considered.
There's probably more modern but the tutorial of Vincent about the TODO list on
theserverside.com gave me a good clue of the objects practice.
One UI, related to field tuning, that I'd love you implement as well is the
"indexed view" of a document: a table with the analyzed view of each field for a
given document.
http://draft.i2geo.net/static/paultmp/i2geo-IndexDoc-TangentenundderSatzdes…
This is from the Admin interface using
i2geo.net Lucene plugin (source at
http://svn.activemath.org/intergeo/Platform/i2gCurriki/plugins/lucene/ )
Right now I'm playing around with XWiki to get a
better idea of the
available features so that it would be useful while indexing. Also, it
would be nice if you could suggest me some JIRA issues.
have a look here:
http://jira.xwiki.org/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery=p…
there's an amount!
I wonder if something around the queue is not something you should address now; I
don't remember having seen this in your code and there's an amount of issues that
the queue in the solr component should not have.
I think it's good to look at things compared to your plans, even include expected
fixed bugs as you wrote in the current plan page.
paul