cancel
Showing results for 
Search instead for 
Did you mean: 

Index Crawler: Scope Resource Filter: Access Path Patterns not working

Former Member
0 Kudos

Hi,

I am using EP6 SP17, KM SP17.

I intend to exclude certain files anywhere in the path of repository /xyz from being indexed at all. All files are ending with .HTML_banner.

So I copied the standard crawler parameter and created a scope resource filter which I included to the new crawler parameter, which is configured in the index in question. The settings of the scope resource filter are:

Case Sensitive: Checked

Access Path Mode: Exclude

Access Path Patterns: I tried the following, neither one works correctly:

*.HTML_banner

/xyz/**banner

[Complete path and file name]

The result is always that the files, which I like to exclude, are still indexed.

Unfortunately, as usual there is no comprehensive documentation about the syntax of the parameter "Access Path Patterns" or maybe I missed it.

Did anyone ever succeed using a scope resource filter in a similar scenario?

TIA,

Uwe

Accepted Solutions (1)

Accepted Solutions (1)

Karin
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Uwe,

sorry, I forgot to mention. The Item ID Pattern is in the result resource filter.

If you want to exclude certain mime-types (or extensions) from being indexed, you need a result resouce filter.

You can not use the scope resource filter for this requirement. This might also be the reason why your folder is still indexed. The value with '.' is not an allowed one in this input field

Hope this helps

Karin

Answers (1)

Answers (1)

Karin
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Uwe,

I once used this feature and it worked fine (with SPS 14).

I would suggest the following:

1. uncheck 'case sensitive' or do you have pathes that you want to index and that have the same name (except for the case) as those that you don't want to index

2. add '*.HTML-banner' to Item ID Patterns (to me it looks like a file-extension

3. Use your path /xyz/**banner with only one star or add maybe banner if this is suitable for you.

You can have a look at this for placeholders: http://help.sap.com/saphelp_nw04/helpdata/en/ac/940c285a2f9b4984e1cb3113a8a9d3/frameset.htm

Hope this helps

Karin

Former Member
0 Kudos

Hi Karin,

thanks for your response, however:

1. Unchecking "case sensitive" does not change anything.

2. Indeed, my file has the extension ".HTML_banner". Do you suggest to rename it to ".HTML-banner"? Where is the property "Item ID Patterns"?

3. "banner" doesn't solve the problem either.

Regards,

Uwe

KarstenH
Advisor
Advisor
0 Kudos

Hi Uwe,

unfortunately, I do not know off-hand, what the issue may be. It might be a combination of case sensitivity and escaped characters, though, which would support Karin's suggestion to try and exclude as well ".HTML_banner" as ".HTML-banner". I will inquire with development however.

In the meantime a return question:

What kind of more detail would you like to see in the documentation as it is found here?

http://help.sap.com/saphelp_nw04/helpdata/en/c0/6f5040b48a6913e10000000a1550b0/frameset.htm

Regards, Karsten

Former Member
0 Kudos

Hi Karsten,

thanks for your remarks. I tried with ".HTML-banner" but the effect is still the same, the document is still indexed.

My side note about the documentation has been driven by several experiences with KM documentation and in this special case I did not feel sure about the syntax, because I miss a detailed description or maybe examples for different use cases. Moreover, the regular expression syntax is not explained. I know Perl Reg. Expr. but are they the same and are all (extended) Reg. Expr. supported? Another example, which might be off topic here, is modifiers for displaying properties. The documentation tells nothing about modifiers like "standalone", "noWrapping" or "useLinkData", I found these only by accident.

KarstenH
Advisor
Advisor
0 Kudos

Hi Uwe,

thanks for the docu feedback.

I will pass this on to the responsible information developer.

Still no news on the original question, though.

Regards, Karsten