nodecrawler is an oscript object and will crawl projects without any problem.As far as I know it is not available to LAPI.if you are well versed in oscript take a look at how you will write your own api in communities.opentext.com there should be an article written by Louis Routhier how you would do that.Otherwise when you encounter a project convert the heagtive dataid into positive and iterate using lapi list objects.I have posted a piece of code in communities.opentext.com where I handle projects as well it is I belive called GetNodePath.
Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
I posted too soon and I wanted to see if thru lapi if you did an xmlexport whether it would crawl decsndants as well.if it does then you could probably use that some how.
Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
I use nodecrawler to process each folder and that works fine, but as an example, when it runs on a folder with a project which has documents, the nodecrawler only returns the parent folder and the project object, no documents or other objects within the project. If nodecrawler run on regular folder with documents it returns all nodes within that folder.
that is not the behaviour that I have seen using the nodecrawler object.Could you post how you are creating the object is it by the lliapi.nodecrawler nodecrawlerobject new's GetNode object ? or are you using a crawler call back object as well.
Actually I have had to write code inside the parentNode and VolumeNode to exclude projects being crawled .
Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.