Working with Queries
The Windchill RV&S OSLC Server provides query capabilities as per the OSLC Core 3.0 specification. Using query capabilities, based on supported domains, client applications can query or search for Windchill RV&S resources in a project. For example, to enable query capabilities for requirement and requirement document resources, the query property must be defined in the requirements-domain-mapping.json file. For more information on the query property, see query Property.
The client applications can navigate to the URIs for query capabilities through discovery of service provider catalogs and service provider resources provided by the Windchill RV&S OSLC Server.
The OSLC client applications can discover the URIs of the query capabilities by sending GET request on a project to the Windchill RV&S OSLC Server per the following URI:
GET <protocol scheme>://<server host name>:<server port number>/<context URI>/project/<project name>
For example:
GET https://localhost:3001/oslc/r/project/%2FProjects%2FRelease2
The client applications must set the Accept header to application/ld+json or application/rdf+xml as the content type in the GET requests to the Windchill RV&S OSLC Server. The OSLC clients must also set the OSLC-Core-version header to 3.0 when sending the GET requests. The response for such GET request includes URIs for the query capabilities.
Query capability is supported for both GET and POST requests.
For example, the Windchill RV&S OSLC Server supports the following URI with supported authentication for the query capability corresponding to the Windchill RV&S requirements:
GET <protocol scheme>://<server host name>:<server port number>/<context URI>/project/<project name>/requirements
For example:
GET https://localhost:3001/oslc/r/project/%2FProjects%2FRelease2/requirements
The Windchill RV&S OSLC Server supports the following URI with supported authentication for the query capability corresponding to the Windchill RV&S requirement documents:
GET <protocol scheme>://<server host name>:<server port number>/<context URI>/project/<project name>/contents
For example:
GET https://localhost:3001/oslc/r/project/%2FProjects%2FRelease2/contents
The following are some examples of OSLC query parameters for use with the query property attributes:
oslc.where query parameter
GET https://localhost:3001/oslc/r/project/%2FProjects%2FRelease2/contents?oslc.where=dcterms:identifier=4
GET https://localhost:3001/oslc/r/project/%2FProjects%2FRelease2/contents?oslc.where=dcterms:title=a*
oslc.orderBy query parameter
GET https://localhost:3001/oslc/r/project/%2FProjects%2FRelease2/contents?oslc.orderby=dcterms:identifier
The default sort order is ascending.
To request descending sort order, the request URI is as follows:
GET https://localhost:3001/oslc/r/project/%2FProjects%2FRelease2/contents?oslc.orderby=-dcterms:identifier
oslc.select query parameter
GET https://localhost:3001/oslc/r/project/%2FProjects%2FRelease2/contents?oslc.select=dcterms:identifier,dcterms:title
oslc.pageSize query parameter
GET https://localhost:3001/oslc/r/project/%2FProjects%2FRelease2/contents?oslc.pageSize=25
* 
The minimum page size is 25. If you specify page size less than 25, an error occurs.
The maximum supported page size is 200.