oslc.where

The oslc.where parameter is comparable to the ‘where’ clause in SQL.  It allows you to narrow down the collection of resources selected, based on criteria of the data in the resources.  When querying a resource collection, the result could be 0, 1 or more resources.

Using this URI, http://localhost/maximo/oslc/os/oslcwodetail, that has no oslc.where clause will return all resources in the collection (each represented by a URI):

You can add the oslc.where to limit the collection of resources returned.  In this example it is limiting the collection to a shortTitle = 1002 (shortTitle is the Maximo WO number).

The result of this request is a single resource URI:

Using the URI in the response shown above you could use that to query the full details of

Work Order 1002.

Note: If you wanted some (such as the Wonum & Desc) selected properties returned along with the URIs in the collection you can use the oslc.select parameter in addition to the oslc.where parameter.   This would be similar to the Maximo Wotrack application’s List tab where a collection of work orders are displayed and in that list are selected fields, such as the work order number, description status etc.  Here’s an example:

 Result:

Similar to the Where clause used in an SQL statement, the oslc.where can perform multiple operations such as =, !=, >, <, <=, >= .  It can also support a ‘like’ operation and an IN operation.  When two (or more) properties are specified in the where they are executed with an AND condition meaning both conditions have to be satisfied.  Currently the oslc.where does not support the OR condition between multiple properties.

The example below shows the two properties being used in the oslc.where with the = and > operators

 Result: