nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Search via WebServices

Jay_Lehmann

Hi,

I am trying to search Livelink via the WebService - and am having some trouble accessing all of the fields. Is there a way to determine the object id (or ultimately a "download" link) for the return results -- or the object type?

I am able to return the data id (ie: DataId=10086839&Version=0) -- but I would like to create a "download" link for all document/files, and an "open" link for folders & urls.

Thanks,

Jay

Find more posts tagged with

Comments

Jay_Lehmann

Using this example, I was able to retrieve the following results:

Item #1 (ID=DataId=9xxx1&Version=2)
[s] Location=2000 1xxx0 7xxx3 1xxx9 9xxx4 9xxx1
[s] MIMEType=application/msword
[s] Name=ABCDEF.doc
[i] Score=74

MIMType works well for determining the type of document - but it is blank for both Folders and URL results ... is there anyway to retrieve the Livelink "type" of those objects?

Also, I am still unable to go from the "ID" provided above to an "Open" or "Download" link ...

Thanks in advance.

Carsten_Kulms

To open the current version of a document of which you know the DataID you can use an URL of the formathttps:///open/You find such an URL in at the top of this e-mail. (That is for a forum entry, but the mechanism is the same.)The action "open" may not always map to that "open" you want, it depends on the configuration.Another possibility is the `long version?https:///?func=doc.Fetch&nodeid=&docTitle=&vernum=

You find such an URL in the e-mail received for your last post in this forum (the example you mentioned).For download the format is https://?func=ll&objId=&objAction=download&vernum=

> MIMType works well for determining the type of document - > but it is blank for both Folders and URL resultsWhat mimetype do you expect for a folder?A folder object itself has no content (it has children).Similar holds for URL objects (the just contain the reference/URL, no content)

Jay_Lehmann

Hi Carsten ... thanks for the reply.

Do I need to parse the dataID out of the "ID" returned by the webservice (in the form "DataId=9943371&Version=2") -- or is there another way to access the dataID? I can write some code to do that, but I was hoping that the webservice would return the dataid seperatley, but I can't find it in the results ...

As for the MIMEType ... I'd like to generate the appropriate link for the user to click - depending on the type of the object.

If the object is a PDF or Word Doc, I'd like the link to "download" the document - so the user can immediately access the document. If the object is a folder, the link should take the user direct to the Livelink page ("http://base/open/dataID" works perfectly for that, thanks!) ... and if the object is URL like, I would ultimately like to be able to link the user directly to the target URL.

Because the search is returning a blank "MIMEType" for both folder and URLs, I do not know how to determine what type of object they are ... I was hoping to also return the Livelink Type (144, etc) to determine what type of object I was dealing with.

Thanks again for your help ... I appreciate it!

- Jay

Kyle_Swidrovich

Hi Jay,

The OTDataID field will have the DataID you are looking for.
Similarly, the OTVersion field will give you the version number, the OTSubType field will give you the numeric subtype of the object (e.g., a document is 144) and OTSubTypeName will give you the name of the subtype (e.g., "Document").

For more information on the available search regions, please review the Admin online help in Content Server.

Keep in mind that these will need to be marked as "Displayable" regions on the Search Manager's regions page on the Content Server side before you will be able to retrieve their values for each search hit.

Kyle

Appu_Nair

Of otsubtype is available in the results you could use that

OtSubtype=144 is a document (PDF,Doc,XLS etc etc etc)

OtSubtype=140 is a URL

OtSubtype=0 folder

If you have access to this page(/../llisapi.dll?func=admin.adminfactories) you can see what the friendly names of the subtype object is likewise

A sysreport can give you. Greg has at his site an elaborate listing http://www.greggriffiths.org/livelink/reference/subtypes/

Un common subtypes you will have to figure that out.

When I did a xml search project I am sure in the returned list the api would give me even a download link with the right things that is

I did not have to parse dataid and make up the link. is there anything in webservices that prohibits you from calling the

Search api.I even put it out here as a link hope it works now..

http://communities.opentext.com/communities/cs.exe/open/7960581

From: eLink Entry: Content Web Services Forum [mailto:otdncontentwebservices971forum@elinkkc.opentext.com]
Sent: Thursday, February 10, 2011 10:17 AM
To: eLink Recipient
Subject: RE Search via WebServices

RE Search via WebServices

Posted by jlehmann@newfield.com (Lehmann, Jay ) On 2011/02/10 11:16

Hi Carsten ... thanks for the reply.

Do I need to parse the dataID out of the "ID" returned by the webservice (in the form "DataId=9943371&Version=2") -- or is there another way to access the dataID? I can write some code to dothat, but I was hoping that the webservice would return the dataid seperatley, but I can't find it in the results ...

As for the MIMEType ... I'd like to generate the appropriate link for the user to click - depending on the type of the object.

Thanks again for your help ... I appreciate it!

- Jay

[To post a comment, use the normal reply function]
Topic:	Search via WebServices
Forum:	Content Web Services Forum
Livelink Server:	knowledge-wlweb01

Jay_Lehmann

Kyle ... those regions are turned off in our system, which now makes sense why there weren't being returned.

I will work with our Admins to get them enabled.

Thank you very much for the help!

Jay_Lehmann

Thanks Appu ... that's just what I needed.