Is this possible?

Jonathan_Haguewood_(jhaguewood_-_(deleted))

Hey everyone,I need to know if this is possible and would appreciate any insight you may have to offer.We will be having some scanned financial documents ported into livelink in bulk. Each image file will somehow have a unique id associated with the document as metadata(an attribute of some kind)Within a .net application, is it possible to find a document based on that unique attribute, dynamaically build a url path to the document and open the image in a browser?I know it's possible to build the url if we have the unique id livelink creates for each document. My two big concerns are creating the url based on an id that is associated with the file that is not the ID livelink created. My second concern is being able to open the image in a browser.Thanks everyone!Jonathan

Find more posts tagged with

Comments

eLink User

Message from Nair, Krishnankutty [Contractor] <Krishnankutty.Nair@anadarko.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">RE: Is this possible?

Anything is possible ….

-----Original Message-----
From: eLink Discussion: LAPI Discussion [mailto:lapi@elinkkc.opentext.com]
Sent: Thursday, August 31, 2006 2:00 PM
To: eLink Recipient
Subject: Is this possible?

Is this possible?
Posted by Haguewood, Jonathan on 08/31/2006 02:55 PM

Hey everyone,

I need to know if this is possible and would appreciate any insight you may have to offer.

We will be having some scanned financial documents ported into livelink in bulk. Each image file will somehow have a unique id associated with the document as metadata(an attribute of some kind)

Within a .net application, is it possible to find a document based on that unique attribute, dynamaically build a url path to the document and open the image in a browser?

Appnair:When you say unique attribute is the attribute put into livelink in any category then querying llattrdata should give you the livelink ObjID.

I know it's possible to build the url if we have the unique id livelink creates for each document. My two big concerns are creating the url based on an id that is associated with the file that is not the ID livelink created. My second concern is being able to open the image in a browser.

Appnair:This really did not make sense to me.If you put a document,url or folder in livelink then LL is supposed to manage it until its life time.

Are you saying something like if 999999 is the ObjID in livelink of the document having the unique attribute ID 1111111
You would rather show 1111111 to the user and then map 999999 behind the scenes ?Then it is just a mapping deal correct.Also new livelink allows you to nick name objects .Would that work.

. My second concern is being able to open the image in a browser.Appnair:This apparently is not livelink functionality,but desktop file associations.If you set the mime type correctly in livelink,LL will server the document correctly,wouldn't it?

Thanks everyone!

Jonathan

[To reply to this thread, use your normal E-mail reply function.]

============================================================

Discussion: LAPI Discussion
https://knowledge.opentext.com/knowledge/llisapi.dll/open/765428

Livelink Server:
https://knowledge.opentext.com/knowledge/llisapi.dll

To Unsubscribe from this Discussion, send an e-mail to unsubscribe.lapi@elinkkc.opentext.com.

*Please note my E-Mail Address has changed. Please
update your contact list*

Anadarko Confidentiality Notice:
This electronic transmission and any attached documents or other
writings are intended only for the person or entity to which it is
addressed and may contain information that is privileged,
confidential or otherwise protected from disclosure. If you have
received this communication in error, please immediately notify
sender by return e-mail and destroy the communication. Any
disclosure, copying, distribution or the taking of any action
concerning the contents of this communication or any attachments by
anyone other than the named recipient is strictly prohibited.

Janusz_Frydecki

If you got at least Livelink 9.5, what you could use is the new nickname field.This can be set using UpdateObjectNickname of the Documents API. Once this is done, you can use this type of url:http://livelink.services.mrq/livelink/llisapi.dll/open/[nickname]I think this would be the easiest way.Also, if you still need to "search" for it, you can use the GetObjectIdByNickname and then use this id for other Documents API functions.About displaying the image, if you retrieve the data using the API (instead of the nickname URL), you would use response.outputStream property within a stream writer or use the BinaryWrite function if you need to manipulate the stream before sending it. Don't forget to set the contentType attribute of the response object on your aspx page.You may have to set the content-disposition header if you want to define the filename. See thishttp://support.microsoft.com/kb/q260519/Louis

eLink User

Message from Carsten Kulms via eLinkWith LES 9.6 it is possible to open a page in the browser which loadsthe requested document by the unique attribute without even using theLAPI.However, as already said, it is neccessary to search for the document.The approach is to search via the Livelink Search API and transformingthe result by XSLT to a HTML page which redirects to the document, e.g.by the attached XSL.The XSL has to be placed in the support directory of the LESinstallation and the URL to do the search will look like{LES baseURL}?func=search&lookfor1=allwords&where1=Attr_9023_2:"EXTID0001"&outputformat=xml&stylesheet=llsxml2html.xslwhere "Attr_9023_2" is the internal name of the category attribute to search.(You find this name in the regions configuration of the correspondingSearchManager.)"llsxml2html.xsl" is the XSL file"EXTID0001" is the unique ID of the document stored in the categoryattributePlease note that I do _not_ recommend to do it this way.Also the attached XSL is just an example - it does not handle errors,e.g. if no document was found.P.S.:You can find documentation on the Livelink Search API here:https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=5557936&objAction=browse