Inmagic^® Genie Version 2.00 Technical Notes

Note: If you print this file, for 8.5-inch by 11-inch paper, portrait orientation, use left and right margins of no more than 0.5 to ensure that the examples, illustrations, and tables print correctly.

Overview

Inmagic^® Genie is an integrated library system application that consists of a set of predefined textbases, forms, and business logic to support library functions such as cataloging, acquisitions, circulation of materials, serials tracking, interlibrary lending, and end user searching.

You can configure the Genie application to meet the specific needs of your organization. The application ships with a number of XML configuration files that contain parameters that you may modify. The names of these files suggest their area of influence: Genie.CONFIG contains general parameters, Reports.CONFIG contains content and formatting information for Summary and Full Display reports, and so forth.

While you could modify these files directly, you would be losing the ability to revert to the out-of-the-box defaults in the event that problems arise. For this reason, the Genie installer creates copies of these files, with a "My" prefix on each file name (for example, MyGenie.CONFIG). As of version 2.00, the application looks for configuration changes in the My*.CONFIG files first. Always use the My*.CONFIG files to customize the application for your purposes. For example, if you want to make a change to a report, make your change in the MyReports.CONFIG file. Do not make any changes to the configuration files without the "My" prefix. These non-My*.CONFIG files are for fall-back purposes. (For example, in case you need to revert to the original settings, you can copy a non-My configuration file and rename it with the "My" prefix.) If the application does not find the My*.CONFIG files, it will use the non-My*.CONFIG files. Using the My*.CONFIG files will allow your customizations to survive future upgrades.

MyGenie.CONFIG lets you change various general settings in the application.
MyGenieFieldMaps.CONFIG lets you change field attributes.
MyLabels.CONFIG lets you set up your own label formats.
MyNavbarMenuData.CONFIG lets you change the appearance of the Genie navigation bar.
MyQueries.CONFIG lets you change the search pages provided for the application.
MyReports.CONFIG lets you change the reports provided for the application. You can also add your own reports if you want.

As of version 2.00, the configuration files now reside in the ConfigFiles subfolder of your main Genie installation folder (for example: C:\Program Files\Genie\ConfigFiles).

Important! Due to the intricate coding and functions that make the Genie application work, the ability to change field attributes depends on your technical expertise with XML. There are rules to which you must strictly adhere. Some XML information is provided in the Content Server online help file (for example, see help topic "Creating Tag Names for XML Input"). Any typographical error (for example, forgetting to use a closing quotation mark) will cause your changes to not take effect and quite possibly break the application. You should always make any changes to your My*.CONFIG files. If necessary, you can refer to the non-MY*.CONFIG files to see what the original settings are.

Important! Whenever you make changes to these configuration files (except for the MyNavbarMenuData.CONFIG file), you must restart IIS (the World Wide Web Publishing Service) using the Services option through the Computer Management window. We recommend that you do this when no one is accessing the Genie application. If logged in users are using the application when IIS is restarted, they will get an "Access Denied" page. They will have to log in to Genie again. For your OPAC users, who typically do not have to log in, restarting IIS will discard the contents of their InfoCart.

Note that your organization may have customized the Genie application, including changing the names of fields and boxes. This technical notes document refers to entities on the Genie graphical user interface (GUI) by their default names.

MyGenie.CONFIG File

Use the MyGenie.CONFIG file to change various general settings for the application.

Adding your logo to your OPAC
Adding a Location drop-down list to the Catalog and OPAC search pages
Changing the date format for the application
Changing the number of days after the current date for the Needed Before box on the Add New ILL Request page
Configuring the volume and issue information for Serial records

Configuring the file upload settings for Catalog records
Configuring the InfoCart for your catalog and OPAC
Changing the items in the drop-down list for various fields

The following sections in the MyGenie.CONFIG file are for the application and you should not need to modify them except as noted below:

<!-- Library-specific settings, including e-mail ->. When the e-mail function is set up through the Set Up E-Mail Information page, the application writes to this section. Typically, you would not need to modify this section of the configuration file. The one exception would be if you wanted to disable the e-mail functionality. When you entered a mail server name on the Set Up E-mail Information page, you enabled various e-mail links in the application. If later you want to hide those e-mail links, you can only do so through the MyGenie.CONFIG file by commenting out or deleting the <add key="MailServer" value=..." /> element and then restarting IIS. Note that you may also want to hide the e-mail items in the drop-down list for the InfoCart, as they will not work once you disable the e-mail functionality.
<OpacPages>. This section is used by the application. Do not modify this section unless instructed to by Inmagic staff or a development partner.
<ExpandPageList>. This section is used by the application. Do not modify this section unless instructed to by Inmagic staff or a development partner.

Adding Your Logo to Your OPAC

You can add your logo to the pages that are available for your OPAC (online public access catalog).

Put the logo file you want to use in the IMAGES subfolder of your main Genie installation folder (for example: C:\Program Files\Genie\Images). The file must be in this subfolder.

Open the MyGenie.CONFIG file.
To activate this feature, remove the comment codes from the add element in the applicable section of the configuration file. The following shows the element in the configuration file with the comment codes removed:


    <!-- corporate logo for OPAC screens -->
    <add key="MyLogo" value="images/Inmagic_Genie_Logo-167.gif" />

Edit the file name provided out-of-the-box (Inmagic_Genie_Logo-167.gif) to match your logo's file name, as shown in the following example:


    <!-- corporate logo for OPAC screens -->
    <add key="MyLogo" value="images/My_Logo.gif" />

Save the configuration file and restart IIS.

Adding a "Location" Drop-down List to the Catalog and OPAC Search Pages

Use a query filter if you want to add a Location drop-down list to the bottom of the Catalog and OPAC search pages. In a multi-branch library, this feature lets the end user specify the branch or location in which to limit the search. The user's selection will be remembered in a browser cookie and used to preselect the same location for future queries.

To activate this feature, locate the following add element in the MyGenie.CONFIG file, change to value="true", as illustrated below, and then restart IIS.


   <add key="ApplyQueryFilter" value="true" ExpiresIn="180"/>

If you later want to remove this feature, change to value="false".

Note: If the logged-in user is a member of a group with a query constraint, the Location drop-down list will not appear. A query constraint is hidden search criteria added to every query into the CATALOG textbase. For more about this, see the Inmagic Genie Security Notes.

If you want to set the number of days before the browser cookie expires, change the value in the ExpiresIn attribute. For example, to set the cookie to:

Expire in 25 days: <add key="ApplyQueryFilter" value="true" ExpiresIn="25"/>
Expire immediately: <add key="ApplyQueryFilter" value="true" ExpiresIn="-1"/>
Never expire: <add key="ApplyQueryFilter" value="true" ExpiresIn="0"/>

Changing the Date Format for the Application

The Genie application uses the default date format of d MMM yyyy (day 3-letter month abbreviation 4-digit year; for example, 23 Nov 2004). This date format should work correctly for any region.

To change the date format for the application, you must change the value attribute in the applicable section of the MyGenie.CONFIG file and then restart IIS.

The following shows the default add element in the configuration file.


      <!-- Date format used for dates generated by Genie; only .Net-compatible 
		date formats can be used -->
      <add key="DateFormat" value="d MMM yyyy"/>

If you prefer a different date format, you can change it. Select one that works in both Windows and .Net. The following example shows a date format of M/d/yyyy, which generates numeric dates such as 11/12/2004 (for November 12, 2004).


      <add key="DateFormat" value="M/d/yyyy"/>

Note: International numeric dates with the day first (for example, d/m/yyyyy) may not work properly with United States versions of .Net and vice versa.

Changing the Number of Days After the Current Date for the "Needed Before" box on the Add New ILL Request Page

The Add New ILL Request page has a Needed Before box, as illustrated below. The application automatically fills in this field from the setting you designate in the MyGenie.CONFIG file. Out of the box, the number is set at 30 (days).

To change the number, do the following:

Open the MyGenie.CONFIG file.
Change the value attribute in the applicable section of the configuration file. As illustrated in the following example, the number has been changed to 60. This means, that if on August 5, 2005 you added a new ILL request, the application will insert October 4, 2005 in the Needed Before box of the Add New ILL Request page.


    <!--  Number of days after the current date for the Needed by date in 
		new ILL Requests-->
    <add key="DaysUntilILLNeedBefore" value="60"/>

Save the configuration file and restart IIS.

Configuring Volume and Issue Information

The Genie application has the ability to generate volume and issue information for the expected arrival dates for a Serial record. The volume and issue information is appended after a date, so that it does not interfere with searches for overdue issues. When an issue arrives and is checked in, the date, volume, and issue information can be re-arranged. You can even add the date that the issue was received.

The appearance of these items in the field entry is governed by a series of elements found in the MyGenie.CONFIG file. These parameters correspond with boxes on the Set Up Serial Arrival Pattern page: Starting Volume, Starting Issue, and Issues per Volume, as illustrated below. When you set up an arrival pattern, if you fill in these boxes on the Set Up Serial Arrival Pattern page, when you generate the issue dates, they will include volume and issue information. You will see this information (dates with volume and issue information) when you go to record the receipt of an issue or mark an issue as not received (by using the Check in and Skip missing issue links next to the Issues Expected box label).

To configure the volume and issue information for a Serial record, you must configure the following add elements in the applicable section of the MyGenie.CONFIG file and then restart IIS.


      <add key="VolumeIssueFormat" value=": v. {v}, no. {i}"/>
      <add key="MovedIssueFormat" value="{d} (expected), {t} (recd): {V}"/>
      <add key="MissingIssueFormat" value="{d} (expected): {V}"/>

VolumeIssueFormat dictates the format of the volume and issue information. This is the information that will be appended to the date the issue is expected to arrive. This element contains two placeholders:

