SRFERS Smart SearchFederated Query

Smart Search Overview

• Automating law enforcement searches using GJXDM-compliant transactions

• ARJIS and Nlets proposal building upon SRFERS

• Multi-database, federated query capability

Smart Search Overview

• Smart Search Policy Compiler Analyzes GJXDM-compliant transaction schemas to

define and record inquiry and response parameters Enables intelligent searching and automated response

construction• Smart Search Engine

User enters known input data and requested response data

All systems that can provide response data, or intermediate input data

Response data is aggregated and returned

Smart Search Policy Compiler

Smart Search Example

Sample Smart Search Metadata

SRFER ServicesMetaDataContact

Client Broker

What transactions can you Share with San Diego?

I Share the following transactions:Request DL

INPUTS: fist, last, dobRETURN: first, last, dob, license#, physical descriptionContact this web service at HTTP://www.test.com/dlreq

My data covers the city of Hilltop, TXMy information is license/ID information

It is confirmed informationI will return a list (of matches)

You may view my dataI will return a response quickly

I am a city repositoryI am searchable as a primary source

You may drill down to details using this service: DL Detail

DL DetailINPUTS: License Number

RETURN: first, last, dob, license#, expiration date, status, photo

Contact this web service at HTTP://www.test.com/dldetailMy data covers the city of hilltop, TX

My information is license/ID informationIt is confirmed informationI will return a single record

You may view, print, take action on my dataI will return a response within 10 minutes

I am a city repositoryI am searchable as a secondary source

You may not drill down

Thank you, I have added your services to my list of sources and will make queries based on the information you have

supplied.

You’re welcome.

SRFERS III MetaData Exchange Model

SRFERS Smart Search Example

Service Broker1

Client Broker

Service Broker2

ContactServiceBookingSearch IN Name, DOB OR SSN OR FBI OUT Name, DOB, Date, SSN, FBI DRILLDOWN BookingDetailBookingDetail IN SystemID OUT Name, DOB, Date, Address, SSN, FBI, PHOTO DRILLDOWN (none)

ContactServiceBookingSearch IN Name, DOB OR SSN OR FBI OUT Name, DOB, Date, SSN, FBI, Photo, Address DRILLDOWN (none)CitationSearch IN Name, DOB OR SSN OR FBI OUT Name, DOB, Date, SSN, FBI DRILLDOWN CitationDetailCitationDetail IN SystemID OUT Name, DOB, Date, Address, DL # DRILLDOWN (none)

· Use Case: · Officer knows Name and DOB, wants a photo: via directory services client

knows:· SB1 accepts name/dob and returns booking search which returns

booking detail with photo. · SB2 accepts name/dob and returns booking search with photo

· Client Broker sends request to both SB1 and SB2 for BookingSearch.· SB1 returns a list of potiential matches. Each match has one or more source

linking protocol (SLP) to drill down to detail· SB2 returns a list of potiential matches with photos for each match· Client has several options for display· Aggregate the lists, display only details provided by both systems, with links to

“details” – for SB1 results when details are requested, CB makes SB1 request (based on the SLP for the record) for SB2 cached additional details are displayed

· Aggregate both lists and show all fields returned from either system – if underlying system does not provide a field, indicate if that field can be requested in details, or if it is not available.

· Also indicate if more detail can be requested (based on SLPs for record)

SRFERS III Smart Search Re-Entrant QueryUse Case

Services Offered Via Metadata Exchange