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

CS10/10.5 Search Extractor changes

David Templeton

Afternoon all,

We are preparing to make changes to the extraction method of the OTLocation field within Content Server’s search Extractor. This is being done to improve the information that is being sent to the search index.

What does this mean to me? If your customization or solution orphans and extends the IndexLibraryNode.GetNodeMetaData() script then you will want to change it from being part of the Extractor’s IndexLibraryNode.GetNodeMetaData() script, and moving into the IndexLibrary AttributeRegion subsystem.

This is a similar change to what happened to the OTName and OTDComment fields in the 10.0 release. To determine if your code is affected by this change, search for files that contain both "MetaString" and "OTLocation".

We would like to understand how many solutions this change will impact. Please contact respond to this posting or respond to me if this change will affect you.