Scheduled DB Maintenance: January 21st - 8:00 AM to 10:00 AM. Confluence will be unavailable during this time.

Navigation:
Documentation
Archive



Page Tree:

Child pages
  • Keyword Searching

This wiki space contains archival documentation of Project Bamboo, April 2008 - March 2013.

Skip to end of metadata
Go to start of metadata

Table of contents


[In creating or augmenting an Activity Definition, please be familiar with the Instructions. Italicized instructions on this page may (should) be edited out as the sections are completed.]

go back to Activity Definitions page


Keyword Searching

Keywords: enter key words from controlled-vocabulary list

Discover

Activity Definition(s)


A scholar may wish to search a collection (an aggregation of business objects) to discover business objects that are relevant to an inquiry. The business objects might be materials of any type (archives & manuscripts, audio, books, datasets, film & video, journals, learning objects, maps, newspapers, objects & artefacts, pictures, scores, theses, web rchives). But they could also be terms in a thesaurus or parties (people or groups), or activities (programs, projects, events). By definition, a keyword search is a search on alphanumeric strings so to discover non-textual objects (image, audio, video, people, datasets), the search will need to use metadata describing those objects. The searched collection may be a registry (an aggregation of metadata) or a repository (an aggregation of content) or it may search both metadata and content. A keyword search may also be initiated by a scholar as part of narrowing or broadening a search.

  1. Enter keywords
    1. [Select the collection(s) to be searched]
    2. [Select the desired formats for results]
    3. [Select the desired search attributes, eg title, subject]
    4. [Select the desired sort order for results]
    5. [Select the desired filters, eg language, date, business object type]
    6. [Specify the desired matching behaviours, eg fuzzy matching, stemming, truncation, proximity, match all, match any]
    7. [Specify the desired grouping behaviours for result sets]
  2. Submit search request
  3. Browse search results
  4. Obtain more information about a discovered object

The shared services (search and read) are evoked by Tasks 2 and 4.

In new generation library catalogs, a keyword search is submitted through a single simple search box and the client application parses user input and adds the required parameters specified in steps a-g based on user context, with relevance ranking as the default sort order for results.

Scholars' Stories (scenarios)


----Optional: examples of tools that perform some part or all of the defined activity, ideally with links to relevant project or vendor web sites

Tool name

What it does

Relevant links

Lucene

Java-based indexing and search technology.

http://lucene.apache.org/

SOLR

high performance search server built using Lucene, with XML/HTTP and JSON/Python/Ruby APIs, hit highlighting, faceted search, caching, replication, and a web admin interface

http://lucene.apache.org/solr/

IndexData Open Source Distributions

suite of products using technologies such as Ajax, Dublin Core, MARC, PHP, RSS, SOAP, SRU/SRW, XML, and Z39.50 (the legacy library search and retrieval protocol, now replaced by SRW/SRU).

http://www.indexdata.dk/

NLA SIngle Business Prototype

National Library of Australia federated search prototype built using Lucene and SOLR

http://ll02.nla.gov.au/

Vufind

Open source new generation library catalog software

http://www.vufind.org/

NLA Catalogue

National Library of Australia Catalogue based on Vufind

 


Related Collections/Content (examples)

----Optional: examples of collections / digital content / digital resources that could be involved in part or all of the defined activity, with links to relevant repository or site where available

Collection/content name

Collection/content description

Relevant links

 

 

 

 

 

 

 

 

 

 

 

 


Applicable Standards or Standards Bodies

----Optional: examples of standards or standards-bodies applicable to the defined activity

Standard name / body

What it governs/regulates/standardizes - What it's for

Relevant links

OAIS Search Web Service (SWS)

Abstract Search and Retrieval Protocol Definition with bindings for http, SRU and OpenSearch

http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=search-ws

SRW/SRU

Search Search and Retrieval protocol

http://www.loc.gov/standards/sru/

Contextual Query Language

Abstract query language

http://www.loc.gov/standards/sru/specs/cql.html

OpenSearch

Search Search and Retrieval protocol

http://www.opensearch.org/Home

e-Framework Search Service Genre

Defines generic behaviours for a shared search service.

http://www.e-framework.org/Services/ServiceGenres/ServiceGenreRegistry/Search/tabid/770/Default.aspx

e-Framework Read Service Genre

Defines generic behaviours for a shared read service

https://e-framework.usq.edu.au/users/wiki/GenreRead (may need to register with the e-Framework wiki to access)


Notes, comments, related activities, concerns

----Note that search and retrieval protocols are a combination of two shared services, Search and Read. The explain service in SRW/SRU is an expression of read with the target business object being a service description. A search and retrieval protocol includes mechanisms for specifying the parameters, filters and behaviours outlined in the activity definition above, but a raft of other services may need to be invoked to create the search request and search response (eg, http://usera.imagecave.com/drofe/search.png.jpg).
go back to Activity Definitions page