RM oslc query to get artifacts that match ID
One answer
Correctly using your query oslc.where=dcterms:identifier=123 will return the base artifact and the module bindings with that identifier, because these all have the same dcterms:identifier. The base artifact will have an rmNav:parent property - the folder it is stored in - and the bindings won't, instead they will have an rm:module property with the module URL.
To get more help you'll have to provide more information about what you expect and what you actually get:
- The complete query URL you're using
- The headers you're providing
- The response result
Edit this information into your question above
Comments
I am using the following url
Headers:
Configuration-Context:<configcontext>
Can you please suggest the changes to get all artifact details (where artifact id is 123)?
See the OSLC Query specification https://docs.oasis-open-projects.org/oslc-op/query/v3.0/os/oslc-query.html
Not sure about using parameter oslc.query, AFAIK oslc.where is the correct way to specify an OSLC Query, see the specification.
If you're going to use a prefix like dcterms then you need an oslc:prefix= parameter to specify the value of each prefix - note the formatting of this, see the specification.
You need to be careful to url encode the values for all parameters - e.g. the bit after the oslc.where= - this is an example of a complete query URL https://jazz.ibm.com:9443/rm/views?oslc.query=true&projectURL=https%3A//jazz.ibm.com%3A9443/rm/process/project-areas/_DSxBkLFXEe-j4_rM2KKkmw&oslc.prefix=dcterms%3D%3Chttp%3A//purl.org/dc/terms/%3E&oslc.where=dcterms%3Aidentifier%3D123&oslc.select=%2A - this is a requirement of the HTTP protocol, i.e. nothing to do with DOORS Next or ELM.
Add parameter oslc.select=* to get all the properties in the results, as in the example above. This is described in the specificaiton.