{v} is a placeholder for the volume number.
{i} is a placeholder for the issue number.

The text before the placeholders is the text that will show in the output. <add key="VolumeIssueFormat" value=": v. {v}, no. {i}"/> will generate entries in the Issues Expected box like these:

10 Sep 2004: v. 12, no. 9
10 Oct 2004: v. 12, no. 10

You should be aware of the following:

If VolumeIssueFormat is not present in the MyGenie.CONFIG file, no volume/issue information is generated, and the Starting Volume, Starting Issue, and Issues per Volume boxes do not appear on the Set Up Serial Arrival Pattern page.
The <add key="VolumeIssueFormat".../> element must begin with a unique separator character (a character that does not appear elsewhere in the inner text for the element, and also does not appear in the date that will precede it). This requirement ensures that it is clear which part of the entry is the date and which part is the volume and issue. In the example shown above, the colon ( : ) is the designated separator character.

MovedIssueFormat dictates the format of this entry when the issue is checked in (after you click the Check in link on the Edit Serial Record page), and the entry is moved to the Issues Received box.

{d} is a placeholder for the date the issue was expected.
{t} is a placeholder for the current date (when the issue is checked in).
{V} [notice that this is a capital V] is a placeholder for volume and issue, exactly as it appears after the separator character in VolumeIssueFormat but with leading and trailing spaces removed.

If any of these placeholders is missing, the corresponding information will be omitted when the entry is moved.

<add key="MovedIssueFormat" value="{d} (expected), {t} (recd): {V}"/> would place these entries in the Issues Received box:

10 Oct 2004 (expected), 10 Oct 2004 (recd): v. 12, no. 10
10 Sep 2004 (expected), 9 Sep 2004 (recd): v. 12, no. 9

MissingIssueFormat dictates the format of the entry when it is moved to the Issues Missing box (after you click the Skip missing issue link). MissingIssueFormat uses the same three placeholders as MovedIssueFormat. Note that Serial claim reports include information from the Issues Missing box. You may need to modify these reports somewhat, depending on the format you select for this parameter.

<add key="MissingIssueFormat" value="{d} (expected): {V}"/> would place these entries in the Issues Missing box:

10 Oct 2004 (expected): v. 12, no. 10
10 Sep 2004 (expected): v. 12, no. 9

To change the format of the output for the volume and issue information

You can change the format of the output for the volume and issue information. For example, you can spell out "volume", "issue", and "received", as illustrated in the following example:


      <add key="VolumeIssueFormat" value=": volume {v}, issue {i}"/>
      <add key="MovedIssueFormat" value="{d} (expected), {t} (received): {V}"/>
      <add key="MissingIssueFormat" value="{d} (expected): {V}"/>

The add elements shown above will generate entries in the Issues Expected box like these:

10 Sep 2004: volume 12, issue 9
10 Oct 2004: volume 12, issue 10

In the Issues Received box like these:

10 Oct 2004 (expected), 10 Oct 2004 (received): volume 12, issue 10
10 Sep 2004 (expected), 9 Sep 2004 (received): volume 12, issue 9

In the Issues Missing box like these:

10 Oct 2004 (expected): volume 12, issue 10
10 Sep 2004 (expected): volume 12, issue 9

Things to keep in mind

In versions of Genie prior to 1.2, the Issue Due, Issue Received, and Missing Issues fields were all strict Date fields. A strict Date field must begin with a date. If you modify MovedIssueFormat and/or MissingIssueFormat so that they do not begin with a date, ensure that the affected field definitions are Text fields or non-strict Date fields. (If you do not have textbases provided with an earlier version of Genie, you do not have to make these changes.)
Case is significant in all of the elements. The {v} placeholder is not the same as {V}, and you cannot use a placeholder in an element that does not expect it. For example, {v} and {i} can only be used in VolumeIssueFormat.
<add key="MovedIssueFormat".../> and <add key="MissingIssueFormat".../> are only used when you click the links over the Issues Expected box. These elements are not used if you move entries between boxes on the edit page by selecting, cutting, and pasting them. Note that if you are checking in an issue that had already been moved to the Issues Missing box, then you do have to use the Select, Cut, and Paste commands to manually make any changes in the format of the information yourself.

Configuring the File Upload Settings for Catalog Records

You configure the file upload functionality though the MyGenie.CONFIG file. For a Catalog record, you can include a document file (for example, the table of contents for a book) or an image file. For a document file, you can link to the original document and/or use the CS/Importer (if you have it installed) to import the full text of the document. For an image file, you can link to the original image file. By default, this functionality is available out-of-the-box for document files. For document files, the functionality uses the Document File Name box, its associated Browse button, and the Extract Text check box on the Biblio 2 tab on the Add/Edit Catalog Record page. For image files, the functionality uses the Image File Name box and its associated Browse button. Library staff users would use the Browse button to browse to and insert the file that they want to associate with the record. If your site uses the CS/Importer, your library users could select the Extract Text check box to have it import the full text of the document. (To learn more about the CS/Importer, see the documentation provided with that product.)

The following illustrations shows the file upload functionality activated for both document and image files.

Note: If imported, the full text is not contained in a field that can be displayed on the Web, as its content could be quite large. Extracting full text is only done to support searching by word, phrase, or proximity expression.

When you configure this functionality, you specify a folder to use in document links (TreatAs="FileLink") and a folder in which the CS/Importer looks for files to import. Note that if you do use the CS/Importer to import the full text of the file, you must also set up the CS/Importer to use the same source file folder (meaning the value for the add key="ImportFolder").

You can also specify the Document Folder for use with the TreatAs="FileLink" feature. Enter the path to the same folder in the Move processed source files to this directory box on the Import Profile Wizard dialog box for the CS/Importer.

Note that there are other CS/Importer settings that you make. Use these settings for the CS/Importer, on the Import Document Options dialog box:

On the Document Fields tab:

In the Field for Text drop-down list, select CatFullText.
In the Field for File Name drop-down list, select CatFileName.

On the Add/Replace Options tab:

In the If Match is Found group, select the Replace Fields option button.
In the If Match is Not Found group, select the Reject New Record option button.

Import Directory and Move To, as described already.

The following shows the document upload section of the MyGenie.CONFIG file.


    <!-- Document & image settings -->
    <add key="ImportFolder" value="ImportFolder"/>
    <add key="DocumentFolder" value="DocumentFolder"/>
    <add key="ImageFolder" value="ImageFolder"/>
    <add key="DocumentUpload" value="true"/>
    <add key="ImageUpload" value="false"/>

To configure the document upload settings for Catalog records, do the following:

Open the MyGenie.CONFIG file.
Change the value attribute in the applicable section of the configuration file.

The value for the key="ImportFolder" attribute tells the application where to put files for the CS/Importer. The specified location must be a subfolder under the Genie installation folder (for example, C:\Program Files\Inmagic\Genie\ImportFolder). The installation process for the Genie application will have created the subfolder named in the default value for this parameter. You do not have to change this parameter unless you rename that folder. If you comment out this string, delete it, or enter no value (meaning value=""), it means you do not have or do not want to use the CS/Importer, and the Extract Text check box will not appear on the Biblio 2 tab. Selecting the Extract Text check box is what determines to which folder (Import or Document) the file will be uploaded.
The value for the key="DocumentFolder" attribute tells the application which folder to use when constructing the URL for the "TreatAs="FileLink" feature. The specified location must be a subfolder under the Genie installation folder (for example, C:\Program Files\Inmagic\Genie\DocumentFolder). The installation process for Genie will have created the subfolder named in the default value for this parameter. You do not have to change this parameter unless you rename that folder.
The value for the key="ImageFolder" attribute tells the application where to store image files. The specified location must be a subfolder under the Genie installation folder (for example, C:\Program Files\Inmagic\Genie\ImageFolder). The installation process for Genie will have created the subfolder named in the default value for this parameter. You do not have to change this parameter unless you rename that folder.
The value for the key="DocumentUpload" attribute activates this functionality for document files. A value of "true" activates the Document File Name box and its associated Browse button, and if there is a value entered for the "add key=ImportFolder" attribute, the Extract Text check box. A value of "false" de-activates the functionality. Out of the box, this value is set to "true".
The value for the key="ImageUpload" attribute activates this functionality for image files. A value of "true" activates the Image File Name box and its associated Browse button. A value of "false" de-activates the functionality. Out of the box, this value is set to "false".

Save the configuration file and restart IIS.

Note: The following string in the Web.CONFIG file controls the maximum size permitted for files to be uploaded.


<httpRuntime maxRequestLength="102400" executionTimeout="3600""/>

The default value, 102400, permits file sizes up to 100 megabytes. If a user attempts to upload a file larger than the specified value, Internet Explorer will display a "Page cannot be displayed" message.

Configuring the InfoCart

With the InfoCart, library staff and end users of your OPAC can select multiple Catalog records and do any of the following:

Request Catalog items via e-mail to the library
Send Catalog record information via e-mail to anyone in text format or as a hypertext link
Download the Catalog information in CSV or XML format
Print Catalog record information
For library staff only: Print labels

To configure the InfoCart, you must configure the applicable <Action Name> section in the <LibraryCart> or <OpacCart> section of the MyGenie.CONFIG file and then restart IIS. The <LibraryCart> section controls the InfoCart for your library staff. The <OpacCart> section controls the InfoCart for the end users of your library. You want to be aware of to which section you are making your changes.

Important! We recommend that you do this (make changes to the configuration file and restart IIS) when no one is using the Genie application. Once you restart IIS (or someone else restarts IIS for some other reason), items in the InfoCart will be discarded. Therefore, you want to be sure that no one is using the application when you restart IIS. Users will see your changes the next time they use the Genie application.

You can configure the InfoCart to:

