-
Notifications
You must be signed in to change notification settings - Fork 3
Identification Configuration
roomthily edited this page Jun 25, 2015
·
2 revisions
The identification task can be configured to use any subset of service identification filters. The filters are defined in a YAML file provided to the identifier at initialization.
YAML Structure
- name: {protocol name}
service:
- name: {name of the service}
request: {} // name of the service request for this identity
filters:
{ands | ors}:
- type: {simple | xpath | complex}
object: {content | url}
value: {text} // if simple, substring to find; if xpath, the xpath to execute
versions:
{checks | defaults}:
ors:
- type: {}
object:
value:
// if defaults, include the value to return if the check returns True
text:
language:
errors:
dataset:
- name: {name of the dataset type}
filters:
{ands | ors}:
- type: {simple | xpath | complex}
object: {content | url}
value: {text} // if simple, substring to find; if xpath, the xpath to execute
versions:
language:
errors:
metadata:
- name: {name of the metadata standard}
filters:
{ands | ors}:
- type: {simple | xpath | complex}
object: {content | url}
value: {text} // if simple, substring to find; if xpath, the xpath to execute
versions:
language:
errors:
resultset:
- name: {name of the result set type} // note these are specific to csw, oai-pmh, opensearch search responses
dialect:
- text: {}
// OR
checks:
ors:
- type: {}
object:
value:
filters:
{ands | ors}:
- type: {simple | xpath | complex}
object: {content | url}
value: {text} // if simple, substring to find; if xpath, the xpath to execute
versions:
language:
errors:
file: