LiveLink objAction xmlexport parameters (minimize xml export size)

[Hooperman]

hello,

is there a way to minimize what is being exported to xml using parameters in the URL? i don't need the extra llnode info (created, createdby, modified...etc).

basically the only node info i need created is name, id, parentid, objname.

i'm just trying to improve the efficiency of the xmlexport...so slow.

also, does anyone have a good guide for all LiveLink url parameters (objAction, scope, transform...etc).

thanks in advance.

 

[ggriffit]

I'm not an expert on Livelink and XML, but the inital thoughts of some of my colleagues who are more familiar is that it is possible, but you would have to use the Builder to amend the code. Alternatively, you could use some Javascript to create and process your own XML file. You'll find plenty of information on this on the internet.

As for a list of the Livelink URL parameters, there isn't one, OT don't have one as far as I am aware. This is mainly due to the wide number of OT and 3rd party modules that are about. I've been considering adding one to my stie at

http://www.greggriffiths.org/livelink/reference/func/

but haven't yet had the time to flesh it out. If you fancy having a go at it or at least providing me with a list from your server I'd appreciate it, I'm always on the lookout for this or any other contribution.

 

[LLGuru]

Hi. Restricting the XML output can indeed only be done using OScript.

Here are the parameters for the XML export:
- &scope=value
where value is:
base (export just the node)
sub (export the node and all its descendants)
n (export the node and its direct descendants up to n levels below the node: 1 for one level below, 2 for two levels below, or 3 for three levels below).- &attributeinfo (export category and attribute information)

- &nodeinfo (export DAPINode information)
versioninfo=value where value is: all (export all versions of the node) current (export the current version of the node only) n (export this particular version number)
followaliases (if an alias is encountered, export the alias and the node that the alias refers to)

- &content=value
where value is:
base64 (base64-encoded content)
cdata (legible text content in a CDATA Section)
plain (legible text content)
Note The cdata and plain settings are acted on only if the MIME type is included in the UnencodedMimetypes setting in the opentext.ini file.

- &requestcontext (dump the user, cgi, and http information for this request)

- &schema (include a <!DOCTYPE> in the file that references an external DTD

- &stylesheet (the name of the stylesheet that should be used to transform the exported XML)
The &stylesheet parameter can take a value that is either a node ID for a stylesheet that is currently stored in Livelink, the name of a file located in the file system, or a complete URL

Good luck