Configure which Catalog fields appear in InfoCart output
Remove an item from the action drop-down list
Change the label of an item in the action drop-down list
Re-order the items in the action drop-down list
For the InfoCart for the OPAC, you can specify attributes

To configure which Catalog fields appear in InfoCart output

Many <Action Name> sections contain a <FieldList> element that identifies the fields to show for each InfoCart output. Out of the box, the application provides you with some fields (where applicable). You can change the items in the <FieldList>.

The following shows the <Action Name="Request" Display="Request"> element section for the InfoCart for the <LibraryCart> section. When a request is made for a Catalog record, the request will show the CatTitle, CatSubtitle, CatAuthor, and CatCallNumber fields as defined in the <FieldList> section.

To add another field, copy a <Field> element from the ones already provided and change it to another field name. For a list of the fields in the CATALOG textbase, see the MyGenieFieldMaps.CONFIG file.

To remove a field, comment out or delete the entire <Field> element.


  <!-- Actions exposed to library staff in the Catalog InfoCart -->
  <LibraryCart>
    <Action Name="Request" Display="Request">
      <FieldList>
        <Field>CatTitle</Field>
        <Field>CatSubtitle</Field>
        <Field>CatAuthor</Field>
        <Field>CatCallNumber</Field>
      </FieldList>
    </Action>
    ...
  </LibraryCart>

To remove an item from the action drop-down list

To remove an item from the drop-down list for the InfoCart, you can remove the entire applicable Action Name section. For example, out of the box, there is an Action Name="EmailText"... section, as shown in the left column below. In the right column, the whole section has been deleted and E-mail (Text) will not appear in the drop-down list for the InfoCart used by library staff.

Out-of-the-Box	Changed, with section deleted
<!-- Actions exposed to library staff in the Catalog InfoCart --> <LibraryCart> <Action Name="Request" Display="Request"> <FieldList> <Field>CatTitle</Field> <Field>CatSubtitle</Field> <Field>CatAuthor</Field> <Field>CatCallNumber</Field> </FieldList> </Action> <Action Name="EmailText" Display="E-mail (Text)"> <FieldList> <Field>CatTitle</Field> <Field>CatSubtitle</Field> <Field>CatAuthor</Field> <Field>CatCallNumber</Field> </FieldList> </Action> <Action Name="EmailLink" Display="E-mail (Link)"> <LinkText>Click here</LinkText> </Action> ... </LibraryCart>	<!-- Actions exposed to library staff in the Catalog InfoCart --> <LibraryCart> <Action Name="Request" Display="Request"> <FieldList> <Field>CatTitle</Field> <Field>CatSubtitle</Field> <Field>CatAuthor</Field> <Field>CatCallNumber</Field> </FieldList> </Action> <Action Name="EmailLink" Display="E-mail (Link)"> <LinkText>Click here</LinkText> </Action> </LibraryCart>

Out-of-the-Box

Changed, with section deleted


<!-- Actions exposed to library staff in the 
   Catalog InfoCart -->
<LibraryCart>
  <Action Name="Request" Display="Request">
    <FieldList>
      <Field>CatTitle</Field>
      <Field>CatSubtitle</Field>
      <Field>CatAuthor</Field>
      <Field>CatCallNumber</Field>
    </FieldList>
  </Action>
  <Action Name="EmailText" Display="E-mail (Text)">
    <FieldList>
      <Field>CatTitle</Field>
      <Field>CatSubtitle</Field>
      <Field>CatAuthor</Field>
      <Field>CatCallNumber</Field>
    </FieldList>
  </Action>
  <Action Name="EmailLink" Display="E-mail (Link)">
    <LinkText>Click here</LinkText>
  </Action>
  ...
</LibraryCart>


<!-- Actions exposed to library staff in the 
  Catalog InfoCart -->
<LibraryCart>
  <Action Name="Request" Display="Request">
    <FieldList>
      <Field>CatTitle</Field>
      <Field>CatSubtitle</Field>
      <Field>CatAuthor</Field>
      <Field>CatCallNumber</Field>
    </FieldList>
  </Action>
  <Action Name="EmailLink" Display="E-mail (Link)">
    <LinkText>Click here</LinkText>
  </Action>
</LibraryCart>

To change the label (the text that appears) of an item in the action drop-down list

To change the label of an item in the drop-down list for the InfoCart, edit the Display attribute for the item. In the following example, the Request item has been changed to Ask the Library for the <OpacCart> section:


  <!-- Actions exposed to end users in the OPAC InfoCart -->
  <OpacCart ShowCartMessage="true" CartMessage="item(s) in cart" 
	ShowCartImage="true" CartImageURL="images/infocart.gif">
    <Action Name="Request" Display="Ask the Library">
      <FieldList>
        <Field>CatTitle</Field>
        <Field>CatSubtitle</Field>
        <Field>CatAuthor</Field>
        <Field>CatCallNumber</Field>
      </FieldList>
    </Action>
    ...
  </OpacCart>

To re-order the items in the action drop-down list

To re-order the items that appear in the drop-down list for the InfoCart, move one or more items to another position in the list.

Out of the box, the Request item is first. In the following example for the <OpacCart> section, it has been moved to the third position, after the two e-mail items:


  <!-- Actions exposed to end users in the OPAC InfoCart -->
  <OpacCart ShowCartMessage="true" CartMessage="item(s) in cart" 
	ShowCartImage="true" CartImageURL="images/infocart.gif">
    <Action Name="EmailText" Display="E-mail (Text)">
      <FieldList>
        <Field>CatTitle</Field>
        <Field>CatSubtitle</Field>
        <Field>CatAuthor</Field>
        <Field>CatCallNumber</Field>
      </FieldList>
    </Action>
    <Action Name="EmailLink" Display="E-mail (Link)">
      <LinkText>Click here</LinkText>
    </Action>
    <Action Name="Request" Display="Request">
      <FieldList>
        <Field>CatTitle</Field>
        <Field>CatSubtitle</Field>
        <Field>CatAuthor</Field>
        <Field>CatCallNumber</Field>
      </FieldList>
    </Action>
    ...
  </OpacCart>

To specify attributes for the InfoCart for the OPAC

For the InfoCart for the OPAC, you can specify attributes. The following table lists the supporting attributes for the OpacCart element.

Attribute	Required	Default	Purpose
CartImageURL	No	infocart.GIF	This is the source URL for the OPAC InfoCart icon.
ShowCartMessage	No	false	Displays text link for the OPAC InfoCart.
CartMessage	No	items in cart	This is the text displayed for the text link for the OPAC InfoCart.
ShowCartImage	No	false	Displays the cart image for the OPAC InfoCart.

Changing the Items for the Drop-down List for Various Fields

For some drop-down lists in the application, you can change the items that appear in the list. To add, edit, or delete the items in the drop-down list for the term of a loan, frequency for a serial; and for orders, the order type, payment method, currency, and order status, do the following:

To change the items in the drop-down list for the "Term of Loan" box on the Check Items Out page and the Edit Loan Record page

Open the MyGenie.CONFIG file.
Depending on what you want to do:

To add a new item: Copy a <Term NumOfDays...> element from the ones already provided and change it to a new loan term. You should change the value for the number of days and enter a value for how you want the item to appear in the drop-down list. The following example shows a loan term of one year, which is not provided out-of-the-box for the application. Note that wherever you place an item in the list is where it will appear on the drop-down list.


  <!-- LoanTerms -->
  <LoanTerms>
    <Term NumOfDays="0" DisplayTerm=" " />
    ...
    <Term NumOfDays="365" DisplayTerm="1 year" />
    <Term NumOfDays="-1" DisplayTerm="permanent" />
  </LoanTerms>

To delete an item: Comment out or delete the entire <Term NumOfDays... /> element.

Note: Do not delete the first item on the list (<Term NumOfDays="0" DisplayTerm=" " />). The blank display informs the end user that no term has been selected yet, and the 0 value ensures that the application will remind the end user to select a term before saving.

Save the configuration file and restart IIS.

To change the items in the drop-down list for the "Frequency" box on the Set Up Serial Arrival Pattern page

Depending on what you want to do:

To add a new item: Copy a <Frequency Pattern...> element from the ones already provided and change it to a new serial frequency. You should change the value for the frequency pattern and enter a value for how you want the item to appear in the drop-down list. The following example shows a frequency choice of Biennially, which is not provided out-of-the-box for the application. Note that wherever you place an item in the list is where it will appear on the drop-down list.


  <!-- SerialFrequency-->
  <SerialFrequency>
    <Frequency Pattern="Y1" Display="Annual" />
    ...
    <Frequency Pattern="Y2" Display="Biennially" />
    <Frequency Pattern="XX" Display="Irregular" />
  </SerialFrequency>

To change the text that displays in the drop-down list: Change the value for the Display attribute for that element.
To delete an item: Comment out or delete the entire <Frequency Pattern... /> element.

Save the configuration file and restart IIS.

How to interpret the pattern codes

For the Frequency Pattern attribute, you can use codes that begin with Y (for years), M (for months), and D (days). For example, Y1 means once every year, Y2 means every two years, Y4 means once every four years, and so forth. The software uses the pattern to create a series of expected arrival dates.

To change the items in the drop-down list for the "Order Type" box on the New/Edit Order page

Depending on what you want to do:

To add a new order type: Copy an <OrderType...> element from the ones already provided and change it to another order type choice. The following example shows an order type of Vendor Promotion, which is not provided out-of-the-box for the application. Note that wherever you place an item in the list is where it will appear on the drop-down list.


  <!-- OrderTypes -->
  <OrderTypes>
    <Type>Blanket Order</Type>
    <Type>Vendor Promotion</Type>
    ...
    <Type>Standing Order</Type>
  </OrderTypes>

To delete an item: Comment out or delete the entire <OrderType... /> element.

Save the configuration file and restart IIS.

To change the items in the drop-down list for the "Payment Method" box on the New/Edit Order page

