tricky content search using Autonomy

We have two pieces of content that make up a number of our content pieces, one being a static file (PDF) and one being a custom content type that we created.

The custom content type has metadata that we use to restrict access to the static file and the content type and static file are related by using the same name.

For example, the static file 123.pdf has an accompanying content instance with the name 123 which contains the access restrictions for the 123.pdf static file.

This works well except for when we need to perform searches. It basically requires us to do a two-stage search:

search through the content of the static files
use the results of the first search and search through the content types to filter based on the metadata

This works in theory but results in suboptimal search response when the search term matches a large number of static files...

Anyway, if anyone has advice about a better approach or a way to improve our current configuration we would love to hear...

Thanks,
Jed

Find more posts tagged with

Comments

Eric Borisow

Hi Jed,

This doesn't get you away from the two-stage search, but have you tried using the API to get the object directly?

ManagedObjectVCMRef[] referringObjects = StaticFile.getReferringManagedObjects(new ManagedObjectVCMRef(<static file>.getContentManagementId().toString()));
for (ManagedObjectVCMRef referringObject : referringObjects)
{
ManagedObject mo = referringObject.retrieveManagedObject();
... do something with the mo
}

Regards,

Eric

Michael_Cohen

We are just about to implement something similar where we have security of a content item defined on the ctd attribute and made searchable so it registers with autonomy. We then query autonomy including security in the search. Theoretically could you do something like this? Cheers,

Mike

Sent from my iPhone

On Feb 15, 2013, at 1:09 PM, "eLink Entry: Discussion Group - Web Experience Management" <v7webcontentmanagement@elinkkc.opentext.com> wrote:

tricky content search using Autonomy Posted by jalexander@ici.org (Alexander, Jed) On 02-15-2013 13:58

We have two pieces of content that make up a number of our content pieces, one being a static file (PDF) and one being a custom content type that we created.The custom content type has metadata that we use to restrict access to the static file and the content type and static file are related by using the same name. For example, the static file 123.pdf has an accompanying content instance with the name 123 which contains the access restrictions for the 123.pdf static file.This works well except for when we need to perform searches. It basically requires us to do a two-stage search:search through the content of the static files use the results of the first search and search through the content types to filter based on the metadataThis works in theory but results in suboptimal search response when the search term matches a large number of static files...Anyway, if anyone! has advice about a better approach or a way to improve our current configuration we would love to hear...Thanks,
Jed
[To post a comment, use the normal reply function]
Forum: Discussion Group - Web Experience Management
Content Server: Knowledge Center

The information contained in this communication is confidential and intended only for the use of the recipient named above, and may be legally privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend it to the sender and delete the original message and copy of it from your computer system. Opinions, conclusions and other information in this message that do not relate to our official business should be understood as neither given nor endorsed by the company.

Qutubuddin

If you have full autonomy license then this is one possible solution approach

<![if !supportLists]>- <![endif]>Write a custom indexer which will add additional metadata to index for every static file indexed by the system, this metadata will typically be all the security information about the object being indexed. Autonomy allows custom schema definition for its indexes.

<![if !supportLists]>- <![endif]>Utilize the Autonomy API to build search pages which sends out search queries which will search and filter results in Autonomy directly (Autonomy allows complex queries, refer to IDOL documentation for more details ).

This is approach has been used by multiple customers to build the type of functionality you want. This approach is not Autonomy Specific either, it should be possible use this approach with other search engines like GSA

Note - This is not possible with Vignette provided OOTB License for Autonomy, if you are using Autonomy.

Thanks & Regards

Qutubuddin Saifuddin
Architect I America Services Organization

Phone: (732) 354 4423
Mobile: (732) 397 7951

Website: www.opentext.com

This email message is confidential, may be privileged, and is intended for the exclusive use of the addressee. Any other person is strictly prohibited from disclosing orreproducing it. If the addressee cannot be reached or is unknown to you, please inform the sender by return email and delete this email message and all copies immediately.

From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Friday, February 15, 2013 2:56 PM
To: eLink Recipient
Subject: Re tricky content search using Autonomy

Re tricky content search using Autonomy

Posted bymike.cohen@hyatt.com (Cohen, Michael) On 02-15-2013 14:55

Mike

Sent from my iPhone

On Feb 15, 2013, at 1:09 PM, "eLink Entry: Discussion Group - Web Experience Management" <v7webcontentmanagement@elinkkc.opentext.com> wrote:

tricky content search using Autonomy

Posted byjalexander@ici.org (Alexander, Jed) On 02-15-2013 13:58

We have two pieces of content that make up a number of our content pieces, one being a static file (PDF) and one being a custom content type that we created.
The custom content type has metadata that we use to restrict access to the static file and the content type and static file are related by using the same name.
For example, the static file 123.pdf has an accompanying content instance with the name 123 which contains the access restrictions for the 123.pdf static file.
This works well except for when we need to perform searches. It basically requires us to do a two-stage search:
search through the content of the static files
use the results of the first search and search through the content types to filter based on the metadata
This works in theory but results in suboptimal search response when the search term matches a large number of static files...
Anyway, if anyone! has advice about a better approach or a way to improve our current configuration we would love to hear...
Thanks,
Jed
[To post a comment, use the normal reply function]
Forum:
Discussion Group - Web Experience Management
Content Server:
Knowledge Center

[To post a comment, use the normal reply function]
Topic:	tricky content search using Autonomy
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center