You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This relates to the current code structure - it is a couple of methods returning the protocol (good match to the cat-interop.identifier) and a boolean for whether it's a service description service (see also #14). But the cat-interop has a kind of hierarchical structure in those identifiers that doesn't match that code structure well:
OpenSearch1.1:Description
which we would not get correctly (we would get OpenSearch1.1 and a True).
Current proposal: make it a class that returns a complete description of the document. It's of Type OpenSearch, Version 1.1, Is Description Document, Is Not Dataset, etc.
The text was updated successfully, but these errors were encountered:
# TODO: put together a configuration widget for
# to map protocol to some search filters
# and some service description filters,
# and some dataset filters so that we can
# have one thing to map the priority set
# vs the IDENTIFY ALL THE THINGS! set. oh,
# and wind up with reasonable line lengths
# for beto. :) so basically elasticsearch all
# the things.
#
# _ors: [content filters] + [url filters] (ANY match)
# _ands [content filter + url filter (or other combo)]
# where an _ands can be a filter in an _ors
and will also need to deal with versions (ie identify through xpath and an xpath, identify through url and some regex?, identify through some namespace and more regex?).
This might be a little overly complex. But configurable is good and code reuse is good.
This part would also be a good place for the error checks? for those services that return a valid response (not just 404/500/etc that nutch handles (@betolink, how does nutch handle the http error codes?)) like the OGC services where the response is a blob of xml with some error but the status code - it returned a response!
See #13 (expanding that list).
This relates to the current code structure - it is a couple of methods returning the protocol (good match to the cat-interop.identifier) and a boolean for whether it's a service description service (see also #14). But the cat-interop has a kind of hierarchical structure in those identifiers that doesn't match that code structure well:
OpenSearch1.1:Description
which we would not get correctly (we would get OpenSearch1.1 and a True).
Current proposal: make it a class that returns a complete description of the document. It's of Type OpenSearch, Version 1.1, Is Description Document, Is Not Dataset, etc.
The text was updated successfully, but these errors were encountered: