Systems Planning Homepage MWeb Homepage MWeb Administrator's Guide - How MWeb Works - Getting Started 1. Configuring the Project - Integrated Searching - Project Setup - Subsets - Search Categories - Stopwords - Linking to MWeb - Moving or Deleting a Project 2. Configuring Databases - Types of Databases - Adding Databases - Configuring Features - Configuring Tables - Configuring Subsets - Configuring Fields - Indexing a Database - Maintaining the Index - Testing the Database - If a Database Changes - Deleting a Database - Databases with Images, Part 1 - Databases with Images, Part 2 - Advanced Relational Topics - More about MARC Databases 3. Configuring the Interface - Introduction - Customizing the Splash Screen - Changing Layouts - Adding a Logo - Changing Messages - Changing CSS Stylesheets - Using XML and XSLT 4. Using MWeb Features - Sorting Search Results - Direct Access - Using HTML Tags in Data 5. Administering MWeb - Basic Tasks - Keeping Records - Administrator Control Center - User Administration - Reporting Problems - Performance Appendix 1: Installation Appendix 2: Reference - Interface Options - Security - Browsers and Standards - Error Messages - Character Encodings - Installation Details - Uninstalling & Reinstalling Appendix 3: Troubleshooting MWeb Glossary Contact Us

MWeb™ Universal Administrator's Guide


4. Using MWeb Features

Sorting Search Results

When you do a search, MWeb returns the results in a default sort order, as follows:

  1. First sorted alphabetically by Database Code, as shown in the list of Databases.
  2. Subsorted alphabetically by the tablenames in the Database (by Subset Number for MWeb Enterprise Databases, PastPerfect-Online Databases, and PastPerfect Export Databases).
  3. Subsorted alphabetically by the record IDs (the unique identifiers of records in each Database).

In Release 2.0 and later, you may modify #3, the order in which individual records are sorted. Sorting is not case-sensitive. You may specify one field or more; see Configuring Tables for how to do this.

Direct Access (future feature)

Direct Access is an MWeb feature that permits users to go directly to content without going through the MWeb Start Page. You can then provide links from other websites directly into Keyword Search Results or Full Records.

Terminology

A Direct Access "link" is like any other HTML link; that is, it looks like this:

     <a href="URL">Link text</a>

The "Link text" is what the user sees and clicks on. When the user clicks on the Link text, the browser navigates to the URL specified in the "href" attribute.

The following sections describe how to construct the URLs for the "href" attributes of your links. Remember, the entire URL is case-insensitive in MWeb.

Keyword Searches

For Keyword Searches, the URL consists of these segments; each segment is shown separately, for clarity, but they should be concatenated with no spaces in your link:

URL segment Notes
http://www.example.org Change www.example.org to your museum's domain name
/unicgi/mwebuni.exe This specifies the URL is for the MWeb program. Replace Uni with the project code.
?request=keyword This is the request type, telling MWeb this is a keyword search
;dtype=i Add this parameter if you wish to search only records with images (see example 2)
;keyword=yyy Replace yyy with the keyword(s) to be searched. Do NOT use quotation marks. Separate multiple keywords with spaces, as in examples 3 and 4.
;db=zzz Optional: Replace zzz with the Database ID* to limit the search to one or more Databases; repeat this parameter for multiple Databases (see example 5).
;ct=zzz Optional: Replace zzz with the Subset ID* to limit the search to one or more Subsets; repeat this parameter for multiple Subsets (see example 6). ("ct" stands for "Content Type" for historical reasons.)

* There is a link in the Project Parameters display to get the Database and Subset IDs, or if you do not have Administrator permission, use this URL: http://www.example.org/unicgi/mwebuni.exe?request=project

Examples:

1) http://www.example.org/unicgi/mwebuni.exe?request=keyword;keyword=basket
2) http://www.example.org/unicgi/mwebuni.exe?request=keyword;dtype=i;keyword=basket
3) http://www.example.org/unicgi/mwebuni.exe?request=keyword;keyword=annie oakley
4) http://www.example.org/unicgi/mwebuni.exe?request=keyword;keyword=rifles or guns
5) http://www.example.org/unicgi/mwebuni.exe?request=keyword;keyword=rifles;db=2;db=3
6) http://www.example.org/unicgi/mwebuni.exe?request=keyword;keyword=rifles;ct=5;ct=6

Full Records

For Full Records, the URL consists of these parts; each segment is shown separately, for clarity, but they should be concatenated with no spaces in your link:

URL segment Notes
http://www.example.org Change www.example.org to your museum's domain name
/unicgi/mwebuni.exe This specifies the URL is for the MWeb program. Replace Uni with the project code.
?request=record This is the request type, telling MWeb this is a full record request
;key=yyy Replace yyy with the tablename and unique ID of the record, separated by a period

Example:

     http://www.example.org/unicgi/mwebuni.exe?request=record;key=object.157

Using HTML Tags in Data

Data may contain HTML tags if you wish. You might want to use HTML tags to italicize or bold certain words, to separate text into paragraphs, etc.

Here are the tags you are most likely to need:

For character formating <b></b> (bold)
<i></i> (italics)
<big></big>
<small></small>
<font></font>
<sub></sub> (subscript)
<sup></sup> (superscript)
For paragraph formating <br> (to start a new line)
<br><br> (to start a new line with a blank line before it)
For tabular information <table>
<tr></tr>
<th></th>
<td></td>
</table>
Problem tags
(do not use)
<doctype>
<html></html>
<meta></meta>
<body></body>
<head></head>
<style></style>

We do not recommend using paragraphs or divs because styles applied to the first paragraph or div in the field will not be applied to later paragraphs or divs:
<p></p>
<div></div>

If in doubt, there is no harm in trying a tag and observing the results.


All contents of website, including HTML and JavaScript, copyright © 1996-2010 Systems Planning. MWeb, InFORMer, and CAPS are trademarks of Selago Design, Inc. MARCView and MARConvert are trademarks of OCLC, Inc.

Systems Planning
4915 Redford Road
Bethesda, MD 20816 USA
(301) 652-1231
info@systemsplanning.com

Including the name of one of our products in the subject of your message will bypass all spam filters.