nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

LscsQuery?

System

LiveSite 7.1

I have been trying to pick this stuff apart. If anyone know about some documentation I don't know about please clue me in. I cracked open the livestiecs-components spar to get a look at the source. In the LacsQuery class there is a method doGetDocumentList. One of the parameters it takes is String queryString. What on earth does that need to look like? In the Display Document List.component this is what is set:
[htmll]
q=
[/html]

What is all that supposed to be? Are there any examples of what these are supposed to be so a human can read them?

Find more posts tagged with

Comments

vpatel

Basically your component will pass some *query* to LSCS (i.e. in business terms: retrieve all documents tagged with a certain metadata). For example:a query like this -- q=TeamSite/Metadata/SomeKey Smiley Frustrated omeValue -- will return all assets that have a been tagged with "TeamSite/Metadata/SomeKey" EA with "SomeValue" as its value.

You could further refine the query such as q=metadata1:value1+AND+metadata2:value2. How this query is constructed is outlined in the LSCS guide.

Now take that component where you are seeing that "funky" expression. In that component, that query is being "dynamicized" (if that is a word) a little bit. User data could be used from the component input datums. Basically lets say you want to re-use this same component in two instances. For instance 1: you want all assets with metadata1:value1. For instance 2: you want all assets with metadata2:value2.

That component is using an "expression language" called OGNL (Object-Graph Navigation Language). It is a 3rd party library that is being used. If you look at that expression that you posted: it basically says that if "query" is not defined then use * (in search world its a catch-all) and if the content type is not defined then do the same. If they are defined then it'll use those valus to construct your query.

This is a sample component. If you feel comfortable using this OGNL expression language and having some flexible/dynamic queries then go for it. If you are more comfortable with simpler queries then go for that.

HTH!

Migrateduser

Thanks for the explanation, just so I know that I am understanding you correctly. The expected query string for the lscs.Client expects the same thing as the REST service does as explained in chapters 2 and 3 of the LSCS Technical Reference Guide? This helps alot!

Rojesh

Hi,
I am not finding a way to append &sort=metadata to querystring after looking at LscsQuery class. It appears it only supports, max results,include content, start and end index. Is there a way to perform sort ?

Thanks in advance.

Adam Stoller

Hi,
I am not finding a way to append &sort=metadata to querystring after looking at LscsQuery class. It appears it only supports, max results,include content, start and end index. Is there a way to perform sort ?

Thanks in advance.

Not sure of the actual answer - but 'sort' is not, strictly speaking, a query operation, it's an operation performed on the results of a query - so perhaps you need to perform a sort within the code that's wrapping the query?

Migrateduser

The request parameter is sort. Chapters 2 and 3 are good for this stuff in the LSCS Tech Ref.

From the LSCS Technical Reference Guide 7.1

sort A comma-separated list of fields by which to sort the results.
 To sort date and numeric fields in ascending order,
prefix the field name with the plus (+) character. Note
that the + character must be percent-encoded as %2B
when included in the URL.
 To sort these fields in descending order, prefix the
field name with the minus (-) character.
By default, the fields will be sorted in alphabetical order.

sort=random Return the result set in a random order.

Pages 33 and 34.
(Chapter 2 Application Programming Interface
REST API
Document Resources
Content Filter Request)

Binettoid

Hey Cyberpop, I got this working using a number of fields.
Lemme know if you need still help with this.
AFIAK it works (unusually) as it is documented. Queries end up with e.g.
&sort=-TeamSite/Metadata/CreationDate
In them. I use a Component Datum with a set of selectable presets for this.