Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Object Importer for existing document?

Status
Not open for further replies.

xrayslayer

IS-IT--Management
Mar 15, 2011
9
ID
Hi,

I'm Ray, pretty new in Livelink world.
I am going to move existing documents to other places using the bulk process.
Is it possible to use Object Importer for existing document that already stored in livelink?
Or should I use Object Exporter first then upload it again using Object Importer? If this is so, how to keep the document's categories?
Please advise.

Thanks!
 
First a little background.Object Importer came first.It was written to upload documents in legacy systems(file shares,filenet,dcoumentum) to livelink.In essentiality it is just a node instruction that used to look xml(now it is really xml) to livelink.People used this extensively in Physical Objects migration,record management projects because it was very easy to setup and very easy to understand the xml file.Note that no building blocks of livelink(eg the category object,classification object) are possible to be created by OI while it can be used to apply these on documents and folders.

Object Exporter-Allows you to move trees of livelink folders.The exported xml file is a file depicting the same syntax of OI.

Now for your 'Move' using OE/OI there is no real easy way to do this with these tools,but kludges can be contrived.

First you would export the files to be exported using OE.
Then you would manipulate the file instructions so that locations are updated to new locations.
When that is done you would re-import the first file changing the action of the document moved to delete.Note by this operation what you are essentially doing is copying and deleting the originals.All the business rukles(like your cats/atts have to be maintained)

Much more simply lapi,websvcs,oscript can actually do the move without doing the kludge.

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,Livelink ECM Champion 2010
 
BTW check if OI syntax allows Move.since it allows delete I have a feeeling that Move also may be supported.If I have time I will check as well

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,Livelink ECM Champion 2010
 
Thanks for your response.
I saw in the admin help for OI, they have the syntax <b>sync</b>
, which described as follows:
Sync: Performs a create or update depending if the object exists in Livelink.

But unfortunately, I couldnt find any details about how to use it.
Can u help me with that?

Thanks!
 
One more thing I have to say about

"Much more simply lapi,websvcs,oscript can actually do the move without doing the kludge."

We dont have any oscript/lapi currently in here. And if we want to use any other freeware/enhancement it will take long time since I need to gain approval from management first.

 
For eg check the right syntax in the examples that come with documentation
Code:
<node action="create" type="document">
<acl group="SYSLL_SCAN" permissions="111011101"></acl>
<acl basegroup=" LES Admins &amp; Developers" permissions="111111111"></acl>
<acl action="remove" standard="owner"></acl>
<acl action="remove" standard="world"></acl>
<category name="Livelink Categories:Financial:Vendor Correspondence">
	<attribute name="Vendor Number"><![CDATA[22222222]]></attribute>
	<attribute name="Vendor Name"><![CDATA[New Vendor Test]]></attribute>
	<attribute name="Document Type"><![CDATA[Miscellaneous]]></attribute>
	<attribute name="SAP Document Number"><![CDATA[434343]]></attribute>
	<attribute name="Invoice Number"><![CDATA[66666666]]></attribute>
	<attribute name="Invoice Number"><![CDATA[77777777]]></attribute>
	<attribute name="Invoice Number"><![CDATA[88888888]]></attribute>
	<attribute name="Capture Date"><![CDATA[20100307]]></attribute>
	<attribute name="Processed Date"><![CDATA[20100607]]></attribute>
	<attribute name="Comments"><![CDATA[Test VC Form]]></attribute>
</category>
<created><![CDATA[20101007130219]]></created>
<createdby><![CDATA[vcctest1]]></createdby>
<description clear="true"></description>
<file><![CDATA[C:\Livelink Migration\0000000157]]></file>
<location><![CDATA[Enterprise:Finance:Vendor Correspondence:22222222:Miscellaneous]]></location>
<mime><![CDATA[application/vnd.openxmlformats-officedocument.wordprocessingml.document]]></mime>
<modified><![CDATA[20101007130219]]></modified>
<title><![CDATA[22222222-New Vendor Test-Oct-07-2010 13-02-18]]></title>
</node>

If the action becomes "sync" and if I run this file again and again every time I run it I will get a new version added

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,Livelink ECM Champion 2010
 
actually I also do not know what sync is addversion adds a new version not sync.If I find out I will share

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,Livelink ECM Champion 2010
 
I've tried using the above script & sync tag and it seems that its only add the version number :(

what should I do then..I tried to ask the helpdesk in OpenText, but havent received any reply yet.

Once I got the answer, I'll share here.

Thanks!
 
well as far as I know the OI is not coded to handle moves in a livelink system.If there is alot of push from customers they may include it otherwise you may have to extend it if you know oscript.Does your company own webreports it can move livelink items as well.

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,Livelink ECM Champion 2010
 
I've explain to our people in global company network that working with Livelink as well, but I'm still waiting for their answer.
If they recommend me to use oscript as well, we will use it.

Btw, I saw in our list of installed module, we have Livelink API Core version 1.0.3. This is what u meant by LAPI?

And yes, we also have module Livelink WebReports Standard version 5.0.1, I am gonna take a look on that module.

Thanks!
 
LAPI is part of the SDK that you download and install it on client computers to connect to any livelink server.It is usual not installed on the livelink application server.the core module Livelink API Core should not be confused by the LAPI client distribution.

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,Livelink ECM Champion 2010
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top