Depending on what you want to do:

To add a new payment method: Copy a <Method...> element from the ones already provided and change it to another payment method choice. The following example shows a payment method of "Barter Exchange", which is not provided out-of-the-box for the application. Note that wherever you place it in the list is where it will appear on the drop-down list.


  <!-- PaymentMethods -->
  <PaymentMethods>
    <Method>Credit Card</Method>
    ...
    <Method>Barter Exchange</Method>
    <Method>Wire Transfer</Method>
  </PaymentMethods>

To delete an item: Comment out or delete the entire <PaymentMethod... /> element.

Save the configuration file and restart IIS.

To change the items in the drop-down list for the "Currency" box on the New/Edit Order page

Depending on what you want to do:

Copy a <Currency...> element from the ones already provided and change it to another currency choice. The following example shows a currency of "South African Rand - ZAR", which is not provided out-of-the-box for the application. Note that wherever you place it in the list is where it will appear on the drop-down list.


  <!-- Currencies -->
  <Currencies>
    <Currency></Currency>
    <Currency>U.S. Dollars - USD</Currency>
    <Currency>U.K. Pounds - GBP</Currency>
    <Currency>Canada Dollars - CAD</Currency>
    <Currency>Euro - EUR</Currency>
    <Currency>South African Rand - ZAR</Currency>
  </Currencies>

To delete an item: Comment out or delete the entire <Currency... /> element.

Save the configuration file and restart IIS.

To change the items in the drop-down list for the "Status" box on the New/Edit Order page

The application uses the <Status Usage...> attribute of the order status to determine which status to automatically select when creating a new item and receiving an item. If no <Status Usage...> element is specified for "new" or "receiving," the application uses the first <Status Display> entry in the list.

We recommend that you do not delete the Status Usage attributes provided out of the box.

Depending on what you want to do:

To add a new order status: Copy a <Status Display...> element from the ones already provided and change it to another order status choice. The following example shows an order status of "unknown", which is not provided out-of-the-box for the application. Note that wherever you place an item in the list is where it will appear on the drop-down list.


  <!-- OrderStatus-->
  ...
  <OrderStatus>
    <Status Usage="new" Display="new" />
    <Status Usage="receiving" Display="received" />
    <Status Display="closed" />
    <Status Display="backordered" />
    <Status Display="unknown" />
  </OrderStatus>

To delete an item: Comment out or delete the entire <Status Display... /> element.

Save the configuration file and restart IIS.

MyGenieFieldMaps.CONFIG File

You can make many field-specific changes to the Genie user interface with this file. If you change a box label, for example, you are also changing how that field is referenced in error messages, on-page hints, browse windows, and so forth. Given this functionality, there is seldom a good reason to change the actual name of that field in the textbase.

If you do want to change the name of the field in the textbase, you will have to use the Inmagic^® CS/TextWorks to do so, and then ensure that the corresponding parameter in the MyGenieFieldMaps.CONFIG file is changed to match.

In addition, if you want to add fields to the textbase, do so in CS/TextWorks, then map the new fields to User-defined fields in the MyGenieFieldMaps.CONFIG file.

Important! Whenever you make changes to this configuration file, you must restart IIS.

You can change any of the following attributes of a field exposed in the Genie application (except when noted where appropriate in this document):

