[Registry-dev] Content Search - Excluding XML Tags

[Kalani]

Hi,


Chathura C. Ekanayake wrote:
> Hi Glen,
>
>   
>> Where does this "requirement" come from??  Also, when you say "text" I 
>> assume you mean both attribute values and tag content?
>>   
>>     
>
> Though this is not a critical requirement, we think it would be useful 
> to have such feature (Asankha suggested it too). For example, when we 
> are storing XML files with a particular schema, all the files contain 
> similar tags. Then if we want to search for some keyword and if the tags 
> of our schema contains that keyword, all XML files will be given as 
> search results. I agree that it is useful to support full text search 
> for XML as well. So I think it is better to come up with a solution 
> which provides both searches as you have proposed.
>
>   
>> I definitely think we need to index tags and namespaces - what if I want 
>> to search the Registry for all documents containing a <wsa:Metadata> 
>> element, or all documents that use a particular namespace's tags?
>>     
Yes. We should provide both type of searches. In previously suggested 
option the handler author is responsible for choosing the type of search 
(when the index is created). I also think that it is better if we can 
give that option to the user.
>> Lucene supports the notion of splitting content into different 
>> properties and then searching across one or more of these properties, 
>> right?  So if you want let's pull tags and namespaces into separate 
>> properties (I haven't thought this all the way through so I'm not 100% 
>> on the details) and then perhaps give the option to include them or not 
>> in the "default" search.  Can we look into something like that?
>>     
Yes. This can be done I guess. We can have two fields in the index and 
put tags and namespaces to a one field and tag content to the other. 
According to the user preference the search can be done over one or both 
fields. However we should have a proper way to get the user preferences.
>> Speaking of options, we need to come up with a general framework for 
>> storing user preferences (what search options do you like, etc) in the 
>> Registry itself and making them available to the UI code.
>>   
>>     
>
> I also thought of improving the support for users in the Registry. Good 
> solution would be to introduce user profiles to Registry, which stores 
> preferences, user details, photo :) , etc. Actually we can model user 
> profile as a resource, so that we can associate it with resources, build 
> user networks (management hierarchies, etc) and introduce many other 
> such user related capabilities.
>
> Thanks,
> Chathura
>   

Thanks,
Kalani
>
> _______________________________________________
> Registry-dev mailing list
> Registry-dev at wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
>
>