Which option to chose for retrieval

Hello All,

We are trying to understand the options we have to retrieve document category and attributes from Content Server?

Need suggestions on which option/API we need to chose. CWS, REST, Search API and AppWorks REST. I guess CWS is more matured and as far as I have seen REST doesn't seem to offer retreival capabilities.

Any pointers on each of the above mentioned would be great. Also we are open to any other better alternative.

Thanks!

Regads,

Vijay

Find more posts tagged with

Comments

AKropp

I can’t speak for AppWorks, but CWS, REST and Search are all valid approaches. CWS/REST can both do retrieve/update/add operations while Search would be read-only. I suppose it depends on what you need to do with it and what you prefer to work with that would dictate your choice. Maybe if you tell us a bit more about your end goal we can comment more about which option might be the better fit for purpose.

From: eLink Entry: Content Server Development Forum <development@elinkkc.opentext.com>
Sent: Friday, April 5, 2019 3:04 PM
To: eLink Recipient <devnull@elinkkc.opentext.com>
Subject: Which option to chose for retrieval

Which option to chose for retrieval

Posted bybharathiar.vijayakannan@hp.com (Vijayakannan, Bharathiar) On 04/05/2019 02:59 PM

Hello All,

We are trying to understand the options we have to retrieve document category and attributes from Content Server?

Any pointers on each of the above mentioned would be great. Also we are open to any other better alternative.

Thanks!

Regads,

Vijay

[To post a comment, use the normal reply function]
Forum:	Content Server Development Forum
Content Server:	My Support

Kyle_Swidrovich

The majority of what the Smart View presents is driven by the publicly-supported REST APIs, including category and attribute information retrieval on nodes.

What have you used as a reference for REST API capability?

The published documentation has a full resource called “categories”.

Kyle

Bharathiar Vijayakannan

Thanks Kyle.

I am trying to understand the options and have to suggest which option is the best in terms of retrieval (performance, stability and maturity of the API and so on).

May I ask if there is a code sample to retrieve something let's say categiries based on meta-data passed on the REST API call. I couldn't understand what's given in the documentation though.

Thanks!

Bharathiar Vijayakannan

Thanks Alex.

As I was mentioning to Kyle, the requirement that I have now is that we need retrieval based on the attributes passed in the REST call. Will check with the business team and get back with the exact requirement.

Thanks!

Kyle_Swidrovich

I'm still unclear on what you're trying to achieve.

You can retrieve nodes by their DataID. From that response, you can read metadata information, including category data, about that node.

You can also use the search engine to locate items based on any searchable metadata, and again, given a node from a search result, you can pull up metadata about that node.

You can also programmatically run a report (which must be designed ahead of time) that could pull information from the database, as necessary.

I would recommend becoming familiar with how one would perform this action via the UI first, then examine the available methods in the REST API documentation to achieve those same steps.

Quoted Bharathiar Vijayakannan on 04/10/2019 12:05 AM:

Thanks Kyle.

I am trying to understand the options and have to suggest which option is the best in terms of retrieval (performance, stability and maturity of the API and so on).

May I ask if there is a code sample to retrieve something let's say categiries based on meta-data passed on the REST API call. I couldn't understand what's given in the documentation though.

Thanks!