<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Colabrativ, Inc. &#187; search</title>
	<atom:link href="http://www.colabrativ.com/tag/search/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.colabrativ.com</link>
	<description>An Experiment Documentation and Electronic Notebook Provider</description>
	<lastBuildDate>Tue, 28 Oct 2014 04:44:35 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Cleo (Clinical Entry and Operations) Patient Treatment Queries</title>
		<link>http://www.colabrativ.com/cleo-patient-treatment-queries/</link>
		<comments>http://www.colabrativ.com/cleo-patient-treatment-queries/#comments</comments>
		<pubDate>Sat, 30 Nov 2013 03:19:31 +0000</pubDate>
		<dc:creator>Marc Whitlow</dc:creator>
				<category><![CDATA[Announcement]]></category>
		<category><![CDATA[Clinical]]></category>
		<category><![CDATA[patients]]></category>
		<category><![CDATA[search]]></category>
		<category><![CDATA[treatment]]></category>

		<guid isPermaLink="false">http://www.colabrativ.com/?p=776</guid>
		<description><![CDATA[We are pleased to announce that Cleo, Colabrativ&#8217;s Clinical Entry and Operations application now has a treatment query that allows a researcher explore the patient treatments in Cleo&#8217;s clinical database. This option is a result of our ongoing collaboration with &#8230; <a href="http://www.colabrativ.com/cleo-patient-treatment-queries/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>We are pleased to announce that Cleo, Colabrativ&#8217;s Clinical Entry and Operations application now has a treatment query that allows a researcher explore the patient treatments in Cleo&#8217;s clinical database.  This option is a result of our ongoing collaboration with <a href="http://www.clearityfoundation.org/" target="_blank">The Clearity Foundation</a>, a non-profit organization dedicated to “improving treatment options for ovarian cancer patients.” </p>
<p>Treatment queries are under the Query tab in Cleo&#8217;s Explore application; see Figure 1.  Creating a Treatment query is a two step process.  First the contents of the treatment table are selected.  Then, the treatment table is filtered. </p>
<table style="border:0px solid white;">
<caption style="font-size: 12pt; padding: 4px;">Figure 1<br />Queries Tab in Cleo&#8217;s Explore Application</caption>
<tr>
<td style="border:0px solid white; padding: 0px;">
      <img src="http://www.colabrativ.com/images/Cleo_Queries_tab_0.png" width="640" alt="The Queries tab in Colabrativ&#8217;s Clinical Entry and Operations (Cleo) application before the creation of any treatment tables or any queries has been run."/>
    </td>
</tr>
<tr>
<td style="border:1px solid #40BCBF; test-align: center; font-size: 10pt; color: #606060; line-height: 115%;">Queries tab in Colabrativ&#8217;s Clinical Entry and Operations (Cleo) Explore application before the creation of any treatment tables, or any queries have been run.</td>
</tr>
</table>
<h3>Selecting Treatments Table Content</h3>
<p>Treatments in the treatments tables are grouped by patient, and chronologically ordered by the start date of each treatment.  There are a number of options that control the contents of a treatments table; each option is reviewed below. </p>
<table style="border:1px solid #CCCCCC;">
<caption style="font-size: 12pt; padding: 4px;">Treatment Table Options</caption>
<tr>
<th>Option</th>
<th colspan="2">Description</th>
</tr>
<tr>
<td>Treatments Included</td>
<td>
      <img src="http://www.colabrativ.com/images/Cleo_Treatments_Included_pull-down.png" alt="Treatments Included pull-down menu in Colabrativ&#8217;s Clinical Entry and Operations (Cleo) Explore application."/>  </p>
<p><strong>Single Treatment</strong> adds a single treatment to each row in the treatments table, and is the default for the Treatments Included option. </p>
<p>The <strong>Treatment and Post-treatment</strong> option adds both a treatment and the next treatment (post-treatment) to each row of the treatments table.  If the treatment is the last treatment and if a Deceased or Last Contact or Lost to Follow Up event is after the last treatment, then the Deceased or Last Contact or Lost to Follow Up event is added as the post-treatment. </p>
<p>The <strong>Pre-treatment to Post-treatment</strong> option adds three treatments to each row in the treatment table.  As with the Treatment and Post-treatment option above, Deceased or Last Contact or Lost to Follow Up events can be the final &#8220;post-treatment&#8221; for a patient. </p>
<p>The <strong>All Treatment</strong> option puts all of a patient&#8217;s treatments in a single row.  As with the Treatment and Post-treatment and Pre-treatment to Post-treatment options above, Deceased, Last Contact or Lost to Follow Up events can be the final &#8220;post-treatment&#8221; for a patient.
    </td>
</tr>
<tr>
<td colspan="2">&nbsp;<br />There are five therapy types that can be included in a treatments table. </td>
</tr>
<tr>
<td>Include Chemotherapies</td>
<td>If checked, chemoetherapy events will be included in the treatments table.</td>
</tr>
<tr>
<td>Include Complementary Therapies</td>
<td>If checked, complementary therapy events will be included in the treatments table, such as treatments with Curcumin.</td>
</tr>
<tr>
<td>Hormone Therapies</td>
<td>If checked, hormone therapy events will be included in the treatments table, such as treatments with Tamoxifen.</td>
</tr>
<tr>
<td>Include Immunotherapies</td>
<td>If checked, immunotherapy events will be included in the treatments table.</td>
</tr>
<tr>
<td>Include Vaccines</td>
<td>If checked, vaccine events will be included in the treatments table, such as MUC1 Dendritic Cell Vaccine treatments.</td>
</tr>
<tr>
<td colspan="2">&nbsp;<br />The next four Include options add additional information to the treatment table, including the patient&#8217;s immunohistochemistry (IHC) and genetic results. </td>
</tr>
<tr>
<td>Include Agent 0 1 Columns</td>
<td>If checked, agent columns will be added to the treatments table.  Each treatment agent in a treatment will have a 1 in the column labeled with that agent&#8217;s name.  This option was designed to facilitate cluster analysis.</td>
</tr>
<tr>
<td>Include IHC Results</td>
<td>If checked, the H-score for each IHC test run on the patient&#8217;s specimen collected just prior to the treatment. e.g. pretreatment specimen, will be added to a column that uses the IHC test code as the column header. </td>
</tr>
<tr>
<td>Include Full IHC Results</td>
<td>If checked, the intensity, percent positive cells and H-score for each IHC test run on the patient&#8217;s pretreatment specimen will be added to the columns that use the IHC test code as prefix for the column header. </td>
</tr>
<tr>
<td>Include Genetic Results</td>
<td>If checked, the results for each genetic test, such as polymerase chain reaction (PCR), fluorescent in situ hybridization (FISH) or next generation sequencing run on the patient&#8217;s pretreatment specimen will be added to a column that uses the test code as the column header. </td>
</tr>
<tr>
<td colspan="2">&nbsp;<br />There are a number of situations in which one might not want to include the next treatment in a table.  The next five options allow one to merge a number of difference treatment types into the treatment added to the treatments table. </td>
</tr>
<tr>
<td>Merge Neoadjuvant Treatments</td>
<td>If checked, neoadjuvant treatments will be merged with the following treatment.  The start date of the neoadjuvent treatment will be used as the start for the merged treatment, if it is before the start of the treatment.  A Neo flag will be added to the Flag column when a neoadjuvent merge is performed. </td>
</tr>
<tr>
<td>Merge HIPEC Treatments</td>
<td>If checked, Heated Intraperitoneal Chemoperfusion (HIPEC) treatments will be merged with the following treatment.  The start date of the HIPEC treatment will be used as the start for the merged treatment, if it is before the start of the treatment.  A HIPEC flag will be added to the Flag column when a HIPEC merge is performed. </td>
</tr>
<tr>
<td>Merge Maintenance Treatments</td>
<td>If checked, maintenance treatments will be merged with the previous treatment.  The end date of the maintenance treatment will be used as the end date for the merged treatment, if it is after the end date of the treatment.  A Main flag is be added to the Flag column when a maintenance merge is performed. </td>
</tr>
<tr>
<td>Merge Continuation Treatments</td>
<td>If checked, continuation treatments will be merged with the previous treatment.  The end date of the continuation treatment will be used as the end date for the merged treatment, if it is after the end date of the treatment.  A Cont flag is be added to the Flag column when a continuation merge is performed. </td>
</tr>
<tr>
<td>Simultaneous Treatments</td>
<td>If checked, treatments that overlap in time, but are of different treatment event types, e.g. a chemotherapy and a hormone therapy, will be treated as simultaneous.  The agents in the simultaneous treatment will be added to an inserted Simultaneous Agents column. </td>
</tr>
<table/>
<h3>Treatments Table Creation</h3>
<p>Once treatments table options have been selected, the table can be created without applying any filtering to it by clicking on the &#8220;Create&#8221; button; see Figure 2.  This is the only action that can be taken for the &#8220;All Treatment&#8221; Treatments Option.  The treatments table creation options are disabled after a treatments table has been created, but the options used to create the treatments table are still displayed. </p>
<p>Prior to the creating the treatments table it is a good idea to supply a title in the &#8220;Query Title&#8221; box.  The title may also be added after creating the table by filling in the &#8220;Query Title&#8221; box and clicking the &#8220;Update Title&#8221; button. </p>
<p>Once the treatments table has been created, it can be downloaded as a tab separated values (TSV) table by clicking on the green link.  For the All Treatments table in Figure 2, the link is PatientTherapies_2013-11-29_09-45-05.tsv. </p>
<table style="border:0px solid white;">
<caption style="font-size: 12pt; padding: 4px;">Figure 2<br />Queries Tab in Cleo&#8217;s After Creating an All Treatments Table</caption>
<tr>
<td style="border:0px solid white; padding: 0px;">
      <img src="http://www.colabrativ.com/images/Cleo_Queries_tab_All_Treatments.png" width="640" alt="The Queries tab in Colabrativ&#8217;s Clinical Entry and Operations (Cleo) application after creating an All Treatments table.  An All Treatments table puts all of a patient&#8217;s treatments in a single row.  The treatments table creation options have been disabled after the treatments table has been created."/>
    </td>
</tr>
<tr>
<td style="border:1px solid #40BCBF; test-align: center; font-size: 10pt; color: #606060; line-height: 115%;">The Queries tab in Colabrativ&#8217;s Clinical Entry and Operations (Cleo) application after creating an All Treatments table.  The treatments table creation options have been disabled, but still display the options that were selected when creating the treatments table, PatientTherapies_2013-11-29_09-45-05.tsv.</td>
</tr>
</table>
<h3>Filtering the Treatments Table</h3>
<p>Filters are applied to a treatments table by selecting a filter from the &#8220;Select Filter&#8221; pull-down menu.  There are a number of filters that can be applied to a treatments table.  Each filter is shown below. </p>
<table style="border:1px solid #CCCCCC;">
<caption style="font-size: 12pt; padding: 4px;">Treatment Table Filters</caption>
<tr>
<th><img src="http://www.colabrativ.com/images/Cleo_Queries_Select_Filter.png" alt="Treatment Table Select Filter pull-down menu in Colabrativ&#8217;s Clinical Entry and Operations (Cleo) Explore application;  Filters include: Cancer Codes, Cancer Stages, Cancer Grades, Patient Histologies, Platinum Response, Specimen Type, Platinum Response and Specimen Type, and Treatment Agents."/></th>
</tr>
<tr>
<td><img src="http://www.colabrativ.com/images/Cleo_Queries_Cancer_Codes_Filter.png" alt="Colabrativ&#8217;s Clinical Entry and Operations (Cleo) Cancer Codes filter: OVA, OVAG, FALL, PERI, MUL, etc."/><br />
  </tr>
<tr>
<td><img src="http://www.colabrativ.com/images/Cleo_Queries_Cancer_Stages_Filter.png" alt="Colabrativ&#8217;s Clinical Entry and Operations (Cleo) Cancer Stages filter: IA, IC, II, IIA, IIB, IIC, III, IIA, IIIB, IIIC and IV."/><br />
  </tr>
<tr>
<td><img src="http://www.colabrativ.com/images/Cleo_Queries_Cancer_Grades_Filter.png" alt="Colabrativ&#8217;s Clinical Entry and Operations (Cleo) Cancer Grades filter: G1, G2, G3, G4 and NA."/><br />
  </tr>
<tr>
<td><img src="http://www.colabrativ.com/images/Cleo_Queries_Patient_Histologies_Filter.png" alt="Colabrativ&#8217;s Clinical Entry and Operations (Cleo) Patient Histologies filter: S, E, MX, AD, CC, etc."/><br />
  </tr>
<tr>
<td><img src="http://www.colabrativ.com/images/Cleo_Queries_Pt_Response_Filter.png" alt="Colabrativ&#8217;s Clinical Entry and Operations (Cleo) Platinum (Pt) Response filter: sensitive, resistant, and not available (NA)."/><br />
  </tr>
<tr>
<td><img src="http://www.colabrativ.com/images/Cleo_Queries_Specimen_Type_Filter.png" alt="Colabrativ&#8217;s Clinical Entry and Operations (Cleo) Specimen Types filter: O, P, LN, and not available (NA)."/><br />
  </tr>
<tr>
<td><img src="http://www.colabrativ.com/images/Cleo_Queries_Pt_Response-Specimen_Type_Filter.png" alt="Colabrativ&#8217;s Clinical Entry and Operations (Cleo) Platinum (Pt) Response and Specimen Types filter."/><br />
  </tr>
<tr>
<td><img src="http://www.colabrativ.com/images/Cleo_Queries_Treatment_Agents_Filter.png" alt="Colabrativ&#8217;s Clinical Entry and Operations (Cleo) Treatment Agents filter."/> <br />Once an agent name has been entered in the Chemotherapy Agents box, a new box will be created for an additional agent name.  If the wild-card (*) is added as an agent then the filter will not remove treatment rows that match the agents supplied, but table row may have additional agents.  Without a wildcard, the number of agents must match the number of agents supplied in the filter.<br />
  </tr>
</table>
<p>After setting up the desired filters for treatments table click on the &#8220;Run Query&#8221; button.  The filtering will be applied to a preexisting treatments table, or a new treatments table will be created from the treatments table options which have been selected.  The starting treatments table can be downloaded using the green link supplied for it.  See Figure 3, in which the start treatment table link is Treatments_2013-11-28_11-08-16.tsv.  The number of patients, specimens and treatments are provided for before and after the filtering.  The filtered table can also be downloaded using the green link supplied for it.  See again Figure 3, in which the query results table link is Query_2013-11-28_11-08-16.tsv.  </p>
<table style="border:0px solid white;">
<caption style="font-size: 12pt; padding: 4px;">Figure 3<br />Queries Tab in Cleo&#8217;s After Filtering Treatments Table</caption>
<tr>
<td style="border:0px solid white; padding: 0px;">
      <img src="http://www.colabrativ.com/images/Cleo_Queries_Specimen_Type_Filtered.png" width="640" alt="The Queries tab in Colabrativ&#8217;s Clinical Entry and Operations (Cleo) application after using a specimen type filter of O and P on a treatments table."/>
    </td>
</tr>
<tr>
<td style="border:1px solid #40BCBF; test-align: center; font-size: 10pt; color: #606060; line-height: 115%;">The Queries Builder after using a specimen type filter of O and P on a treatments table.  The treatments tables created before and after filtering are Treatments_2013-11-28_11-08-16.tsv, and Query_2013-11-28_11-08-16.tsv, respectively.</td>
</tr>
</table>
<p>Multiple filters can be run at the same time by simply selecting another filter from the &#8220;Select Filter&#8221; pull-down menu.  After a Query has been run, additional filtering can be performed.  For example, one might want to first filter on Cancer Codes and then Patient Histologies initially, and then to use the resulting filtered treatments table as the starting table for several treatment agents filterings. </p>
<h3>Select Query</h3>
<p>Just below the Query Builder banner is the &#8220;Select Query&#8221; pull-down menu (see Figure 3).  All of the queries that have been run are displayed in this pull-down menu with their time-stamps plus their queries titles.  To clear the query, an empty query can be selected from the &#8220;Select Query&#8221; pull-down menu.  When a query is selected, the Query Builder panel will be cleared and replaced with the selected query&#8217;s information.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.colabrativ.com/cleo-patient-treatment-queries/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Introduction of iExperiment Search</title>
		<link>http://www.colabrativ.com/introduction-of-iexperiment-search/</link>
		<comments>http://www.colabrativ.com/introduction-of-iexperiment-search/#comments</comments>
		<pubDate>Sat, 12 Mar 2011 22:51:05 +0000</pubDate>
		<dc:creator>Marc Whitlow</dc:creator>
				<category><![CDATA[Announcement]]></category>
		<category><![CDATA[iExperiment]]></category>
		<category><![CDATA[Lucene]]></category>
		<category><![CDATA[search]]></category>

		<guid isPermaLink="false">http://www.colabrativ.com/?p=13</guid>
		<description><![CDATA[We are pleased to announce that iExperiment now has the ability to search your experiment record. iExperiment&#8217;s search is built on the open source Apache Lucene search engine library. &#160; iExperiment electronic notebook search user interface showing a carboxypeptidase purification &#8230; <a href="http://www.colabrativ.com/introduction-of-iexperiment-search/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>We are pleased to announce that iExperiment now has the ability to search your experiment record.  iExperiment&#8217;s search is built on the open source <a href="http://lucene.apache.org/java/docs/index.html" target="_blank">Apache Lucene</a> search engine library.</p>
<div style="text-align: center"><img src="../images/carboxypeptidase_purification_search_600.gif" alt="iExperiment electronic notebook search user interface showing a carboxypeptidase purification example" />&nbsp;</p>
<p><span style="font-size: 11px">iExperiment electronic notebook search user interface showing a carboxypeptidase purification example.</span></p>
</div>
<p>iExperiment&#8217;s new search interface is shown above. Like all search interfaces, ours has a query box and a submit query button. You can search specific fields in your experiment results. The specific fields are provided for you in the Add Field pull-down menu. In the example above, a general search is being performed on &#8220;carboxypeptidase&#8221; and a specific search on &#8220;purification&#8221; in the category &#8220;technique&#8221;.  For your convenience a &#8220;Clear Query&#8221; button is provided to begin new searches.  Each result contains the title and authors of the experiments found in the search, along with text fragments highlighting the search words.  The record title is linked to the full record.</p>
<div>
<p><strong>Search Fields</strong> are arranged in a hierarchical manner. The basis for the hierarchy is as follows:</p>
<p></p>
<div style="text-align: center;float: left"><img src="../images/add_field_pulldown.gif" alt="The top portion of the Add Field pull down menu in iExperiment electronic notebook search user interface." />&nbsp;<br />
<span style="font-size: 11px">The top portion of the Add Field pull down menu.</span>
</div>
<p><strong>Meta Data:</strong></p>
<ul style="list-style-type: none;">
<li>title, authors, institutions, last modified, projects,</li>
<li>state, and categories</li>
</ul>
<p><strong>Sections:</strong></p>
<ul style="list-style-type: none;">
<li>purpose, introduction, plan, methods, results,</li>
<li>summary, and conclusions</li>
</ul>
<p><strong>Materials:</strong></p>
<ul style="list-style-type: none;">
<li>animals, strain, species, consumables, lot number,</li>
<li>expiration date, equipment, serial number,</li>
<li>reagents, formula, pH, samples, part number,</li>
<li>suppliers names, address and URL</li>
</ul>
<p><strong>Content:</strong></p>
<ul style="list-style-type: none;>
<li></li>
<li>and data category
<ul style="list-style-type: none;>
<li>attachment, figure, file name, caption, sample set, </li>
<li>and data category</li>
</ul>
<p><strong>Search Tips:</strong> The <a href="http://lucene.apache.org/java/3_0_3/queryparsersyntax.html" target="_blank">Lucene query parser syntax</a> used in iExperiment&#8217;s search function is summarized in the table below.</p>
<table>
<thead>
<tr>
<th width="75">Qurey Type</th>
<th width="140">Example</th>
<th>Discussion</th>
</tr>
</thead>
<tbody>
<tr>
<td>Single Term</td>
<td>protein</td>
<td>For a single term like &#8220;protein&#8221;, the program will be searched for the word &#8220;protein&#8221; in all of the records the user has permission to view.</td>
</tr>
<tr>
<td>Single Character Wildcard</td>
<td>te?t</td>
<td>The single character wildcard is a question mark (?).  Our example &#8220;te?t&#8221; will match both &#8220;te<span style="color: red">s</span>t&#8221; or &#8220;te<span style="color: red">x</span>t&#8221;.  A wildcard cannot be the first character of a search term.  If you do place a wildcard at the beginning of a word, you will receive a message reminding you about this limitation.</td>
</tr>
<tr>
<td>Multiple Character Wildcard</td>
<td>carbo*</td>
<td>The multiple character wildcard is an asterisk (*).  Our example &#8220;carbo*&#8221; will match &#8220;carbon&#8221;, &#8220;carbonic&#8221;, &#8220;carbonyl&#8221;, and many other similar words.</td>
</tr>
<tr>
<td>Fuzzy Searches</td>
<td>carbo~</td>
<td>Lucene fuzzy search uses the tilde character (~).  Our example &#8220;carbo~&#8221; will match both &#8220;carbon&#8221; and &#8220;harbor&#8221;.</td>
</tr>
<tr>
<td>Phrase</td>
<td>&#8220;protein purification&#8221;</td>
<td>A phrase is a group of words enclosed within quotes.  The search returns exact matches to the phrase.  Without the quotes, the search looks for any records that contain any of the words.</td>
</tr>
<tr>
<td>Proximity Searches</td>
<td>&#8220;phosphate sodium&#8221;~3</td>
<td>A proximity search contains a group of words in quotes with a tilde character (~) after the last quote mark, followed by an integer.  The integer is the number of hops a word must make to match the phrase.  Our example will find &#8220;phosphate sodium&#8221;, &#8220;sodium phosphate&#8221;, and &#8220;sodium dihydrogen phosphate&#8221;.</td>
</tr>
<tr>
<td>Field</td>
<td>author:david</td>
<td>A field is denoted by a colon (:) after the field name followed by the field search term.  Field names must match exactly.  If the field is not exact, the search will return no matches.  We have provided an &#8220;Add Field&#8221; pull down menu, so the user do not have to remember the field names.</td>
</tr>
<tr>
<td>Range Searches</td>
<td>[2011-01-01 TO 2011-01-31]</td>
<td>Range searches are contained in a pair of square brackets[], and include a pair of terms separated by a &#8220;TO&#8221;.  Range searches are useful for searching dates.  Due to the <a href="http://en.wikipedia.org/wiki/Lexicographical_order" target="_blank">lexigraphical ordering</a> of words the year must proceed the month which proceeds the day.  Dates in iExperiment are stored as YYYY-MM-DD, where the YYYY is the year, MM is the numerical month, and DD is the numerical day.  Our example search will return experiments that have dates in January 2011.</td>
</tr>
<tr>
<td>AND Operator</td>
<td>protein AND purification</td>
<td>The default operator between search terms is OR.  Using the AND operator requires that the search return results that match both terms.</td>
</tr>
<tr>
<td>Required (<strong>+</strong>) Operator</td>
<td>protein +purification</td>
<td>The required operator is a plus sign (<strong>+</strong>) before a search term.  Our example will return results that contain &#8220;purification&#8221;, and may contain &#8220;protein&#8221;.</td>
</tr>
<tr>
<td>NOT Operator</td>
<td>purification NOT &#8220;lipid purification&#8221;</td>
<td>The NOT operator allows you to exclude terms from your searches.  A minus sign (<strong>-</strong>) can also be used as a NOT operator.  The example could be expressed as &#8216;purification -&#8221;lipid purification&#8221;.&#8217;</td>
</tr>
<tr>
<td>Grouping</td>
<td>title:(carboxypeptidae AND purification)</td>
<td>Terms can be grouped by enclosing the terms with parentheses ().  This is useful for performing both multiple term field searches, as shown in the example, and for controlling the logic of a search with AND and OR operators.</td>
</tr>
</tbody>
</table>
<p>For more details see <a href="http://lucene.apache.org/java/3_0_3/queryparsersyntax.html" target="_blank">http://lucene.apache.org/java/3_0_3/queryparsersyntax.html</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.colabrativ.com/introduction-of-iexperiment-search/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
	</channel>
</rss>
