~~~~~~~~~~~~~~~~~~~~~~~
Z39.50 server target definitions have been removed from the sample
`opensrf.xml.example` file. To migrate existing settings from your
-`opensrf.xml` configuration file to the database, peform the
+`opensrf.xml` configuration file to the database, perform the
following steps:
1. First, set up your custom Z39.50 sources in the database. For
My Lists
^^^^^^^^
The My Lists feature replaces the bookbag feature that was available in
-versions proior to 2.2. This feature enables you to create temporary and
+versions prior to 2.2. This feature enables you to create temporary and
permanent lists; create and edit notes for items in lists; place holds on items
in lists; and share lists via RSS feeds and CSV files.
User Settings Available from Patron Editor
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-Staff can now access and update user settings, like notification prefererences
+Staff can now access and update user settings, like notification preferences
and default pickup library, in the patron editor.
Mark Patron E-mail or Phone as Invalid
^^^^^^^^^^^^^^^^^^^^^^
Enhancements to notifications by telephony, including:
-* A feature that allows an Evergreen system to roll over failed notifcations
+* A feature that allows an Evergreen system to roll over failed notifications
into new ones with a different notification method.
* Holiday awareness. System administrators can, via `cron`, schedule the
`set_pbx_holidays` script on an Evergreen system to periodically update
will be given an 'in transit' status instead of 'holds shelf'. The intent is
to stop the system from sending holds notifications before the item is ready
to be placed on the holds shelf. Possible use cases include Automated
- Materials Handling(AMH) checkins, in which items may be sitting in a bin for a
+ Materials Handling (AMH) checkins, in which items may be sitting in a bin for a
while before landing on the holds shelf, and checkins done on closed days.
Copy Location Alerts
The Acquisitions Load MARC Order Record interface enables you to add MARC
records to selection lists and purchase orders and upload the records into the
catalog. The Vandelay interface enables you to create specific match points
-between incoming MARC records and exisiting catalog records. Combining these
+between incoming MARC records and existing catalog records. Combining these
two features enables you to track on order MARC records through the
Acquisitions interface and to utilize the record matching mechanisms available
in Vandelay when importing acquisitions records.
Improved Displays for Provider and Fund Administration Pages
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This enhancement provides improved support for viewing the provider and fund
-administation pages. It also allows staff to use filters to find providers and
+administration pages. It also allows staff to use filters to find providers and
funds.
Cataloging
++++++++++++++++++++
If a user has a bookbag with an overly long name, the end of it will
-jut out past the right margin of the menu in FireFox and several other
+jut out past the right margin of the menu in Firefox and several other
browsers. To change this behavior, you may want to edit the `.popmenu
li:hover li a` css entry in `web/css/skin/default/opac/style.css` by
adding an `overflow` property. If you desire to have the longer names
-clipped to the size ofthe menu then add `overlow: hidden`. If you
+clipped to the size of the menu then add `overflow: hidden`. If you
prefer to have a scroll bar for oversized entries, then add `overflow:
auto`.
Public patron notes are now visible in the 'Account Summary' box of 'My
Account'.
-Auto-Override Permissable Patron Hold Fail Events
+Auto-Override Permissible Patron Hold Fail Events
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
A new Library Setting is available that tells TPAC to automatically override
url_prefix('REPLACE/stuff') becomes 'oils://remote/replace/stuff'
url_prefix('REPLACE?query') becomes 'oils://remote/replace?query'
-url_prefix('RPLACE|ment') becomes 'oils://remote/replacement'
+url_prefix('REPLACE|ment') becomes 'oils://remote/replacement'
The pipe is intended for cases where the urls entry may or may not already
contain a query string, say for differences between OPACs where one requires
Numbers 15 (keyword|keyword) and 16 (subject|complete) should generally be set
to false.
-The config.metabib_class table has a new 'bouyant'
+The config.metabib_class table has a new 'buoyant'
column. Setting this to true means that when a user is typing in the OPAC
search box with a search class selector set to, say, 'Subject', and the cmc row
-for 'Subject' has 'bouyant' set to true, the top suggestions will definitely
+for 'Subject' has 'buoyant' set to true, the top suggestions will definitely
come from the Subject fields of MARC records (if any). 'restrict' is like
-'bouyant', only stronger. In that case suggestions /only/ come from the
+'buoyant', only stronger. In that case suggestions /only/ come from the
selected class.
This is the idea behind the 'restrict' column (in both the
At bottom, autosuggest is shaped by PostgreSQL's Full Text Search features.
Some of the arguments that are passed to TS_RANK_CD() and TS_HEADLINE() are
-expoposed via options to the openils.widget.AutoSuggest and
+exposed via options to the openils.widget.AutoSuggest and
openils.AutoSuggestStore modules, which have comments. You can customize your
OPAC files to invoke these with your desired options without touching much
actual code.
[abstract]
Purpose
-------
-Evergreen supplies a broad API for accessing, processing and interacting with library data. Because of the relatively complex nature of the underlying database schema, and the flexibility required by clients when, in the simplest case, performing CRUD operations, focus has been given to providing a nearly direct view of various data source. When, however, the verbosity or complexity of full object access gets in the way of performant or straight-forward UIs, there has been a tendency to create one-off data simplification calls targetting specific use cases.
+Evergreen supplies a broad API for accessing, processing and interacting with library data. Because of the relatively complex nature of the underlying database schema, and the flexibility required by clients when, in the simplest case, performing CRUD operations, focus has been given to providing a nearly direct view of various data source. When, however, the verbosity or complexity of full object access gets in the way of performant or straight-forward UIs, there has been a tendency to create one-off data simplification calls targeting specific use cases.
A generalized API which accepts a simplified query structure and field mapping, calculates the required backend query, and flattens the hierarchical data returned for each top level row into a would facilitate the simplification of existing UIs and provide for new UIs based on simple, reusable components.
--------
The existing, public open-ils.fielder server will be extended with two new OpenSRF methods, contained in a separate package so that they will be reusable in a private service which does not require authentication.
-These methods will be supported by code which takes simplifed cstore/pcrud search and order-by hashes and computes the full data structure required for the query. The simplification will leverage the IDL to discover links between classes.
+These methods will be supported by code which takes simplified cstore/pcrud search and order-by hashes and computes the full data structure required for the query. The simplification will leverage the IDL to discover links between classes.
Underlying the simplified search grammar will be a path-field mapping structure. This will describe the layout of fields, how they are to collapse from fleshed objects, and how the shape of both the query and result data structures should be interpreted by and presented to the caller.
</listitem>
<listitem>
<para>in the field definition for the field in the IDL, the tag
- <literal>"il8n"</literal> is present and true;</para>
+ <literal>"i18n"</literal> is present and true;</para>
</listitem>
<listitem>
<para>the query does <emphasis>not</emphasis> include the
<para> Here we asked for a left outer join. For a right outer join, code
<literal>"type":"right"</literal>. For a full outer join, code
<literal>"type":"full"</literal>. Any other value for "type" results in an inner
- join, so watch out for typos. A type of <literal>"rihgt"</literal> will give you
+ join, so watch out for typos. A type of <literal>"right"</literal> will give you
a wrong join instead of a right one. </para>
<para> Here is the resulting SQL for this example: </para>
We'll talk about setting up Festival in a later step. Strictly speaking, you might not need Festival if your institution doesn't
need its notice message to contain truly dynamic parts (such as reading a
list of overdue titles). Asterisk can read numbers aloud by itself, and if
-you need notices to choose between a finite set of possiblities of things to
+you need notices to choose between a finite set of possibilities of things to
say, you can just make or acquire recordings of each of those things and
choose between them with logic either in the Action/Trigger template or in
the Asterisk dialplan (for example, reading the name of a library branch
Be sure you also installed DAHDI if you're using analog hardware to place phone calls (there are even cases when you want to install it for digital calling; grep Asterisk documentation for "timing source").
When in doubt, just install it. Maybe your package manager already did for you.
-If using analog telephony, get your hardware configured and make sure you can see the things that you're supposed to see with +/usr/sbin/dahdi_tool+ (typical install location, but look around if needed) and the command "dahdi show channels" in the Asterisk interactive console. I'm handwaving over the specifics here. There's a wealth of information avaiable online about how to do this.
+If using analog telephony, get your hardware configured and make sure you can see the things that you're supposed to see with +/usr/sbin/dahdi_tool+ (typical install location, but look around if needed) and the command "dahdi show channels" in the Asterisk interactive console. I'm handwaving over the specifics here. There's a wealth of information available online about how to do this.
If using digital telephony, preferably with the SIP protocol, get that configured in asterisk and make sure your SIP channel(s) is/are up. Again, more specifics on this are available online.
NOTE: I'm sorry I've obviously written the above from a North America-centric perspective; somebody else feel free to correct this.
-When you think you've got something subsituted for X that might work, do the following as root:
+When you think you've got something substituted for X that might work, do the following as root:
-------------------------------------------------------
cp yourfile /tmp
where you substitute "SIP/blah/somenumber" or "DAHDI/N/somenumber" for X as in the earlier example in this document.
-Spool the file as per previous instructions. Does the message being read to you over the phone match the script you have? If so, great. Otherwise, do not continute until you get it right.
+Spool the file as per previous instructions. Does the message being read to you over the phone match the script you have? If so, great. Otherwise, do not continue until you get it right.
Repeat this process to create a hold-available notice, assuming your institution wants one. You'll create a similar chunk of dialplan, but you'll just change the messages and logic to reflect your script for hold-available notices rather than your script for overdue notices.
Action/Trigger Event Definitions
--------------------------------
-It's time to create Action/Trigger Event Definitions (rows in the action_trigger.event_defintion table) for the notifications you want.
+It's time to create Action/Trigger Event Definitions (rows in the action_trigger.event_definition table) for the notifications you want.
Setting up the event definition itself
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Init scripts for the Asterisk box
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-If you installed Asterisk from source instead of from a distro package, look in the source tarball for sample init scripts. Choose the one appropriate for your distro, put it in place, run 'chkconfig' or 'update-rc.d' or whatever's appropritate for your distro, and make sure you can start and stop Asterisk with that init script now.
+If you installed Asterisk from source instead of from a distro package, look in the source tarball for sample init scripts. Choose the one appropriate for your distro, put it in place, run 'chkconfig' or 'update-rc.d' or whatever's appropriate for your distro, and make sure you can start and stop Asterisk with that init script now.
For festival, I think on Debianesque distros you will have installed this from a package, but if you're on something Redhat-ish and you need an init script, the following will probably work.
30-59 9 * * 1-6 /usr/local/bin/eg-pbx-allocator.pl -c /usr/local/etc/eg-pbx-daemon.conf
-------------------------------------------------------
-So you see how those three cron lines togeter run the allocator every minute within Anytown's 930am - 630pm Mon-Sat call window.
+So you see how those three cron lines together run the allocator every minute within Anytown's 930am - 630pm Mon-Sat call window.
Cron job for action_trigger_runner.pl
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This may have implications for load scheduling. That might mean changes to the cron job on the Asterisk machine that runs eg-pbx-allocator.pl, or changes to the queue_limit value in +/usr/local/etc/eg-pbx-daemon.conf+, or other things. Telephony is an adventure.
-The target for a hold.available hook is a hold, unlike a checkout.due hook for which the target is a circ, so for your event_definition's environment, notice change 'circ_lib' to 'pickup_lib'. Then within your event_defintion's template, make the same substitution and any other reasonable changes in light of the fact that now target is an array of holds, whereas before it was an array of circs.
+The target for a hold.available hook is a hold, unlike a checkout.due hook for which the target is a circ, so for your event_definition's environment, notice change 'circ_lib' to 'pickup_lib'. Then within your event_definition's template, make the same substitution and any other reasonable changes in light of the fact that now target is an array of holds, whereas before it was an array of circs.
Troubleshooting and support
---------------------------
TODO: Explain how info from Account in a callfile winds up in CSV, and why it's good and helpful.
-- Activate one of the cdr modules that come with Asterisk. Call Detail Records wind up in either a CSV file or a database table depending on which module you activate. You can even have the cdr_pgsql.so module put that database table in the same postgres database as Evergreen itself uses. A cdr databse table will have one row per call made, with lots of information about what the phone number was and what happened with the call. This information will be less reliable if you're using analog hardware, but is better if you're using digital telephony (VoIP).
+- Activate one of the cdr modules that come with Asterisk. Call Detail Records wind up in either a CSV file or a database table depending on which module you activate. You can even have the cdr_pgsql.so module put that database table in the same postgres database as Evergreen itself uses. A cdr database table will have one row per call made, with lots of information about what the phone number was and what happened with the call. This information will be less reliable if you're using analog hardware, but is better if you're using digital telephony (VoIP).
- Check +/var/log/asterisk/full+. grep around in this file to learn how to find all kinds of good information.
- Run the interactive Asterisk console. On the asterisk server, as root, run */usr/sbin/asterisk -rvvvvvvvvvv* . Watch things happen in real time.
- Consult the Evergreen database to see what kinds of notices have been generated. The following is an example query to see if any telephone notices went out regarding Harry Potter (assuming you kept the titlestring part in your event definition template):
* Merge Overlay Profiles and Record Match Sets (see link:../cataloging/batch_importing_MARC.txt[Batch Importing MARC Records] in Cataloging)
* Providers
-Acquisitons Workflow
+Acquisitions Workflow
~~~~~~~~~~~~~~~~~~~~
The following diagram shows how the workflow functions in Evergreen. One of the differences in this process you should notice is that when creating a selection list on the vendor site, libraries will be downloading and importing the vendor bibs and item records.
^^^^^^^^^^^^^^^^^^^
This feature enables you to return to a specific line item on a selection list,
-purchase order, or invoice after you have naviagted away from the page that
+purchase order, or invoice after you have navigated away from the page that
contained the line item. This feature is especially useful when you must
identify a line item in a long list. After working with a line item, you can
return to your place in the search results or the list of line items.
By default, you must be logged into your OPAC account to send a text message from Evergreen. However, if you disable this setting, you can text message copy information without having
to login to your OPAC account.
-To disable the patron login requirmement:
+To disable the patron login requirement:
. Click *Admin* -> *Local Administration* -> *Library Settings Editor.*
. Select the setting, *Disable auth requirement for texting call numbers*.
~~~~~~~~
A thesaurus describes the semantic rules that govern the meaning of words in a
-MARC record. The thesaurus code, which indicates the specific thesarus that
+MARC record. The thesaurus code, which indicates the specific thesaurus that
should control a MARC record, is encoded in a fixed field using the mnemonic
Subj in the authority record. Eleven thesauri associated with the Library of
Congress control set exist by default in the staff client.
. Create the corresponding tag in the bibliographic record that should contain
this information. Click the *None* link in the *Controlled Bib Fields* column.
. Click *New Control Set Bib Field*.
-. Add the corresponding tag in the bibiographic record.
+. Add the corresponding tag in the bibliographic record.
. Click *Save*.
image::media/Authority_Control_Sets4.jpg[Authority_Control_Sets4]
You may also delete Resource Attribute Values, Resource Attributes and Resource Types. But you have to delete them in the reverse order when you create them to make sure the entry is not in use when you try to delete it.
-This is the deletion order: Resource Attribut Map/Resources --> Resource Attribute Values --> Resource Attributes --> Resource Types.
+This is the deletion order: Resource Attribute Map/Resources --> Resource Attribute Values --> Resource Attributes --> Resource Types.
enter a zero (0) in this field.
. Check the box adjacent to *Global Flag* if you want all of the org units in
your consortium to be restricted by this limit set when it is applied to a
-circulation policy. Otherwise, Evergreen will only appy the limit to the direct
+circulation policy. Otherwise, Evergreen will only apply the limit to the direct
ancestors and descendants of the owning library.
. Enter a brief *Description* of the circulation limit set.
. Click *Save*.
Statistical Categories Editor
-----------------------------
-This is where you configure your statistical categories (stat cats). Stat cats are a way to save and report on additional information that doesn’t fit elsewhere in Evergreen's default records. It is possible to have stat cats for copies or patrons.
+This is where you configure your statistical categories (stat cats). Stat cats are a way to save and report on additional information that doesn't fit elsewhere in Evergreen's default records. It is possible to have stat cats for copies or patrons.
1. Click *Admin -> Local Administration -> Statistical Categories Editor.*
Restrict Z39.50 Sources by Permission Group
-------------------------------------------
-In Evergreen versions preceeding 2.2, all users with cataloging privileges could view all of the Z39.50 servers that were available for use in the staff client. In Evergreen version 2.2, you can use a permission to restrict users' access to Z39.50 servers. You can apply a permission to the Z39.50 servers to restrict access to that server, and then assign that permission to users or groups so that they can access the restricted servers.
+In Evergreen versions preceding 2.2, all users with cataloging privileges could view all of the Z39.50 servers that were available for use in the staff client. In Evergreen version 2.2, you can use a permission to restrict users' access to Z39.50 servers. You can apply a permission to the Z39.50 servers to restrict access to that server, and then assign that permission to users or groups so that they can access the restricted servers.
Administrative Settings
~~~~~~~~~~~~~~~~~~~~~~~
indexterm:[staff client, standalone interface]
If your connection to Evergreen is lost, click _Standalone
-Interface_ tio circulate items or register patrons while connection is down.
+Interface_ to circulate items or register patrons while connection is down.
Logging Out
~~~~~~~~~~~
Clicking the *x* on the application window (not the login window) will not exit
Evergreen, but only close the window.
-A new application window can be opened by cicking _Open New Window_ from the
+A new application window can be opened by clicking _Open New Window_ from the
login window.
============
our `templates_BR1` skin.
To begin with, we need to find the page(s) that contain the text in question.
-The simplest way to do that is with the handly utility `ack`, which is much
+The simplest way to do that is with the handy utility `ack`, which is much
like `grep` but with built-in recursion and other tricks. On Debian-based
systems, the command is `ack-grep` as `ack` conflicts with an existing utility.
In the following example, we search for files that contain the text "Link 1":
Using this Feature
~~~~~~~~~~~~~~~~~~
-The last activty date for user logins appears in the patron's summary.
+The last activity date for user logins appears in the patron's summary.
image::media/User_Activity_Types2A.jpg[User_Activity_Types2A]
+
image::media/workstation_admin-3.png[select hotkeys]
+
-* *Default*: inlcuding all hotkeys
+* *Default*: including all hotkeys
* *Minimal*: including those hotkeys using CTRL key
* *None*: excluding all hotkeys
+
indexterm:[receipt template editor, checkout]
There are many default receipt templates included with the Evergreen staff
-client. These templates are saved on invidual workstations. Customization can be
+client. These templates are saved on individual workstations. Customization can be
done workstation by workstation or by exporting the templates to import to other
workstations.
See http://www.w3schools.com/html/ for more information on HTML tags.
You may insert a link to an image, e.g. your library's logo, that exists on the
-web. For example, to in
lcude the white Evergreen logo from this document, enter tag <img
+web. For example, to in
clude the white Evergreen logo from this document, enter tag <img
src=http://docs.evergreen-ils.org/2.3/media/small_logo_white.jpg>. in the
receipt template.
at a particular library (see <<library_settings_editor, Library Settings>> for details). A different default
group can be set up on individual workstations by the following steps.
-. Go to *Admin -> Workstation Adminitration -> Toolbars -> Current*.
+. Go to *Admin -> Workstation Administration -> Toolbars -> Current*.
+
image::media/workstation-button_bar-2.png[button bar 2]
+
administrators can create new groups for individual accounts, workstations or
all in a particular library.
-. Go to *Admin -> Workstation Adminitration -> Toolbars -> Configure Toolbars.
+. Go to *Admin -> Workstation Administration -> Toolbars -> Configure Toolbars.
. Click *New Toolbar*
+
image::media/workstation-button_bar-3.png[button bar 3]
add. You may select one in the Selected pane, and then click *`<--(R)`* to remove
it.
. Check one of the radio buttons: *Owning Org Unit*, *Owning Workstation*, or *Owning
-User* to specify the new group should be availalbe to everyone/workstation in
+User* to specify the new group should be available to everyone/workstation in
your library, or this workstation or yourself only.
. If you chose _Owning Workstation_ in the above step, click the down-pointed
arrow at the end of the _Permission Context_ box to select your library in the
-orgnization unit tree.
+organization unit tree.
. Click *Save Toolbar*.
. The new toolbar group will be displayed together with Circulation and
Cataloguing groups when you choose a toolbar group next time.
WHERE ppl.code IN ('UPDATE_MARC', 'CREATE_MARC', 'IMPORT_MARC');
------------------------------------------------------------------------------
-Similarly, we want to give the Student Circulators group the abillity to check
+Similarly, we want to give the Student Circulators group the ability to check
out copies and record in-house uses at the system level, so we assign the
COPY_CHECKOUT and CREATE_IN_HOUSE_USE permissions at depth 1 (overriding the
same _Staff_ permissions that were granted only at depth 2):
you will need to open the Apache configuration file _/etc/apache2/eg_vhost.conf_
and edit several lines:
-. Uncoment (remove the "#" at the beginning of the line) and add your chilifresh
+. Uncomment (remove the "#" at the beginning of the line) and add your ChiliFresh
account number:
----
#SetEnv OILS_CHILIFRESH_PROFILE
----
-Uncomment the line indicating the location of the Evergreen javaScript for
+Uncomment the line indicating the location of the Evergreen JavaScript for
ChiliFresh:
----
#SetEnv OILS_CHILIFRESH_URL http://chilifresh.com/on-site /js/evergreen.js
----
-. Uncomment the line indicating the secure URL for the Evergreen javaScript :
+. Uncomment the line indicating the secure URL for the Evergreen JavaScript :
----
#SetEnv OILS_CHILIFRESH_HTTPS_URL https://secure.chilifresh.com/on-site/js/evergreen.js
Google Analytics
~~~~~~~~~~~~~~~~
-Google Analytics is a free service to collect statisitics for your Evergreen
+Google Analytics is a free service to collect statistics for your Evergreen
site. In order to use Google Analytics you will first need to set up the
service from the Google Analytics website at http://www.google.com/analytics/.
To activate Google Analytics you will need to edit _config.tt2_ in your
An OpenURL resolver allows you to find electronic resources and pull them into
your catalog based on the ISBN or ISSN of the item. In order to use the SFX
-OpenURL resolver, you will need to subscribe to the Ex Libirs SFX service. To
+OpenURL resolver, you will need to subscribe to the Ex Libris SFX service. To
activate the service in Evergreen edit the _config.tt2_ file in your template.
Enable the resolver by changing the value of _openurl.enabled_ to _true_ and
-change the _openurl.baseurl_ setting to point to the URL of your openURL
+change the _openurl.baseurl_ setting to point to the URL of your OpenURL
resolver.
Syndetic Solutions
integer referencing the id field in permission.grp_tree. Setting this value will effect
the permissions for the user. See the values in permission.grp_tree for possibilities.
+
-ident_type is the identification type used for identiying users. This is a integer value
+ident_type is the identification type used for identifying users. This is a integer value
referencing config.identification_type and should match the id values of that table. The
default values are 1 for Drivers License, 2 for SSN or 3 for other.
+
WITH CSV HEADER;
-----------------------------------
+
-The script wil vary depending on the format of your patron load file (patrons.csv).
+The script will vary depending on the format of your patron load file (patrons.csv).
+
. Formatting of some fields to fit Evergreen filed formatting may be required. Here is an example
of sql to adjust phone numbers in the staging table to fit the evergreen field:
are used to track spending and purchases for specific collections. Some
libraries may choose to define very broad funds for their collections (e.g.
children's materials, adult materials) while others may choose to define more
-specific funds (e.g. adult non-fiction DVD's for BR1).
+specific funds (e.g. adult non-fiction DVDs for BR1).
If your library does not wish to track fund accounting, you can create one
large generic fund and use that fund for all of your purchases.
9) Select an *Insufficient Quality Fall-Through Profile* if desired. This
-field enables you to indicate that if the inbound record doees not meet the
+field enables you to indicate that if the inbound record does not meet the
configured quality standards, then you may still import the record using an
alternate merge profile. This field is typically used for selecting a merge
profile that allows the user to import holdings attached to a lower quality
Using the Conjoined Items Feature
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-The Conjoined Items feature was designed so that you can link items between bibliographic records when you have the item in hand, or when the item is not physically present. Both processes are described here. The steps are fewer if you have the item in hand, but both processes accomplish the same task. This documentalso demonstrates the process to edit or delete links between items and bibliographic records. Finally, the permission a cataloger needs to use this feature is listed.
+The Conjoined Items feature was designed so that you can link items between bibliographic records when you have the item in hand, or when the item is not physically present. Both processes are described here. The steps are fewer if you have the item in hand, but both processes accomplish the same task. This document also demonstrates the process to edit or delete links between items and bibliographic records. Finally, the permission a cataloger needs to use this feature is listed.
.Scenario 1: I want to link an item to another bibliographic record, but I do not have the item in hand
*Monograph Parts* enables you to differentiate between parts of monographs or other multi-part items. This feature enables catalogers to describe items more precisely by labeling the parts of an item. For example, catalogers might identify the parts of a monograph or the discs of a DVD set. This feature also allows patrons more flexibility when placing holds on multi-part items. A patron could place a hold on a specific disc of a DVD set if they want to access a specific season or episode rather than an entire series.
-Four new permissions are used by this functionality: CREATE_MONOGRAPH_PART, UPDATE_MONOGRAPH_PART, DELETE_MONOGRAPH_PART and MAP_MONOGRAPH_PART. Thes
-e permissions should be assigned at the consorial level to those groups or users that will make use of the features described below.
+Four new permissions are used by this functionality: CREATE_MONOGRAPH_PART, UPDATE_MONOGRAPH_PART, DELETE_MONOGRAPH_PART and MAP_MONOGRAPH_PART. These permissions should be assigned at the consortial level to those groups or users that will make use of the features described below.
Add a monograph part to an existing record
Pre-catalogued item circulation is not available on Offline Interface. If an
existing pre-cat barcode happens to be used, it is checked out with the
previous author and title. If a new pre-cat barcode is attempted, an error of
-`ASSET NOT FOUND` (item not found) isreturned upon processing offline
+`ASSET NOT FOUND` (item not found) is returned upon processing offline
transactions.
Renew
.REQUEST flow in a stateless connection
image:media/REQUEST.png[REQUEST flow in a stateless connection]
-When an OpenSRF client issues a `CONNECT` message to create a _stateful_ conection, the
+When an OpenSRF client issues a `CONNECT` message to create a _stateful_ connection, the
router returns the Jabber ID of the next available service to the client so
that the client can issue one or more `REQUEST` message directly to that
particular service and the service will return corresponding `RESULT` messages
* The `contextfield` attribute, if it exists, defines the field in this class
that identifies the library within the system for which the user must have
-prvileges to work. If a user has been granted a given permission, but has not been
+privileges to work. If a user has been granted a given permission, but has not been
granted privileges to work at a given library, they can not perform the action
at that library.
Let's explore the call to `__PACKAGE__->register_method()`; most of the elements
of the hash are optional, and for the sake of brevity we omitted them in the
previous example. As we have seen in the results of the <<opensrfIntrospection,introspection call>>, a
-verbose regisration method call is recommended to better enable the internal
+verbose registration method call is recommended to better enable the internal
documentation. So, for the sake of completeness here, is the set of elements
that you should pass to `__PACKAGE__->register_method()`:
If this does not work, it's time to do some troubleshooting.
- * As the *opensrf* Linux acccount, run the `settings-tester.pl` script to see
+ * As the *opensrf* Linux account, run the `settings-tester.pl` script to see
if it finds any system configuration problems. The script is found at
`Open-ILS/src/support-scripts/settings-tester.pl` in the Evergreen source
tree.
image::media/staff_client_installation_0.png[]
+
. Click _Next_ to accept
-desitnation folder.
+destination folder.
+
image::media/staff_client_installation_1.png[]
+
* Windows (XP, Vista, or 7), Mac OS X, or Linux operating system
* a reliable high speed Internet connection
* 512Mb of RAM
- * The staff client uses the TCP protocal on ports 80 and 443 to communicate with the Evergreen server.
+ * The staff client uses the TCP protocol on ports 80 and 443 to communicate with the Evergreen server.
*Barcode Scanners*
Configuration files allow you to define labels for canned searches in the icon
grid, determine how icons lead users to new pages, and define whether those icons
are canned searches or links to external resources. Documentation describing how
-to use the configruation files is available in the Evergreen respository.
+to use the configuration files is available in the Evergreen repository.
My Lists 2.2
------------
-The *My Lists* feature replaces the bookbag feature that was available in versions proior to 2.2. The *My Lists* feature is a part of the Template Toolkit OPAC that is available in version 2.2. This feature enables you to create temporary and permanent lists; create and edit notes for items in lists; place holds on items in lists; and share lists via RSS feeds and CSV files.
+The *My Lists* feature replaces the bookbag feature that was available in versions prior to 2.2. The *My Lists* feature is a part of the Template Toolkit OPAC that is available in version 2.2. This feature enables you to create temporary and permanent lists; create and edit notes for items in lists; place holds on items in lists; and share lists via RSS feeds and CSV files.
*Create New Lists*
image::media/cap-wiz-chron.jpg[Chronology]
. To add chronological units to the captions, check the box adjacent to Use chronology captions.
-. Choose a chronology for the first level. If you want to display the terms such as "year" and "month" next to the chronology caption in the catlaog, then check the box beneath Display in holding field.
+. Choose a chronology for the first level. If you want to display the terms such as "year" and "month" next to the chronology caption in the catalog, then check the box beneath Display in holding field.
. To include additional levels of chronology, click Add Chronology Caption. Each level that you add must be smaller than the previous level.
. After you have completed the chronology caption, click Next.
. Open the Subscriptions tab.
. Right-click or click Actions for Selected Row -> Make predictions.
-. A pop up box will aks you how many items you want to predict. Enter the number, and click OK.
+. A pop up box will ask you how many items you want to predict. Enter the number, and click OK.
. A confirmation message will appear. Click OK.
. Click the Issuances link to view the predicted issues.
[NOTE]
-A subscription may have multiple captions and patterns listed in the subscripiton details, but only one Caption and Pattern can be active at any time. If you want to add multiple patterns, e.g. for Basic and Supplement, Click Add Caption and Pattern.
+A subscription may have multiple captions and patterns listed in the subscription details, but only one Caption and Pattern can be active at any time. If you want to add multiple patterns, e.g. for Basic and Supplement, Click Add Caption and Pattern.
Use the Pattern Code Wizard
image::media/cap-wiz-chron.jpg[Chronology]
. To add chronological units to the captions, check the box adjacent to Use chronology captions.
-. Choose a chronology for the first level. If you want to display the terms, "year" and "month" next to the chronology caption in the catlaog, then check the box beneath Display in holding field.
+. Choose a chronology for the first level. If you want to display the terms, "year" and "month" next to the chronology caption in the catalog, then check the box beneath Display in holding field.
. To include additional levels of chronology, click Add Chronology Caption. Each level that you add must be smaller than the previous level.
. After you have completed the chronology caption, click Next.
Edit Subscriptions
------------------
-Subscriptions can be edite to change the caption and pattern and other information.
+Subscriptions can be edited to change the caption and pattern and other information.
Serials Control View
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-------------------------------------------------
In previous versions of Evergreen, issues of serials displayed in a list ordered by publication date. The list could be lengthy if the library had extensive holdings of a serial.
-Using the Template Toolkit OPAC that is available in version 2.2, you can group issues of serials in the OPAC by chronology or enumeration. For example, you might group issues by date published or by volume. Users can expand these hyperlinked groups to view holdings of specific issues. The result is a clean, easy-to-naviagte interface for viewing holdings of serials with a large quantity of issues.
+Using the Template Toolkit OPAC that is available in version 2.2, you can group issues of serials in the OPAC by chronology or enumeration. For example, you might group issues by date published or by volume. Users can expand these hyperlinked groups to view holdings of specific issues. The result is a clean, easy-to-navigate interface for viewing holdings of serials with a large quantity of issues.
NOTE: This feature is only available in the Template Toolkit OPAC.
System Generated Holdings Statement
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-As issues are received, Evergreen creates a holding statement in the OPAC based on what is set up in the Caption and Patterns of the subscription. The systems generated holdings can only be edited by changing caption and pattern information and there is no abilitiy to edit the statement as free text.
+As issues are received, Evergreen creates a holding statement in the OPAC based on what is set up in the Caption and Patterns of the subscription. The systems generated holdings can only be edited by changing caption and pattern information and there is no ability to edit the statement as free text.
MARC Format for Holdings Display (MFHD)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
projects / Evergreen.git / commitdiff