Search long form

This page is not relevant for most users. We will explain more about these long form searches later.

In general, search looks for any string matches. So, if there is another collection called 'GearTest2', the search will return both 'GearTest' and 'GearTest2'. If you want an exact match, then use

srch.collection.match.exact_label = 'GearTest';

The set of terms you can match is defined by the scitran data model. There are many possibilities, but for beginners (and we are all beginners) the key terms are probably illustrated here.

srch.project.match.label = 'vwfa';
srch.project.match.exact_label = 'vwfa';
srch.session.match.name = '2016_05_10'
srch.collections.match.label = 'ENGAGE';    
srch.acquisitions.match.label = 'T1w 1mm'; 
srch.files.match.type = 'bvec';

srch.projects.bool.must(1).match.group = 'wandell';
srch.projects.bool.must(2).match.label = 'vwfa';

srch.sessions.bool.must{1}.range.subjectx0x2E_age.gt = year2sec(10);
srch.sessions.bool.must{1}.range.subjectx0x2E_age.lt = year2sec(15);

The search 'operators' are 'match', 'bool', 'must', 'should' and 'range'. For now, use the examples in the file s_stSearches.m. A more thorough document will appear.

Syntax on searches

[Search syntax](Search syntax)

Notes for Gear-heads

Matlab uses '.' in structs, and json allows '.' as part of the variable name. So, we insert a dot on the Matlab side by inserting a string, x0x2E_. For example, to create a json object like this:

s = {
"range": {
	"subject.age": {
   		  "lte": 315576000
	    }
       }
  }

We use the code

 clear srch; 
 srch.range.subjectx0x2E_age.lte = years2sec(10);

(time values, including dates, are stored in SI units, seconds).

jsonwrite(srch,struct('indent','  ','replacementstyle','hex')) 

Parses the hex.

Another issue is the use of _ at the front of a variable, like _id

In this case, we cannot set a structure variable with a leading underscore, such as srch._id. But we can set

 srch.projects.match.x0x5F_id = projectID;

Again jsonwrite(srch,struct('indent',' ','replacementstyle','hex')) parses the string and the variable becomes simply _id, in the json data, without all the x0x5F nonsense.