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!

syntax for importing system attributes into livelink through xml

Status
Not open for further replies.

sunny1518

Programmer
Sep 3, 2012
27
US
Hi All,

I have created an xml control file to import documents into livelink. I have a system attribute with name="NAME" and value="Restricted" and this needs to be applied to document when it is imported as this make the document as protected and the document general tab has the metadata which looks like:
[highlight #FCE94F]Is the item classified as Restricted
yes
No[/highlight] (yes and no have a radio button)
I have tried the following tags but nothing worked
1.<systemattributes>
<systemattribute attrlen="50" attrname="NAME" attrtype="1" attrvalue="Restricted" DispName="iProtect Classification" DispType="Popup" IsEditable="false" IsSystem="true" Required="1" />
</systemattributes>
2.<system>:NAME=Restricted</system>
3.<NAME>Restricted</Name>

please suggest appropriate syntax. Thank you in advance!
 
If you are talking about "Additional Node Attributes" I do not think OI handles those.Are you saying when you add anything in your livelink you get a place where you tack in 'NAME' and possible values 'Restricted' if that is the case you and I are talking about the same thing.The additional metadata which we call categories and attributes are usually created in a place in livelink so when you say something like this in your OI
Code:
<category name="Livelink Categories:CANADA Records Management:UWI or LSD Number DLS"> 
<attribute name="LSD">05</attribute>
</category>

The OI parser looks at that string "Livelink Categories:CANADA Records Management:UWI or LSD Number DLS" to find the real category object and looks at its definition.
For additional node attributes there is a not a place it is an actual alter of the dtree table that happens which you cannot go back once you have done it.
For the greatest time I have heard that using System attributes is not a good practice,but if that is your case you may have to create a oscript code logic to handle that
for you.




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
 
Hi appnair,

Thanks for the reply.. Here NAME is the system attribute name and that field will be present in general tab and I want to pass the value Restricted to it.
Normally when I create a document through add document and if the parent folder has the Restricted value assigned to NAME, then even the document will get the value inherited. Infact in the document creation page and in the General tab I can see

iProtect Classification:Is the item classified as Restricted (Iprotect Classification is the display name of the system attribute)
yes(yes is marked)
No


When I create document through OI the Iprotect classification field look like
iProtect Classification:NO classification specified (Iprotect is the display name of the system attribute)
yes(nothing is marked)
No

But when I click on yes radio button and update then I can see

iProtect Classification:Is the item classified as Restricted (Iprotect is the display name of the system attribute)
yes(yes is marked)
No


I am sharing the export code of an existing document which has the Restricted value assigned to NAME

<systemattributes>
<systemattribute attrlen="50" attrname="NAME" attrtype="1" attrvalue="Restricted" DispName="iProtect Classification" DispType="Popup" IsEditable="false" IsSystem="true" Required="1" />
</systemattributes>
 
sorry about the font.. here is my reply

Thanks for the reply.. Here NAME is the system attribute name and that field will be present in general tab and I want to pass the value Restricted to it.
Normally when I create a document through add document and if the parent folder has the Restricted value assigned to NAME, then even the document will get the value inherited. Infact in the document creation page and in the General tab I can see

[highlight #FCE94F]iProtect Classification:Is the item classified as Restricted (Iprotect Classification is the display name of the system attribute)
yes(yes is marked)
No[/highlight]

When I create document through OI the Iprotect classification field look like
[highlight #FCE94F]iProtect Classification:NO classification specified
yes(nothing is marked)
No[/highlight]
But when I click on yes radio button and update then I can see

[highlight #FCE94F]iProtect Classification:Is the item classified as Restricted
yes(yes is marked)
No[/highlight]

I am sharing the xml export code of an existing document which has the Restricted value assigned to NAME

<systemattributes>
<systemattribute attrlen="50" attrname="NAME" attrtype="1" attrvalue="Restricted" DispName="iProtect Classification" DispType="Popup" IsEditable="false" IsSystem="true" Required="1" />
</systemattributes>
 
Sorry I could not understand anything that you have put.If I were you I would do this.
I would create a Folder under Enterprise and call it Test so it is like this Enterprise:Test
When you do that fill all that you want .Then I would create a single document underneath it again filling all
livelink asks you.

Then I would use OE(Object Exporter) and export this hierarchy Enterprise:Test.Then I will look at the output file
That is a OI file.If you see your system attribute and its syntax you have a way.

In other words a OE export of folders,documents etc in a livelink will create a OI file that is how you learn
what to put where.

What I think you are getting confused and getting me confused is trying to do a XMlexport and expecting that to work in
a OI file.They are different code/modules.If you use xmlexport create it back using xmlimport don't mix and match.

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 guess You have resolved the issue!

I was doing the XMLexport by using the objectid of the test document which I have created and expecting the same <Systemattributes> tag in xmlxport to work in my xml control file.

I will try ObjectExporter and try to get the System attributes syntax.

Thank you!
 
Hi appnair,

I have tried the Object exporter but getting the following error in logs:

[Error] The value for '<docstorage>' was not specified
[Error] The value for '<docstorage>' was not specified

But I have specified the Docstorage in my control file, below is the control file I have used:

<export>
<location>Enterprise:test4</location>
<docstorage>/export/home/documents</docstorage>
</export>

My livelink is in unix server. please correct me where I am making the mistake.

Thanks in advanace!
 
I have configured the destination, log and working folders.. and it is generating log as well in log folder
 
why is you path looking like that
<docstorage>/export/home/documents</docstorage>

are you a unix livelink my export file looks like this
<export>
<node>
<location>Enterprise:test4</location>
<docstorage>c:\temp\</docstorage>
</node>
</export>

Now the export will work only if you have RDPed to a server running livelink so C:\temp is the path on my livelink server


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
 
since you are unix I would do this by logging on to the livelink server and try to do
/export/home/documents and see as the logged in userr you can see that .

I also use <nod>/</node> although I think it is implied

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 the information appnair. I would try running the control file by adding the node tag.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top