Search for Node based on Attribute value

Bruce_Percy

Hi All,

A question from a total newbie...

I've inherited some code which calls into Content Server (via DocumentManagement web service) to retrieve folders / documents and which then uploads to an Office 365 SharePoint site.

The code finds relevant items by traversing the 'folder tree' looking for a boolean attribute that is set to true.

It uses the DocumentManagement web service GetNodeByPath() method to load the Node and then uses the Metadata property to find metadata to do the traversal and to look for the attribute to check for upload.

Is there a way of doing this by just querying specifically for an Attribute with a specific value, rather than having to traverse a given hierarchy and looking at each Node to check if an Attribute is set?

 

Thanks in advance.

Appu_Nair1

Not necessarily sure why your original algoriths does what it does now but I will point out more possibilities since you say you are a newbie.

1. You can create a search query,limiting scope to a container and down,search queries are much like SQL(including I think it obeys SQL) but normally one uses LQL or Complex Queries where you can say ,give me that attribute under such and such areas I am interested and BTW I am only interested in Folders and Documents.Lots of examples in the documentaion(XML Search API) or if you create a good gui based search and it works to your adavantage,you can put wansearchlogs=true and run it,it will show you the LQL that the query is running.
2. The metadata or attribute data is usually in llattrdata table.It is very easy to expose what you want to know using a "view" or using database functions.Both approaches are documented in the KB in either "Champion Tool Kit" or "Knowledge Base".Once you know a sql query has what you are looking for it might be possible to code against it with simple LR 's(that obey permissions) or SQL queries(which most people,including me will say you should refrain from ,because you will be by passing livelink's permission safe guards)

I would definitely vote for the search XML API attempts.