Changes between Version 50 and Version 51 of BluePrint/TextSearch


Ignore:
Timestamp:
05/01/13 07:00:43 (9 years ago)
Author:
Vishrut Mehta
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/TextSearch

    v50 v51  
    1111=== Global Search ===
    1212'''(Do this if time permits)'''
    13 *    It will provide users to search for a particular query really quick over multiple resources together(eg. Organization, Hospital, etc.).
     13*    It will provide users to search for a particular query really quick over multiple resources together(eg. Organization, Hospital, etc.).[[BR]]
     14'''(Note: For the GSoC Project, we will try to make the basic structure of the global search and extending its functionality and a nice UI display will be out of the scope of this project. This work can be done as a post GSoC work)'''
    1415
    1516== Stakeholders ==
     
    205206
    206207Result:
    207 <The line containing the query(string to be searched) text> <Resource><Document Name>
    208 The path of the file, its file format, uploaded date-time  
    209 <the snippet of 2-3 lines of that document>
     208<The line containing the query(string to be searched) text> <Resource><Document Name>[[BR]]
     209The path of the file, its file format, uploaded date-time [[BR]]
     210<the snippet of 2-3 lines of that document>[[BR]]
    210211
    211212This will be format for the UI display for each matched record.
     
    217218==== Global Search ====
    218219
     220*    At first, we need to index the uploaded document by defining a new onaccept method for this global search.
     221
    219222*    We will look a the design implementation of IFRC template, and add the global search text box using S3Filter and S3TextFilter.
    220223
    221 *    We would not search for a particular record over here, but would filter all widgets for common context. As Dominic guided me, the solution is generic - i.e. it can use any filter widget (text, options, date/time etc.) - but requires the configuration of a context link for every resource (e.g. how is the resource linked to the event).
    222 
    223 *    For eg. If I configure a S3Profile page with a bunch of resources, introspect all text fields in the respective tables. After doing this, configure them as context links, and then add an S3TextFilter for this context.So thus,  then this would let me search for text phrases through all these resources.
    224 
     224*    We would need to '''flatten''' the records and its components into a text representation.
     225
     226*    After doing this, we need to include the important information of the resource as well as the important information of its component in form of List.
     227For eg. list(or a dictionary) would be like "Sectors: Food, Something Else, Another Sector"
     228"Type: Organisation, Name: <name of org>"
     229
     230*    After getting this information, this is when Solr will come into play and will do the full-text search on these information. So we wold get the information of the search results doing the REST calls and thus we need to output the search results.
     231 
    225232*    After doing this and filtering out the common context, we would need a UI to display it. It would be simple, user friendly and categorized. Showing it in a much better way would be for future implementation.
    226233 
     234*    The UI presentation will be a '''Categorized display''', something like:
     235Search: DRR
     236
     237Result:
     238
     239Sector "DRR":
     240    (Records corresponding to this)
     241  - 5 Projects related to "DRR"
     242  - 7 Programmes related to "DRR"
     243  - 3 Events related to "DRR"
     244
     245Location "Taiwan DRR Centre":
     246
     247  - 1 Event related to "Taiwan DRR Centre"
     248  - 5 Staff Members related to "Taiwan DRR Centre"
     249
     250...and so forth.
     251
    227252== References ==
    228253