Hi Mike,
I have replied to similar threads in the KB .One should understand the mechanism of a livelink document ingestion.
case 1-using the livelink GUI.Here the file is either uploaded or streamed to the livelink webserver from its source.The node(dataid) is allocated and its version is being set.At this point the livelink server has to extract your header info.Many MS software products like VB,C#,Jscript etc can be used to read this info.However oscript(livelinks language) does not easily understand MS interfaces.Hence it is necessary to write code at the livelink side to do this.OT Australia has a paid module for this.Consider contacting Andrew Foti at open text for details.You will have to either create a COM package and develop this logic,or create a java class file to wrap the logic.The livelink search engine does index meta data from the document hence that is another way to attempt it.
Case 2:If the document is uploaded by an app ,then it isprobably written not in oscript.Here interfacing with MS software and livelink is a little more easier.Livelink interaction would be either thru lapi or webservices.
Case 3:OpenText wants you to do all your programming using their Enterprise connect framework which is catually the replacement for Livelink explorer.It does provide hooks into major enterprsie suites like MS Office or SAP.
Case 4:Well the transmittals package of OT has a module that probably was developed by the ausrtailian wing.In its outset it could set variables of a word macro by oscript.I looked at it when I was working on the project.
I am not aware of out of the box tools although if you know perl programming,you could use a LES pipleine and store word metadata with a category data in livelink although it won't get into the word header.
Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008