Field name (as defined in the textbase). Do not change this attribute value.
Box label (as it appears on Web edit pages, and often the search pages)
Required-field indicator (whether the box label is preceded by a red asterisk on a Web edit page)
Browse link (whether a link to the field's validation list follows the box label on a Web edit page)

General Instructions on How to Make Changes

In many cases, you change field attributes in the MyGenieFieldMaps.CONFIG file and, when necessary, make matching changes to a textbase through CS/TextWorks. Note that the attributes must be associated with the original field name.

To make changes to a Genie textbase through CS/TextWorks

Start CS/TextWorks. For example, from the Windows Start menu, choose Program>Inmagic Applications>Content Server>CSTextWorks.

Open the Genie textbase for which you want to change a field attribute.

Choose Maintain>Edit Textbase Structure to open the Edit Fields dialog box and make your field attribute changes. You can:

Change a field name
Change whether a field is required
Add, remove, or edit a validation list for a field
Add a field

Save your changes.
To reflect these changes in the Genie application, see the next set of steps. For example, if you made a field required that is also used on a page in the Genie application, you want to put a required-field indicator before the box label on the page for that field, so that users can see that requirement.

To make field attribute changes reflect in the Genie application

Open the MyGenieFieldMaps.CONFIG file.

Within the FieldMap element, locate the textbase section in which you want to make field attribute changes (for example, <inmg:FieldMap TextbaseName="Borrower" ... >) and make your changes.

In the Field element (for example, <Field AppName="BorrName" UserName="BorrName" BoxLabel="Name" VList="false" /> within the FieldMap element make your changes.

After you make your changes to the MyGenieFieldMaps.CONFIG file, stop and restart IIS.
If you have not already made corresponding changes to the applicable textbase, do so now; see the above set of steps. For example, if you added a required-field indicator to a field in the Genie application, you should apply Field Entry Required validation for the field in the textbase through CS/TextWorks.

The MyGenieFieldMaps.CONFIG file is in XML format. As installed, it contains placeholders for all of the fields that can be configured in the Genie textbases that are directly involved in the application, with default values supplied.

Within the guidelines as stated in this document, you can change the values in the MyGenieFieldMaps.CONFIG file to make the Genie application more meaningful for your end users. For each field you want to change, supply the appropriate attribute values.

The following table lists the supported attributes for the FieldMap element for the MyGenieFieldMaps.CONFIG file.

Attribute	Required	Default	Purpose
Heading	No	Textbase name	The value here is what typically appears after "Inmagic Genie:" on a page (for example, "Inmagic Genie: Interlibrary Lenders" where Interlibrary Lenders is the heading text).
HistoryLink	No	Textbase name	The value here is text (typically the meaningful name of a textbase) that is part of the label that describes a type of page (for example, the history link for a search page for the ILLENDER textbase could be "IL Lenders Search", where IL Lenders is the history link text).

The following table lists the supported attributes for the Field element for the MyGenieFieldMaps.CONFIG file.

Attribute	Required	Default	Purpose
AppName	Yes	None	The value here is the original field name used by the Genie application; do not change or omit the value.
BoxLabel	No	Should be the same as the AppName attribute.	The value here is the text that appears above the edit box for this field. It also appears in error messages and on-page hints referencing this field. It is the default label for the field in Full Display reports and search pages, unless overridden by a Display attribute in the report or search page definition (separate configuration files). Do not omit this attribute unless you plan to provide Display parameters for all references to this field in Full Display reports and search pages.
Required	No	What is specified on edit page	A value of "true" here makes a red asterisk appear before a box label on Genie edit pages.
UserName	No	Should be the same as the AppName attribute.	The value here is the name of the equivalent field in your textbase structure in SOAP-friendly format (for example, spaces and hyphens changed to underscores). You can change this value with certain exceptions. For the primary ID field for each textbase, the UserName attribute is omitted for these fields. If you supply a UserName different from the AppName, it will be ignored. If you rename the field in the textbase using CS/TextWorks, this will break the Genie application for this textbase.
VList	No	What is specified on the edit page	A value of "true" here makes a Browse link appear after a box label on Genie edit pages.

Example of the BORROWER section


<inmg:FieldMap TextbaseName="Borrower" Heading="Borrowers" HistoryLink="Borrower">
    <Field AppName="BorrID" />
    <Field AppName="BorrName" UserName="BorrName" BoxLabel="Name" VList="false" />
    <Field AppName="BorrNumber" UserName="BorrNumber" BoxLabel="Borrower
	Number" VList="false" Required="false" />
    ...
    <Field AppName="BorrEmail" UserName="BorrEmail" BoxLabel="E-mail"
	VList="false" Required="false" />
    ...
</inmg:FieldMap>

Example of the BORROWER section with changes

In the BorrName element, the Username and BoxLabel attributes have been changed. In the BorrEmail element, the UserName attribute is not include because the original value is acceptable, and the BoxLabel attribute has been changed.


<inmg:FieldMap TextbaseName="Borrower" Heading="Borrowers" HistoryLink="Borrower">
   <Field AppName="BorrID" />
   <Field AppName="BorrName" UserName="Full_Name" BoxLabel="Full Name (last, first)" 
	VList="false"/>
   ...
   <Field AppName="BorrEmail" BoxLabel="E-mail Address" Required="true" />
	...
</inmg:FieldMap>

Changing a Field Name

You can change a field name if you really must. To do so, you have to change the field name in the textbase with CS/TextWorks and specify that change in the UserName attribute for the applicable textbase section in the MyGenieFieldMaps.CONFIG file to reflect the change in the application.

Example of changing a field name

<Field AppName="LoanItemBC" UserName="LoanItemBarCode" BoxLabel="Item Bar Code" 
	VList="false" Required="false" />

Note that a field name submitted in XML must be valid, both in terms of the Content Server product and in terms of the Genie application. The field name must be a valid Content Server field name. When you change the field name in the textbase using CS/TextWorks, it will ensure that the field name is compliant. When you then specify the new name in the MyGenieFieldMaps.CONFIG file, you should modify the name as instructed in the Content Server help topic "Creating Tag Names for XML Input" (for example, by replacing spaces with underscores). Note that Genie uses the SOAPFormat ON setting, so be sure to use the appropriate instructions. Also be sure to specify the appropriate case. If a textbase field name is "CatEditor," do not set the UserName attribute in the MyGenieFieldMaps.CONFIG file to "cateditor." XML is case-sensitive.

Important! You cannot change the following field names because they are used as unique identifiers in the Genie textbases. They also omit the UserName attribute to indicate that they cannot be renamed.

CatID in CATALOG	LoanID in LOANS
BorrID in BORROWER	OrdID in ORDERS
ILLID in ILL	ResID in RESERVES
ILnID in ILLENDER	SerID in SERIALS
ItemID in ITEMS	SuppID in SUPPLIER

In addition, if you rename the LoanTerm or LoanDateLoaned fields in LOANS, you have to update the Computed Number Definition for the LoanDateDue field so that the formula uses the new field names.

Including a Required-field Indicator

You can make a field be required in a Genie textbase. You do this with CS/TextWorks. To make it obvious in the Genie application that an end user must fill in that field, you specify this requirement by changing the value of the Required attribute to "true" for that field in the applicable textbase section of the MyGenieFieldMaps.CONFIG file. For the Genie application, this visual signal is a red asterisk on a Web edit page.

Example of including a Required-field indicator


<Field AppName="BorrEmail" UserName="BorrEmail" BoxLabel="E-mail" VList="false"
	Required="true" />

A field may be specified as a required field because that is the way you set it up in the textbase or because the field is required by the Genie application. For example, the BorrName field on the Genie Add New Borrower page is a required field, but the BorrDepartment field is not. However, you could configure it so that the BorrDepartment field is required. If you do so, we strongly recommend that you include a visual signal with this field in the Genie application.

It is the designer’s responsibility to ensure that the visual signal matches the actual field attribute, to avoid confusing the end user. If you make a field a required field and do not provide a visual indicator of this, the only way a user will know about the required field is when he or she tries to save the record and the application presents an error message saying that a value is expected in the required field.

Note that with a few exceptions, actual required-field validation is done when a record is submitted to the textbase.

The exceptions are controls that have ASP.NET client- or server-side validation applied. These controls will prohibit submission of a form with the specified boxes empty. The ones representing textbase fields are:

Title on the CATALOG add and edit pages
Name on the BORROWER add and edit pages
Requestor on the ILL add and edit pages
Name on the ILLENDER add and edit page
Item Bar Code and Term of Loan on the LOANS edit page
Borrower, Items, and Term of Loan on the LOANS checkout page
Order Number, Item Number, Number of Copies, and List Price on the ORDER add and edit pages
Name and Type on the Edit Reserve List page
Title on the SERIALS edit pages
Company Name on the SUPPLIER add and edit pages

The required-field indicator cannot be removed from these controls. Any attempt to do so in the configuration file will be ignored.

Including a Browse Link

You can include a browse link option on an editable box on a Web edit page. Visually, this means a Browse link will appear next to a box label on a Web edit page. To do so, add a validation list to a Genie textbase field, which you do with CS/TextWorks. To make the validation list accessible with the corresponding editable box in the Genie application, you have to set the VList attribute to "true" for that field in the applicable textbase section of the MyGenieFieldMaps.CONFIG file. This link, when clicked by an end user, opens a dialog box with a list of validation terms for the field.

Example of including a Browse link


<Field AppName="BorrDepartment" UserName="BorrDepartment" BoxLabel="Department" 
	VList="true" Required="false" />

Adding a New Field

You can add a new field to the Genie application. There are placeholders in Genie for a limited number of fields that you can add to each textbase and expose in the Web pages. These placeholders are invisible to the GUI for the application until you make them appear.

To add a new field, you would first add it to a Genie textbase using CS/TextWorks. Then to make a corresponding edit box appear on an edit form, you must add a UDF (user-defined field) entry for that new field in the applicable textbase section of the MyGenieFieldMaps.CONFIG file and map the UDF to the field by specifying the field name in the UserName attribute of that UDF entry.

Note: Genie contains several "workflow" forms, such as Check Items Out for LOANS and Set Up Serial Arrival Pattern for SERIALS that are not, strictly speaking, edit forms. Therefore these forms do not include accommodations for UDFs.

Example of adding a field

If you wanted to enter birthdates for your borrowers, you would add a Birthdate field to the BORROWER textbase. To make this field appear in edit forms in the Genie application, you would add a corresponding UDF entry to the BORROWER section of the MyGenieFieldMaps.CONFIG file, as illustrated:

<Field AppName="UDF01" UserName="Birthdate" BoxLabel="Date of Birth" VList="false"
	Required="false" />

Note that there is one additional attribute you can specify for a UDF: the height of the edit box, in lines. Use the optional NumLines attribute. For example:

<Field AppName="UDF02" UserName="Contacts" BoxLabel="Contacts" VList="false"
	Required="false" NumLines="2" />

Note that the default is NumLines="1" if you do not specify this setting, and the corresponding box always has a vertical scroll bar even if it is one line high.

UDFs have generic names in the Genie application: UDF01, UDF02, UDF03, and so forth. Twenty UDFs (UDF01 - UDF20) are available for the BORROWER, CATALOG, ILL, ILLENDER, ORDERS, and SUPPLIER textbases, and eight UDFs (UDF01 - UDF08)are available for the SERIALS and LOANS textbases. The other textbases have no accommodation for adding user-defined fields.

Most edit pages display edit boxes in two (2) columns. The boxes for the UDFs will appear at the bottom and proceed in left-right fashion:

UDF01	UDF02
UDF03	UDF04

In the case of the Catalog edit page, where the edit boxes are divided among four tabs, the 20 available UDFs have been distributed among the tabs. UDF01–UDF04 are on the Biblio 1 tab, UDF05–UDF08 are on the Biblio 2 tab, UDF09–UDF16 are on the Physical tab, and UDF17-UDF20 are on the Serials tab. If you only map one of the UDFs in a row, it will appear in the left-most column.

Note: As of Genie 2.00, you can control where UDF fields appear on the Summary and Full Display reports by adding them to your MyReports.CONFIG file. The same is true for the MyQueries.CONFIG file.

Tip! The Genie application shows only those fields that are the most commonly used. If, for example, you are moving from Inmagic^® DB/Text^® for Libraries to Inmagic^® Genie and you used fields in a textbase that do not appear on a page in the Genie application, you can use the UDF fields to make the fields you use appear.

About Deleting Fields

Do not delete any of the textbase fields exposed in the Genie application. Fields not involved in the business logic can be repurposed (for example, rename CatResponsibility to CatAdditionalAuthors) or ignored (for example, change a box label for a not-needed field to Do Not Use). Deleting a textbase field may interfere with the functioning of the application.

Changing a Box Label

You can change a box label for the Genie application if you want. This change only has to be made in the MyGenieFieldMaps.CONFIG file by changing the value of the applicable BoxLabel attribute. Many characters may be used for box labels. However, note that several punctuation characters should not be used. For example, the following will cause error messages:

"	Will cause an error message to appear at the very top of the first Genie page you access and will cause all the changes in the MyGenieFieldMaps.CONFIG file to be ignored. If you must use this symbol, use its encoded equivalent, "
&	Will cause an error message to appear at the very top of the first Genie page you access and will cause all the changes in the MyGenieFieldMaps.CONFIG file to be ignored. If you must use this symbol, use its encoded equivalent, &
<	Will cause .Net error messages. Even if you use its encoded equivalent, the result will not be as you want.

Example of changing a box label

The value here is the text that appears above the edit box for this field. It also appears in error messages and on-page hints referencing this field. It is the default label for the field in Full Display reports and search pages, unless overridden by a Display attribute in the report or search page definition (separate configuration files). Do not omit this attribute unless you plan to provide Display attributes for all references to this field in Full Display reports and search pages.

<Field AppName="BorrTelephone" UserName="BorrTelephone" BoxLabel="Phone" VList="false"

Required="false" />

Box labels that you supply are displayed on editable boxes on edit pages. If appropriate, they also appear on search page boxes and field-specific boxes on "workflow" pages (such as the Check Items Out page for LOANS and Set Up Serial Arrival Pattern for SERIALS).

In a few cases, the original edit box label for a field is not the same as the original query box label for that field. In those cases, the MyGenieFieldMaps.CONFIG file omits the BoxLabel attribute. If you decide to supply a box label for these fields, that label will appear on the edit box and the query box for that field (unless the query box definition in the MyQueries.CONFIG file contains an overriding Display attribute).

Changing the text in a Heading and/or History Link for a Page

You should make these changes in your MyGenieFieldMaps.CONFIG file.

You can change the text in a heading and/or history link for a page. The heading text is what typically appears after "Inmagic Genie:" on a page. The history link is directly under the heading area and shows how you got to where you are. The history link text is part of the label that describes a type of page (for example, the history link for a search page for the catalog would be "Catalog Search", where Catalog is the history link text.)

You may want to change the text for a heading and/or history link to use more understandable terms for your end users. In the absence of a setting in the MyGenieFieldMaps.CONFIG file, the application uses the name of the textbase. For example, in the case of the CATALOG textbase, using the name of the textbase may suffice. However, in the case of the ILLENDER textbase, we have provided you with more easily understandable text for the heading and history link, which you can change as you want.

Change or add a Heading attribute and/or HistoryLink attribute to the first inmg:FieldMap element for a textbase section, as illustrated for the ILLENDER textbase:

<inmg:FieldMap TextbaseName="ILLender" Heading="Interlibrary Lenders" HistoryLink="IL Lenders">

Examples of headings and history links

The following illustration shows the heading and history link for the pages for the CATALOG textbase in the MyGenieFieldMaps.CONFIG file. No changes have been made to the section of the configuration file because the name of the textbase can be used in both the heading name (Inmagic Genie: Catalog) and the history link text (Catalog Search > Search Results) with clarity.

<inmg:FieldMap TextbaseName="Catalog">

The following illustration shows the heading and history link for the ILLENDER textbase without any Heading and/or HistoryLink attributes. Users may not recognize what function they are dealing with because the heading ((Inmagic Genie: ILLender) and the history link text (ILLender Search > Search Results) may not be easily understandable.

<inmg:FieldMap TextbaseName="ILLender">

The following illustration shows the heading and history link for the ILLENDER textbase in the MyGenieFieldMaps.CONFIG file with Heading and/or HistoryLink attributes. End users should more easily recognize what function they are dealing with because the heading (Inmagic Genie: Interlibrary Lenders) and the history link text (IL Lender Search > Search Results) are more easily understandable.

<inmg:FieldMap TextbaseName="ILLender" Heading="Interlibrary Lenders" HistoryLink="IL Lender">

More Information About Field Attributes in CS/TextWorks

The following apply to field attributes that have not been specifically mentioned.

You can change field type and special filing rules for most fields. The exceptions are noted here.
You must not change the field type of an Automatic Number field, or the field type or associated field for a Link field.
You can add a word or term index to a field, but removing an index may have an impact on Web-based queries.
You should communicate changes in the validation rules for a field to anyone who will be editing records over the Web. You may be able to use the

BoxLabel

<Field AppName="BorrEmail" BoxLabel="E-mail (single-entry only)"

MyLabels.CONFIG File

Use the MyLabels.CONFIG file to set up label formats to suit your organization's needs. Out of the box, the MyLabels.CONFIG file is set up with labels formats to print University Products labels and Gaylord labels, and spine labels.

Important! Whenever you make changes to this configuration file, you must restart IIS.

You can make changes to the following levels in the MyLabels.CONFIG file:

Label. At this level (Label element) you create your label settings.
TextArea. At this level (TextArea element) you specify the areas where label information can be printed.
Field. At this level (Field element) you specify the field data to be printed in the defined text area.

To create a new label format, we suggest you copy a label format already created and defined in the MyLabels.CONFIG file and change the copied elements group as necessary for your new label format. For your new label format:

For the Label element, change the Name attribute, which is required and must be unique for every label format, and the other attributes, as necessary. Note that, typically, this name does not appear in the user interface. The name should avoid characters that need to be escaped in XML, including ampersand, angled brackets, and extended characters. It may be useful to the limit use of punctuation in label names. Case is also significant.
Change the attributes for the TextArea element as needed to specify the areas where label information can be printed.
Change the attributes in the Field element as needed to specify the field data to be printed in the defined text area.

Making Label-level Changes for Label Formats

The following is an example of the Label element for Gaylord labels:


<inmg:Label Name="Gaylord" LabelSetWidth="7.5" LabelSetHeight="1.25"
	Unit="inch" NumberAcross="1" LeftMargin="0.5" TopMargin="0.5"
	BottomMargin="0.5" ShowBorder="false">
<TextArea Name="Box1" Left="0.2" Top="0.1" Width="0.6" Height="1.10"> 
<Field Name="CatCallNumber" TreatAs="WordList"/> 
</TextArea>
...
</inmg:Label >

The following table lists the supported attributes for the Label element.

Attribute	Required	Default	Explanation
BottomMargin	No	0.5	Sets the bottom print margin. *Tip!* You can use this attribute to adjust the page break.
LabelSetHeight	Yes	None	Sets the height of a label set.
LabelSetWidth	Yes	None	Sets the width of a label set.
LeftMargin	No	0.5	Sets the left print margin.
Name	Yes	None	Unique name for the label type. It should be the same as the one listed in the LibraryCart/Action section of the MyGenie.CONFIG file.
NumberAcross	Yes	None	Sets the total number of label sets across horizontally.
TopMargin	No	0.5	Sets the top print margin.
ShowBorder	No	false	Displays border of label set and text area. It should always be false for normal use. *Tip!* You can set this attribute to true to help with troubleshooting any problems.
Unit	No	inch	The applicable values are inch and cm.

Making TextArea-level Changes for Label Formats

The following is an example of the TextArea element for Gaylord labels:


<inmg:Label Name="Gaylord" LabelSetWidth="7.5" LabelSetHeight="1.25"
	Unit="inch" NumberAcross="1" LeftMargin="0.5" TopMargin="0.5"
	BottomMargin="0.5" ShowBorder="false">
<TextArea Name="Box1" Left="0.2" Top="0.1" Width="0.6" Height="1.10"> 
<Field Name="CatCallNumber" TreatAs="WordList"/> 
</TextArea>
...
<TextArea Name="Box5" Left="5.35" Top="0.1" Width="2.11" Height="1.10"> 
<Field Name="CatAuthor" Footer="&lt;br/&gt;"/>
<Field Name="CatTitle" UpperCase="true"/> 
</TextArea>
</inmg:Label >

The following table lists the supported attributes for the TextArea element.

Attribute	Required	Default	Explanation
Height	Yes	None	Sets the height of the text area. *Tip!* If a line is cut off in the middle when you print the label set, shorten the height to eliminate the half-line.
Left	Yes	None	Sets the absolute position at left within the label set.
Name	Yes	None	Unique name for the text area.
Top	Yes	None	Sets the absolute position at top within the label set.
Width	Yes	None	Sets the width of the text area.

Making Field-level Changes for Labels Formats

The following is an example of the Field element for Gaylord labels:


<inmg:Label Name="Gaylord" LabelSetWidth="7.5" LabelSetHeight="1.25"
	Unit="inch" NumberAcross="1" LeftMargin="0.5" TopMargin="0.5"
	BottomMargin="0.5" ShowBorder="false">
<TextArea Name="Box1" Left="0.2" Top="0.1" Width="0.6" Height="1.10"> 
<Field Name="CatCallNumber" TreatAs="WordList"/> 
</TextArea>
...
<TextArea Name="Box5" Left="5.35" Top="0.1" Width="2.11" Height="1.10"> 
<Field Name="CatAuthor" Footer="&lt;br/&gt;"/>
<Field Name="CatTitle" UpperCase="true"/> 
</TextArea>
</inmg:Label >

The following table lists the supported attributes for the Field element.

Attribute	Required	Default	Explanation
CssClass	No	None	Css Class applied to field contents, headers, and footers.
Footer	No	None	Used to add extra characters after the field contents.
Header	No	None	Used to add extra characters and before the field contents.
Name	Yes	None	Should be the same as the AppName attribute defined in the MyGenieFieldMaps.CONFIG file for the field names in the CATALOG textbase.
Separator	No	"; "	Used when a field has multiple entries.
Style	No	None	HTML style applied to field contents, headers, and footers.
Uppercase	No	As returned from the textbase	If you use a value of true, then all text will print out in uppercase.

MyNavbarMenuData.CONFIG File

Use the MyNavbarMenuData.CONFIG file to change the look of the Genie navigation bar to suit your organization's needs.

Changing the text and/or image for a navigation bar button and its command links
Hiding a navigation bar button and all its command links.
Hiding a command link for a navigation bar button
Re-ordering the appearance of the navigation buttons and/or command links
Making a command link not appear depending on login

Changing the Text and/or Image for a Navigation Bar Button and its Command Links

Find the group of XML elements in the MyNavbarMenuData.CONFIG file that describes the section of the navigation bar that you want to change. Out of the box, the elements for each navigation bar button and its command links are listed in the following order: Catalog, Borrower, Loan, Serial, Supplier, Order, ILL, and Other.
The first Item element for a menu group (for example, Item Id="Catalog"...) corresponds to the navigation bar button.

To change the text for the button, change the text after the "Text" attribute in the applicable element group.
To change the image for the button, change the name of the GIF file for the "Look-LeftIconUrl" attribute. Note that the GIF file must reside in the Images subfolder of the main Genie installation folder (for example, C:\Program Files\Genie\Images). To make an image not appear, you can delete the image file name.

The Item elements nested within the menu element describe the command links for the particular menu.

To change the image associated with a command link, change the name of the GIF file for the "Look-LeftIconUrl" attribute in that applicable nested element.
To change the text for a command link, change the text for the "Text" attribute.

Save the configuration file.

Example of the Catalog menu group

The following shows the elements group for the Catalog menu and its command links and images, before you make any changes to them.


<Item Id="Catalog" Text="Cataloging" itemtype="Menu" DefaultSubItemLookId="Level2ItemLook" 
		SubGroupCssClass="Level2Group" SubGroupItemSpacing="5" Expanded="false" 
		Look-LeftIconUrl="Catalog.gif">	
	<Item Id="Catalog_CartLink" Look-LeftIconUrl="infocart.gif" 
		Text="item(s) in cart" NavigateURL="catalog_cart.aspx "
		permission="Administrators Catalogers Staff"></Item>
	<Item Id="Catalog_Search" Look-LeftIconUrl="Book-Search.gif" Text="Search Catalog" 
		NavigateURL="catalog_search.aspx" permission="Administrators Catalogers Staff"></Item>
	<Item Id="Catalog_Add" Look-LeftIconUrl="Card-Edit.gif" 
		Text="Add New Catalog Item" NavigateURL="catalog_edit.aspx"
		permission="Administrators Catalogers"></Item>
</Item>

Example of the Catalog group, customized

The following shows the elements group for the Catalog menu and its command links with customizations. In the top-level Item element both the text for the navigation bar button and the image for the button have been changed. In the first nested Item element within the elements group, only the image has been changed. In the second and third nested Item elements, only the text for the command links has been changed. In addition, in the third nested Item element, the image file name has been deleted so that only the command link text appears on the navigation bar.


<Item Id="Catalog" Text="Catalogue" itemtype="Menu" DefaultSubItemLookId="Level2ItemLook" 
		SubGroupCssClass="Level2Group" SubGroupItemSpacing="5" Expanded="false" 
		Look-LeftIconUrl="Bookshelves.gif">	
	<Item Id="Catalog_CartLink" Look-LeftIconUrl="Blue_cart.gif" 
		Text="item(s) in cart" NavigateURL="catalog_cart.aspx "
		permission="Administrators Catalogers Staff"></Item>
	<Item Id="Catalog_Search" Look-LeftIconUrl="Book-Search.gif" 
		Text="Search Catalogue" NavigateURL="catalog_search.aspx" 
		permission="Administrators Catalogers Staff"></Item>
	<Item Id="Catalog_Add" Look-LeftIconUrl="" 
		Text="Add New Catalogue Item" NavigateURL="catalog_edit.aspx"
		permission="Administrators Catalogers"></Item>
</Item>

Hiding a Navigation Bar Button and All its Command Links

Find the elements group in the MyNavbarMenuData.CONFIG file that contains the section of the navigation bar that you want to hide. Out of the box, the elements group for each navigation bar button and its command links are listed in the following order: Catalog, Borrower, Loan, Serial, Supplier, Order, ILL, and Other.
Insert comment codes at the very beginning of this section and at the very end of the section.
Save the configuration file.

Example of hidden Interlibrary Loans navigation bar button and its command links

The following shows the elements group for the Interlibrary Loans navigation bar button and its command links commented out so that this menu does not appear on the navigation bar. The begin comment code  is at the end of the commented out section.


<!--	<Item Id="ILL" Text="Interlibrary Loans" itemtype="Menu" 
			DefaultSubItemLookId="Level2ItemLook" 
			SubGroupCssClass="Level2Group" SubGroupItemSpacing="5" 
			Expanded="false" Look-LeftIconUrl="interlibrary-loans.gif">
		<Item Id="ILL_Search" Look-LeftIconUrl="search-loans.gif" 
			Text="Search Loans" NavigateURL="ill_search.aspx" 
			permission="Administrators Catalogers Staff"></Item>
		<Item Id="ILL_Add" Look-LeftIconUrl="add-loan.gif" Text="Add New Loan" 
			NavigateURL="ill_edit.aspx" 
			permission="Administrators Catalogers Staff"></Item>
		<Item Id="ILLender_Search" Look-LeftIconUrl="search-lenders.gif" 
			Text="Search Lenders" NavigateURL="illender_search.aspx" 
			permission="Administrators Catalogers Staff"> </Item>
		<Item Id="ILLender_Add" Look-LeftIconUrl="add-lender.gif" 
			Text="Add New Lender" NavigateURL="illender_edit.aspx" 
			permission="Administrators Catalogers Staff"></Item>
	</Item> -->

Hiding a Command Link for a Navigation Bar Button

Find the elements group in the MyNavbarMenuData.CONFIG file that contains the command link you want to hide. Out of the box, the elements group for each navigation bar button and its command links are listed in the following order: Catalog, Borrower, Loan, Serial, Supplier, Order, ILL, and Other.
Insert comment codes at the very beginning of the Item element for the command link and at the very end of the element.
Save the configuration file.

Example of hidden Order Items command link from Orders navigation bar button

The following shows the elements group for the Orders navigation button and its command links. One of them is the Order Items command link, which has been commented out so that it does not appear in the navigation bar. The begin comment code  is at the end of the commented out element.


<Item Id="Order" Text="Orders" itemtype="Menu" 
		DefaultSubItemLookId="Level2ItemLook"
		SubGroupCssClass="Level2Group" SubGroupItemSpacing="5" 
		Expanded="false" Look-LeftIconUrl="orders.gif">
	<Item Id="Orders_Search" Look-LeftIconUrl="search-orders.gif" 
		Text="Search Orders" NavigateURL="orders_search.aspx" 
		permission="Administrators Catalogers Staff"></Item>
	<Item Id="Order_Serial" Look-LeftIconUrl="order-serials.gif" 
		Text="Order Serials" NavigateURL="orders_edit.aspx?Serial=true" 
		permission="Administrators Catalogers"></Item>
<!--	<Item Id="Order_Items" Look-LeftIconUrl="order-items.gif" 
		Text="Order Items" NavigateURL="orders_edit.aspx" 
		permission="Administrators Catalogers"></Item> -->
	<Item Id="Receiving_Order" Look-LeftIconUrl="receiving-orders.gif" 
		Text="Receiving Orders"
		NavigateURL="orders_Search.aspx?Receiving=true" 
		permission="Administrators Catalogers"></Item>
</Item>

Re-ordering the Appearance of the Navigation Buttons and/or Command Links

You can re-order the navigation bar buttons and/or command links by moving the applicable elements group (for a button and its command links) or a particular nested element for a command link. Wherever you move the command link is where it will appear on the navigation bar, whether you move it within the same button, move it under another button, or move it to the top level of the navigation bar. For example, if you move a command link between two elements groups (say the Catalog and Borrower groups), the command link is inserted as a button link between the two other buttons you inserted in between. You can move the command link to the top of the navigation bar and the bottom of it. As another example, you may want to move the Log Out function from under the Other button to the top level of the navigation bar.

To re-order a navigation bar button and its command links, select the elements group in the MyNavbarMenuData.CONFIG file that contains the configuration elements for the button and its command links. Out of the box, the element groups for each navigation bar button and its command links are listed in the following order: Catalog, Borrower, Loan, Serial, Supplier, Order, ILL, and Other. Use the Cut command to cut the section, go to the place where you want to insert the navigation bar button and its command links, and use the Paste command to insert the section where you want it.
To re-order a link, select the Item ID nested element for the link and use the Cut and Paste commands.
Save the configuration file.

Example of a link moved to top level of the navigation bar

Out of the box, the link to log out resides under the Other button. The following shows the elements group for the Other button group with the nested Item element for the logout function outside of the Other button group. Because of its placement in the example, a Log Out button is added to the navigation bar after the Other button. This gives you top-level access to the logout function.


<Item Id="Other" Text="Other" itemtype="Menu" 
	DefaultSubItemLookId="Level2ItemLook" SubGroupCssClass="Level2Group"
	SubGroupItemSpacing="5" Expanded="false" Look-LeftIconUrl="other.gif">
   <Item Id="Other_Help" Look-LeftIconUrl="about.gif" Text="Help Topics" 
	NavigateURL='javascript:OpenHelpWindow(0,"")'
	permission="Administrators Catalogers Staff"></Item>
   <Item Id="Other_EMail" Look-LeftIconUrl="letter.gif" Height="32" 
	Text="Set Up E-mail Information" NavigateURL="ConfigurePage.aspx" 
	permission="Administrators Catalogers"></Item>
   <Item Id="Other_Logins" Look-LeftIconUrl="padlock.gif" Height="32" 
	Text="Manage Security &amp; Logins" NavigateURL="key_search.aspx"
	permission="Administrators"></Item>
   </Item>
<Item Id="Other_LogOut" Look-LeftIconUrl="Logout.gif" Text="Log Out" 
	NavigateURL="logout.aspx" permission="Administrators Catalogers 
	Staff"></Item>

Making a Command Link Not Appear Depending on Login

You can use the MyNavbarMenuData.CONFIG file to control if a command link appears on the navigation bar depending on the login. The permission attribute for each command link string in the MyNavbarMenuData.CONFIG file is for convenience and is not a security function. For example, if you do not want your library staff to be able to add new lenders for interlibrary loans, you can make the Add New Lender command link under the Interlibrary Loans button on the navigation bar not appear for those who log on as library staff while keeping it for those who log on as administrators or catalogers.

Find the elements group in the MyNavbarMenuData.CONFIG file that contains the command link that you want to make not appear depending on the login. Out of the box, the elements group for each navigation bar button and its command links are listed in the following order: Catalog, Borrower, Loan, Serial, Supplier, Order, ILL, and Other.
In the permission attribute for the command link element, delete the value that corresponds to the login type.
Save the configuration file.

Example of making a command link not appear depending on login

The following shows the elements group for the Interlibrary Loans button group. Every command link is set to show all command links when you log in as an administrator (admin). However, when you log in as library staff (staff), you will not see the Add New Lender command link.


<Item Id="ILL" Text="Interlibrary Loans" itemtype="Menu" 
		DefaultSubItemLookId="Level2ItemLook" 
		SubGroupCssClass="Level2Group" 
		SubGroupItemSpacing="5" Expanded="false" 
		Look-LeftIconUrl="interlibrary-loans.gif">
	<Item Id="ILL_Search" Look-LeftIconUrl="search-loans.gif" 
		Text="Search Loans" NavigateURL="ill_search.aspx" 
		permission="Administrators Catalogers Staff"></Item>
	<Item Id="ILL_Add" Look-LeftIconUrl="add-loan.gif" Text="Add New Loan" 
		NavigateURL="ill_edit.aspx" 
		permission="Administrators Catalogers Staff"></Item>
	<Item Id="ILLender_Search" Look-LeftIconUrl="search-lenders.gif" 
		Text="Search Lenders" NavigateURL="illender_search.aspx" 
		permission="Administrators Catalogers Staff"></Item>
	<Item Id="ILLender_Add" Look-LeftIconUrl="add-lender.gif" 
		Text="Add New Lender" NavigateURL="illender_edit.aspx" 
		permission="Administrators Catalogers"></Item>
	...
</Item>

MyQueries.CONFIG File

The MyQueries.CONFIG file defines all the search pages (for example, the Borrower Search page, the Catalog Search page) provided for the application. You can use this configuration file to add or remove a query box on a search page. You cannot use it to create a new search page.

To change a search page

Open the MyQueries.CONFIG file.
Find the <inmg:QueryScreen...> section that defines the search page that you want to change. For example, <inmg:QueryScreen Name="borrower_search"... > for the Borrower Search page, <inmg:QueryScreen Name="catalog_search"... > for the Catalog Search page, and so forth. To learn about this element, see The QueryScreen Element. The following example shows this element for the Borrower Search page.


<inmg:QueryScreen Name="borrower_search" Title="Borrower Search" 
	BrowseButtonText="Browse" BooleanAnd="AND" BooleanOr="OR" 
	BooleanNot="NOT" >
   <QueryField Type="QueryField" Display="Any Word" 
	CssClass="SearchTextInput" LabelCssClass="SearchLabel" 
	ShowBrowse="false" ShowBoolean="true" FieldList="BorrNumber 
	| BorrName | BorrDepartment | BorrTelephone | BorrFax | BorrEmail 
	| BorrAddress | BorrMailStop | BorrCity | BorrState | BorrPostalCode  
	| BorrCountry"/> 
   ...
</inmg:QueryScreen>

Depending on what you want to do:

To add a new query box to a search page: Copy a <QueryField Type... /> string from the ones already provided and change the applicable attributes. For example, change the Type, Display, and FieldList attributes. To learn about this element, see The QueryField Element. The following example shows adding a query box to the Borrower Search page, which is not provided out-of-the-box for the application.


<inmg:QueryScreen Name="borrower_search" Title="Borrower Search" 
	BrowseButtonText="Browse" BooleanAnd="AND" BooleanOr="OR" 
	BooleanNot="NOT" >
   <QueryField Type="QueryField" Display="Any Word" 
	CssClass="SearchTextInput" LabelCssClass="SearchLabel" 
	ShowBrowse="false" ShowBoolean="true" FieldList="BorrNumber 
	| BorrName | BorrDepartment | BorrTelephone | BorrFax | BorrEmail 
	| BorrAddress | BorrMailStop | BorrCity | BorrState 
	| BorrPostalCode | BorrCountry"/>
  <QueryField Type="QueryField" CssClass="SearchTextInput" 
	LabelCssClass="SearchLabel" ShowBrowse="true" 
	ShowBoolean="true" FieldList="BorrName"/> 
   <QueryField Type="QueryField" CssClass="SearchTextInput" 
	LabelCssClass="SearchLabel" ShowBrowse="true" 
	ShowBoolean="true" FieldList="BorrNumber"/> 
   <QueryField Type="QueryField" Display="Telephone Number" 
	CssClass="SearchTextInput" LabelCssClass="SearchLabel" 
	ShowBrowse="true" ShowBoolean="true" 
	FieldList="BorrTelephone"/> 
   ...
</inmg:QueryScreen>

Note that wherever you place the QueryField element is where the query box will appear on the search page.

To remove a query box: Delete the entire <QueryField... /> element.

Save the configuration file and restart IIS.

The QueryScreen Element

In the MyQueries.CONFIG file, the QueryScreen element identifies the search page and contains its configuration settings in the format string (list of attributes). The following table lists the supported attributes for this element.

Attribute	Required	Default	Explanation
BooleanAnd	No	"AND"	Identifies Boolean AND in the AND, OR, NOT drop-down list that appears to the left of the query boxes.
BooleanOr	No	"OR"	Identifies Boolean OR in the AND, OR, NOT drop-down list that appears to the left of the query boxes.
BooleanNot	No	"NOT"	Identifies Boolean NOT in the AND, OR, NOT drop-down list that appears to the left of the query boxes.
BrowseButtonText	No	" Browse "	Use to set the text that appears on the [out-of-the-box] Browse button that appears to the right of the query box.
Heading	No	Textbase name	This value for this attribute is applied to the page heading. The page heading is the top heading on a (search) page (for example, "Inmagic Genie: Borrowers").
Name	Yes	None	Do not change this attribute value. Use to identify the search page name. The value for this attribute matches the ASPX page name.
Title	No	Textbase name	This value for this attribute is applied to the (search) page title and in the title bar of the browser window. A page title appears below a page heading, for example, "Borrower Search".

The QueryField Element

The QueryField element lets you specify the query boxes that you want to appear in the search page and the element contains its configuration settings in the format string. You can specify one or more fields from either the primary or a linked textbase to search. The textbase fields listed in the FieldList attribute should be the same as the AppName attribute specified in the MyGenieFieldMaps.CONFIG file for any field that is to be searched.

The following table lists the supported attributes for the QueryField element.

Attribute	Required	Default	Explanation
CssClass	No	For a query box, use "SearchTextInput". For a check box, use "SearchCheckBox".	CSS class used for the text users type or paste in a query box or the text associated with a check box.
Display	No	If this attribute is not set, the default is taken from the BoxLabel attribute in the MyGenieFieldMaps .CONFIG file for the first field in the FieldList attribute.	If this value is included, it has a higher priority than the BoxLabel attribute in the MyGenieFieldMaps.CONFIG file. Typically you would want to set this attribute if your query box searches more than one field (for example, out of the box, the Any Word query box on the Borrower Search page [as shown in the example below] and the Catalog Search page).
FieldList	Yes	None	Use to determine which fields are to be searched by that query box. If more than one field is to be searched, separate each field name with a pipe character ( \| ) as shown in the example below for the Borrower Search page. The field names in the FieldList entry must match the AppName attribute for the textbase as listed in the MyGenieFieldMaps.CONFIG file. Note that if a field to be searched is a field in a secondary textbase, then you must specify it in the format SecondaryFieldName .PrimaryLinkFieldName. See the example below with "BorrName.LoanBorrID \| ... />, where BorrName refers to the BorrName field in the secondary textbase (BORROWER), and LoanBorrID the Link field in the primary textbase (LOANS) that links to the secondary textbase. Note also that if there is only one value for this attribute and it is missing (in other words, FieldList=""), this query box will not appear on the search page.
LabelCssClass	No	"SearchLabel"	Css class, defined in Genie.CSS, used for the query box label.
ShowBoolean	No	true	Set to "true" to display a drop-down list with Boolean AND, OR, NOT before a query box or "false" to hide the drop-down list. Note that in the QueryScreen Name="loans_search" section, because of the intricacies of the Loan Search page, the Boolean drop-down list will always appear for the Loan Date Returned query box. Therefore, the ShowBoolean attribute does not appear in the MyQueries.CONFIG file for this query box. Even if you were to add ShowBoolean="false" for this query box, it would be ignored.
ShowBrowse	No	true	Set to "true" to display a Browse button after a query box or "false" to hide the Browse button.
Type	No	"QueryField" Other values are: "CheckBox" and "ButtonRow". See examples below.	Use to determine how the box is to be treated by the application. CheckBox is only supported for the three out-of-the-box check boxes on the Loan Search page.
The following attributes are for Type="ButtonRow"
ResetButtonText	No	"Reset"	Use to modify the text that appears on the [out-of-the-box] Reset button on search pages. Note that there is no value for this attribute (in other words, Reset=""), this button will not appear on the search page.
SubmitButtonText	Yes	"Submit"	Use to modify the text that appears on the [out-of-the-box] Submit Query button on search pages.
The following attributes are for Type="CheckBox"
chkID	Yes	None	Currently only implemented for the three check boxes on the Loan Search page. This value of chkID is not configurable.
ShowCheckBox	No	true	Set to "true" to display check boxes on the Loan Search page or to "false" to hide the them.

Inmagic® Genie Version 2.00 Technical Notes

Overview

MyGenie.CONFIG File

Adding Your Logo to Your OPAC

Adding a "Location" Drop-down List to the Catalog and OPAC Search Pages

Changing the Date Format for the Application

Changing the Number of Days After the Current Date for the "Needed Before" box on the Add New ILL Request Page

Configuring Volume and Issue Information

To change the format of the output for the volume and issue information

Things to keep in mind

Configuring the File Upload Settings for Catalog Records

Configuring the InfoCart

To configure which Catalog fields appear in InfoCart output

To remove an item from the action drop-down list

To change the label (the text that appears) of an item in the action drop-down list

To re-order the items in the action drop-down list

To specify attributes for the InfoCart for the OPAC

Changing the Items for the Drop-down List for Various Fields

To change the items in the drop-down list for the "Term of Loan" box on the Check Items Out page and the Edit Loan Record page

To change the items in the drop-down list for the "Frequency" box on the Set Up Serial Arrival Pattern page

How to interpret the pattern codes

To change the items in the drop-down list for the "Order Type" box on the New/Edit Order page

To change the items in the drop-down list for the "Payment Method" box on the New/Edit Order page

To change the items in the drop-down list for the "Currency" box on the New/Edit Order page

To change the items in the drop-down list for the "Status" box on the New/Edit Order page

MyGenieFieldMaps.CONFIG File

General Instructions on How to Make Changes

To make changes to a Genie textbase through CS/TextWorks

To make field attribute changes reflect in the Genie application

Example of the BORROWER section

Example of the BORROWER section with changes

Changing a Field Name

Example of changing a field name

Including a Required-field Indicator

Example of including a Required-field indicator

Including a Browse Link

Example of including a Browse link

Adding a New Field

Example of adding a field

About Deleting Fields

Changing a Box Label

Example of changing a box label

Changing the text in a Heading and/or History Link for a Page

More Information About Field Attributes in CS/TextWorks

MyLabels.CONFIG File

Making Label-level Changes for Label Formats

Making TextArea-level Changes for Label Formats

Making Field-level Changes for Labels Formats

MyNavbarMenuData.CONFIG File

Changing the Text and/or Image for a Navigation Bar Button and its Command Links

Example of the Catalog menu group

Example of the Catalog group, customized

Hiding a Navigation Bar Button and All its Command Links

Example of hidden Interlibrary Loans navigation bar button and its command links

Hiding a Command Link for a Navigation Bar Button

Example of hidden Order Items command link from Orders navigation bar button

Re-ordering the Appearance of the Navigation Buttons and/or Command Links

Example of a link moved to top level of the navigation bar

Making a Command Link Not Appear Depending on Login

Example of making a command link not appear depending on login

MyQueries.CONFIG File

To change a search page

The QueryScreen Element

The QueryField Element

Example of the FieldList attribute with multiple fields for the Borrower Search page

Inmagic^® Genie Version 2.00 Technical Notes