Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3
Note
titleSakai 2.4.0 is not the most current release

Sakai 2.4.1 has been released with primarily additional security fixes. The Sakai 2.4.x maintenance branch also has these security fixes as well as other minor bug fixes.

We recommend using the post-2.4 Citations Helper branch along with either Sakai 2.4.1 or Sakai 2.4.x. For post-2.4 Citations Helper configuration instructions, please see the post-2.4 Configuration Instructions page. (The post-2.4 Citations Helper will work with Sakai 2.4.0, but we do not recommend it.)

< back to Configuration Instructions

...

Tip
titleTable of Contents
Table of Contents
indent15px
stylenone

1 Example Scenario

The following is an example scenario that could use static configuration:

I have created a set of commonly used search categories and databases at my library that I would like all Citations Helper users to use. This set consists of General Interest, Science, Literature, Arts and Engineering categories and their related databases. My institution uses only Ex Libris MetaLib and there is a single username and password that the Citations Helper will use to access MetaLib.

2 Choosing an OSID implementation

For Sakai 2.4, the Citations Helper supports the SIRSI SingleSearch and Ex Libris MetaLib metasearch engines. Each of these metasearch engines has a corresponding Repository OSID implementation that the Citations Helper needs to use to properly communicate with the particular product's XML gateway.

...

  • osidImpl@org.sakaiproject.citation.api.ConfigurationService=
    • edu.indiana.lib.osid.base.repository.http - OSID implementation package to be used with SIRSI SingleSearch.
    • org.sakaibrary.osid.repository.xserver - OSID implementation package to be used with Ex Libris MetaLib.

...

3 Accessing the Metasearch XML Gateway

Many metasearching products provide an XML gateway to search and retrieve records from a metasearch engine remotely.

...

  • metasearchBaseUrl@org.sakaiproject.citation.api.ConfigurationService=<base URL of metasearch XML gateway>
    • For Sirsi SingleSearch, the XML gateway is called the Web2 Bridge. The URL to access Web2 is often the base address of your SingleSearch instance followed by /web2/servlet/MuseWeb2. For example:
      No Format
      nopaneltrue
      http://metasearch.university.edu/web2/servlet/MuseWeb2
    • For Ex Libris MetaLib, the XML gateway is called the X-Server. The URL to access the X-Server is usually the base address of your MetaLib instance followed by a /X. For example:
      No Format
      nopaneltrue
      http://metasearch.university.edu/X
  • metasearchUsername@org.sakaiproject.citation.api.ConfigurationService=<XML gateway username>
  • metasearchPassword@org.sakaiproject.citation.api.ConfigurationService=<XML gateway password>

...

4 Defining Search Categories & Databases

Search categories provide organizational structure to the databases that users have access to search through the Citations Helper. Search categories and databases are defined in an XML file called, categories.xml. This file should be located within your sakai.home directory, in a directory called org.sakaiproject.citation. Unless you have specifically changed sakai.home, it will be a folder named 'sakai' in your Tomcat root directory (i.e. /opt/apache-tomcat-5.5.23/sakai/org.sakaiproject.citation/categories.xml).

...