Oscript is a server side language like ASP/JSP on which livelink is written so regardless of the script in that it is not lightweight like javascript, it takes a lot of learning.Easy to use examples are hard to come by other than some snippets in the KB.LAPI supports XMLExport/Import howver lapi has been deprecated in newer versions of livelink so there is very little help for you.
For a starting programmer enough info exists in public and the vendor to do simple export import for e.g why don't you think like this
[ol 1]
[li]Create a list of nodeid's in a text file using a Live Report/SQL[/li]
[li]Read Each one of those dataids[/li]
[li]Use a Webservices command to download each one.It basically takes 15 mins to set up a WSAPI server either IIS or Tomact whatver your preference another 15 minutes to find an example that you can understand[/li]
[li]If you can download one write a loop[/li]
[li]Do the reverse do an upload with an available example in your case you are interested in out[/li]
[/ol]
Standard OOB functionality called "Collections" exists in your livelink. Simply put if you create a collection and "Burn it to Disk" it will give you a index.htm file with hyperlinks to content you have in that disk not livelink .This is used to export chunks of livelink replete with metadata for
eDiscovery purposes.The html is xml so you can parse that for technical info I think.Only caveat is LL will put a technical structure to contents as file systems have serious heart burn when it exceeds length allowed by unix/windows so if a deep structure is downloaded LL will use a technical algorithm to represent it.The entire file path as in livelink is included in the html file.
Migration involving browsers are supported for small data sets.
Oscript can be learned by only creating a fully working livelink server installing builder or the CSIDE plugin in 10.5 and up and spending lots of time on it .
OT provides class room and distant education courses.In the public you will see code and samples primarily by [link livelink.in]me[/url] and [link greggriffiths.org]greggriffiths.org[/url]
there are many other hoobyists like us.
free to use support channels existed at one time but OT deprecated it.
If you do not want to make it your career I would use WSAPI or REST if supported.My gut feel is that OT is trying a closed approach to not allow customers to customize rather give them tools like SOAP,REST and WebReports to get by for their requirements so not many people in companies use Oscript other than a few.
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