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; } } }

Retrieving the tagged content through custom taxonomy in action UI.

Nageswar

Hi Techies,

We have issue with custom taxonomies.

Actually we have created Custom taxonomy like Language with two nodes. Deployed these taxonomies to development through PLC. So Taxonomy nodes are there in Site publisher database.

We have also tagged some DCRs and images with these custom taxonomy nodes.

We have created action by retrieve tagging content based on Custom taxonomy.

Created the condition & rule and applied this rule to some site publisher page.

While previewing the page , tagged content is not retrieving based on custom taxonomy. Here Language node.

We verified through LCSC debug panel by searching with same metadata , this debug panel displaying all dcrs & documents.

And we have overridden SampleContentRetrieverAction action java class and verified logs, that shows the zero results for our meta data search through this class.

code is
Client client = ContentService.getInstance().getContentClient(context.getContext());
LSCSIterator iter = client.getDocuments(queryString, 0, Integer.parseInt(maxContentCount));

here query string is our custom taxonomy like TeamSite%2FMetadata%2FLanguage%3A%3D%22hfay7djm%22.

But we are getting zero results.

Any help would be appreciated.

Thanks in advance,
Nageswar

Find more posts tagged with

Comments

Rick Poulin

code is
Client client = ContentService.getInstance().getContentClient(context.getContext());
LSCSIterator iter = client.getDocuments(queryString, 0, Integer.parseInt(maxContentCount));

here query string is our custom taxonomy like TeamSite%2FMetadata%2FLanguage%3A%3D%22hfay7djm%22.

But we are getting zero results.

Has this ever worked for you? Because your query does not follow the proper format, namely the equals and double quotes shouldn't be there, and you're missing the "q=". Try this (URL encoding not required for any of these characters, but good for future proofing):

String queryString = "q=" + URLEncoder.encode("TeamSite/Metadata/Language:hfay7djm", "UTF-8");

HIDECOLUMNS.rptdesign

Nageswar

Thanks rpoulin,

But Actually ,Here We are just overriding the ootb SampleContentRetrieverAction java class for printing logs for understanding.

I have posted the that query itself in the forum. We are passing This metadata query from content xml from the component like shown below in action parameter.

Param Name="TaggedMetadata">TeamSite/Metadata/Language

Here we are not at all touching the query, It is automatically generating by using " new Query(new AndConstraint((Constraint[])queryConstraintList.toArray(new Constraint[0])), null); " .

I have already tagged some dcrs & images by using above custom taxonomy node. I have verified that Database also having same "hfay7djm" taxonomy id.

LSCSIterator iter = client.getDocuments(queryString, 0, Integer.parseInt(maxContentCount)); is alwase displaying zero results.

Please clarify that any configuration required while doing action verbalization.

Regards,
Nageswar

Rick Poulin

Here we are not at all touching the query, It is automatically generating by using " new Query(new AndConstraint((Constraint[])queryConstraintList.toArray(new Constraint[0])), null); " .

The Query class automatically adds "q=" in front of the query string it generates, so how are you debugging that value? I suggest setting the SampleContentRetrieverAction class to debug logging, at which point you should see a debug line "Executing LSCS query [queryString]" in your logs. That's the very final query right before the actual execution, and that's the one you should double check.

Upon further investigation, it seems as though the escaped double-quotes surrounding the value do not affect the query (at least not on my server, although I still don't think they really belong there). So as a next step, try executing the call yourself directly against LSCS in a web browser and fiddle with the query until you figure out what's wrong with it. I'd expect you'll get no more results through your browser. I guess the follow up is, are you sure you actually have any deployed content that's tagged with that value?

Nageswar

Thanks rpoulin,

Yes, Query class automatically adds "q=" in front of the query string it generates. Now I am printing that value in degug statement in our customSampleContentRetrieverAction class which is extends SampleContentRetrieverAction.

like LOGGER.debug("Executing LSCS query " + query); , this statement prinitng the value TeamSite%2FMetadata%2FLanguage%3A%3D%22hfay7djm%22

Same above query string it is automatically passing to
String queryString = query.toString();
LSCSIterator iter = client.getDocuments(queryString, 0, Integer.parseInt(maxContentCount)).

I have already double checked against LSCS server is having some dcrs and images which are tagged with above custom taxonomy language node. so content is deployed.

I can retrieve the content by passing "dcr name" or "image name" in Metadata Search " q:" field & //livesite/default/main/CustomTaxonomy in "project" field.

Regards,
Nageswar

Ashish_Sangal

Hi Nageshwar,

Did you try setting the project name?

Or try logging project name in your custom code.