Any way to get default URL for a node?

Hi,

I so far haven't seen this, and I suspect that it's non-trivial, but what if I want to be able to get the default URL for a particular node? I checked in the REST API and there doesn't seem to be any property there either that defines what is this node's default URL.

Here's the use case: Client app, that is web based is responsible for all interaction with Content Server. Currently, they are using Web Services API. We have Brava! in the mix, and for docs that are of a MIME type that are not supported by Brava, we want to have the application simply download the document and present it through it's interface, while if it's a Brava-able document, the application would simply return the Brava URL to the user. Currently the application is hard-coded to do the latter for all documents which isn't quite what we want.

I'm ideally trying to find a way with Web Services to get whether the document is Brava enabled, or if I could get its default URL which would give me roughly the same info. I'm also exploring using the REST API which I already have a Java wrapper built for to allow for quick integration.

If this is not possible without extending either WS or REST, that's fine, I'll simply tell the client that.

Thanks in advance

-Hugh Ferguson

Find more posts tagged with

Comments

Ferdinand Prantl

The problem is the term "default node URL" itself. There is no such global concept, AFAIK. You say, that you want to open Brava Viewer. Do you want a "default node URL" at all? Because otherwise there are similar concepts, which you can use. They open kind of "default page". You can continue to Brava by a second click. You can also execute other action, if you do not want to go to Brava.

Classic UI

The closest concept to the single "Node URL" is probably the "/open/{node_id}" action:

https://knowledge.opentext.com/knowledge/cs.dll/open/68457626

It works for any node type. The "link" action can be configured for "open" or "properties" in user settings:

https://knowledge.opentext.com/knowledge/cs.dll/link/68457626

Smart UI

There is a concept of the "node page" on the URL "/app/nodes/{node_id}":

https://knowledge.opentext.com/knowledge/cs.dll/app/nodes/15106294

It works for any node type.

Common

We do not have a "unified node page" yet, which could be either Classic UI or Smart UI, preferably configurable in user settings. We wait for customer feedback/requests.

HFCDev

Hi Ferdinand,

Close, and it almost works. For the case of Brava enabled documents, the Open link does invoke the Brava viewer, but fgor non-Brava enabled docs, it merely gives you the properties page. That's probably based on the fact the open link is used as the default URL. What I really need unfortunately is the ability to tell if the document *would* open in Brava or not.

Using REST, I can do this by doing a /v1/api/nodes/{nodeID}/actions command and getting back whether Brava! is in the node list. The main reason I was hoping to do the equivalent in WS is that the client already is using WS, and I didn't want them to have to convert to REST.

-hugh