-= Receive Items From an Invoice 2.2\r
-\r
-This feature will be available in Evergreen version 2.2.\r
-\r
-*Abstract*\r
+Receive Items From an Invoice\r
+-----------------------------\r
\r
This feature enables users to receive items from an invoice. Staff can receive individual copies, or they can receive items in batch.\r
\r
-\r
-*Table of Contents*\r
-\r
-* Receive Items in Batch\r
-* Receive Specific Copies\r
-\r
-\r
-*Recieve Items in Batch (List Mode)*\r
+Recieve Items in Batch (List Mode)\r
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r
\r
In this example, we have created a purchase order, added line items and copies, and activated the purchase order. We will create an invoice from the purchase order, receive items, and invoice them. We will receive the items in batch from the invoice.\r
\r
\r
\r
\r
-*Recieve Specific Copies (Numeric Mode)*\r
+Recieve Specific Copies (Numeric Mode)\r
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r
\r
In this example, we have created a purchase order, added line items and copies, and activated the purchase order. We will create an invoice from the purchase order, receive items, and invoice them. We will receive specific copies from the invoice. This function may be useful to libraries who purchase items that have been barcoded by their vendor. \r
\r
\r
image::/esi/docs/wp-content/uploads/2011/11/Receive_Items_From_an_Invoice7.jpg[Receive_Items_From_an_Invoice7]\r
\r
-\r
-Copyright: 2011 Equinox Software. This work by Equinox Software, Inc. is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.\r
-\r
-Author: Sally Fortin, Equinox Software
\ No newline at end of file
-= Authority Control Sets 2.2\r
-\r
-This feature will be available in Evergreen version 2.2.\r
-\r
-*Abstract*\r
+Authority Control Sets\r
+----------------------\r
\r
The tags and subfields that display in authority records in Evergreen are proscribed by control sets. The Library of Congress control set is the default control set in Evergreen. In Evergreen release 2.2, you can create customized control sets for authority records. Also, you can define thesauri and authority fields for these control sets.\r
\r
Patrons and staff will be able to browse authorities in the OPAC. The following fields are browsable by default: author, series, subject, title, and topic. You will be able to add custom browse axes in addition to these default fields.\r
\r
-*Table of Contents*\r
-\r
-\r
-* Control Sets\r
-* Thesauri\r
-* Authority Fields\r
-* Browse Axes\r
-* OPAC Searching of Authorities\r
-* Permissions to use this Feature\r
-\r
-*Control Sets*\r
+Control Sets\r
+~~~~~~~~~~~~\r
\r
You can specify the MARC tags and subfields that an authority record should contain. The Library of Congress control set exists in the staff client by default. The control sets feature enables librarians to add or customize new control sets.\r
\r
To access existing control sets, click *Admin* -> *Server Administration* -> *Authorities* -> *Control Sets*.\r
\r
-\r
To add a *control set*:\r
\r
1) Click *Admin* -> *Server Administration* -> *Authorities* -> *Control Sets*.\r
image::/esi/docs/wp-content/uploads/2011/11/Authority_Control_Sets1.jpg[Authority_Control_Sets1]\r
\r
\r
-*Thesauri*\r
+Thesauri\r
+~~~~~~~~\r
\r
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 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. \r
\r
\r
\r
\r
-*Authority Fields*\r
-\r
+Authority Fields\r
+~~~~~~~~~~~~~~~~\r
\r
Authority fields indicate the tags and subfields that should be entered in the authority record. Authority fields also enable you to specify the type of data that should be entered in a tag. For example, in an authority record governed by a Library of Congress control set, the 100 tag would contain a "Heading - Personal Name." Authority fields also enable you to create the corresponding tag in the bibliographic record that would contain the same data. \r
\r
-==== To create an *Authority Field*:\r
+To create an *Authority Field*:\r
+\r
\r
1) Click *Admin* -> *Server Administration* -> *Authorities* -> *Control Sets*.\r
\r
image::/esi/docs/wp-content/uploads/2011/11/Authority_Control_Sets4.jpg[Authority_Control_Sets4]\r
\r
\r
-\r
*Browse Axes*\r
\r
Authority records can be browsed, by default, along five axes: author, series, subject, title, and topic. Use the *Browse Axes* feature to create additional axes.\r
\r
\r
-\r
Create a new *Browse Axis*:\r
\r
1) Click *Admin* -> *Server Administration* -> *Authorities* -> *Browse Axes*\r
* UPDATE_AUTHORITY_CONTROL_SET\r
* DELETE_AUTHORITY_CONTROL_SET\r
\r
-\r
-\r
-Copyright: 2011 Equinox Software. This work by Equinox Software, Inc. is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.\r
-\r
-Author: Sally Fortin, Equinox Software\r
-\r
-\r
-\r
-\r
-\r
-\r
-= Call Number Prefixes and Suffixes 2.1\r
+Call Number Prefixes and Suffixes\r
+---------------------------------\r
\r
-This feature will be available in Evergreen version 2.1.\r
+You can configure call number prefixes and suffixes in the Admin module. This feature ensures more precise cataloging because each cataloger will have access to an identical drop down menu of call number prefixes and suffixes that are used at his library. In addition, it may streamline cataloging workflow. Catalogers can use a drop down menu to enter call number prefixes and suffixes rather than entering them manually. You can also run reports on call number prefixes and suffixes that would facilitate collection development and maintenance.\r
\r
-*Abstract*\r
\r
-In Evergreen version 2.1, you can configure call number prefixes and suffixes in the Admin module. This feature ensures more precise cataloging because each cataloger will have access to an identical drop down menu of call number prefixes and suffixes that are used at his library. In addition, it may streamline cataloging workflow. Catalogers can use a drop down menu to enter call number prefixes and suffixes rather than entering them manually. You can also run reports on call number prefixes and suffixes that would facilitate collection development and maintenance.\r
-\r
-\r
-*Table of Contents*\r
-\r
-* Configure Call Number Prefixes\r
-* Configure Call Number Suffixes\r
-* Apply Call Number Prefixes and Suffixes\r
-\r
-\r
-*Configure call number prefixes*:\r
+Configure call number prefixes\r
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r
\r
Call number prefixes are codes that precede a call number.\r
\r
\r
\r
\r
-*Configure call number suffixes*:\r
+Configure call number suffixes\r
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r
\r
Call number suffixes are codes that succeed a call number.\r
\r
5. Click *Save*.\r
\r
\r
-\r
image::/esi/docs/wp-content/uploads/2011/11/Call_Number_Prefixes_and_Suffixes_2_21.jpg[Call_Number_Prefixes_and_Suffixes_2_22]\r
\r
\r
-*Apply Call Number Prefixes and Suffixes*\r
-\r
+Apply Call Number Prefixes and Suffixes\r
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r
\r
You can apply call number prefixes and suffixes to items from a pre-configured list in the *Unified Volume/Copy Creator*. See the document, Unified Volume/Copy Creator, for an example.\r
-\r
-\r
-\r
-Copyright: 2011 Equinox Software. This work by Equinox Software, Inc. is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.\r
-\r
-Author: Sally Fortin, Equinox Software\r
-= Recent Staff Searches 2.2\r
-\r
-This feature is available in Evergreen version 2.2.\r
-\r
-*Abstract*\r
+Recent Staff Searches\r
+---------------------\r
\r
This feature enables you to view your recent searches as you perform them in the staff client. The number of searches that you can view is configurable. This feature is only available through the staff client; it is not available to patrons in the OPAC. \r
\r
-*Table of Contents*\r
-\r
-* Administrative Settings\r
-* View Recent Staff Searches\r
-\r
-\r
*Administrative Settings*\r
\r
By default, ten searches will be saved as you search the staff client. If you want to change the number of saved searches, then you can configure the number of searches that you wish to save through the *Library Settings Editor* in the *Admin* module.\r
2. Your search results for the current search will appear in the middle of the screen. The most recent searches will appear on the left side of the screen.\r
\r
image::/esi/docs/wp-content/uploads/2011/11/Saved_Catalog_Searches_2_22.jpg[Saved_Catalog_Searches_2_22]\r
-\r
-\r
-Copyright: 2011 Equinox Software. This work by Equinox Software, Inc. is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.\r
-\r
-Author: Sally Fortin, Equinox Software\r
-\r
-= Restrict Z39.50 Sources by Permission Group 2.2\r
-\r
-\r
-This functionality will be available in Evergreen version 2.2.\r
-\r
-*Abstract*\r
+Restrict Z39.50 Sources by Permission Group\r
+-------------------------------------------\r
\r
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.\r
\r
-\r
-*Table of Contents*\r
-\r
-* Administrative Settings\r
-* Restrict Z39.50 Sources by Permission Group\r
-\r
-\r
-*Administrative Settings*\r
+Administrative Settings\r
+~~~~~~~~~~~~~~~~~~~~~~~\r
\r
You can add a permission to limit use of Z39.50 servers, or you can use an existing permission.\r
\r
\r
\r
\r
-*Restrict Z39.50 Sources by Permission Group*\r
-\r
+Restrict Z39.50 Sources by Permission Group\r
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r
\r
1) Click *Admin -> Server Administration -> Z39.50 Servers*\r
\r
\r
6) Users that log in to the staff client and have that permission will be able to see the restricted Z39.50 server. \r
\r
-\r
NOTE: As an alternative to creating a new permission to restrict use, you can use a preexisting permission. For example, your library uses a permission group called SuperCat, and only members in this group should have access to a restricted Z39.50 source. Identify a permission that is unique to the SuperCat group (e.g. CREATE_MARC) and apply that permission to the restricted Z39.50 server. Because these users are in the only group with the permission, they will be the only group w/ access to the restricted server.\r
-\r
-\r
-Copyright: 2011 Equinox Software. This work by Equinox Software, Inc. is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.\r
-\r
-Author: Sally Fortin, Equinox Software\r
-= Batch Importing MARC Records 2.2\r
+Batch Importing MARC Records 2.2\r
+--------------------------------\r
\r
This feature will be available in Evergreen version 2.2.\r
\r
-=== *Abstract*\r
+*Abstract*\r
+~~~~~~~~~~\r
\r
The cataloging module in version 2.2 includes an enhanced MARC Batch Import interface. This interface features improved matching of records and managing of your import queue. In 2.2, you will be able to specify match points between incoming and existing records. You will also be able to apply filters to your queue that enable you to generate any errors that may have occurred during import. You will also be able to print your queue, email your queue, or export your queue as a CSV file. \r
\r
-\r
-=== *Table of Contents*\r
-\r
-* Permissions\r
-* Record Display Attributes\r
-* Record Match Sets\r
-* Replace Mode\r
-* Quality Metrics\r
-* Import Records\r
-\r
-=== *Permissions*\r
+*Permissions*\r
+~~~~~~~~~~~~~\r
\r
To use match sets to import records, you will need the following permission:\r
\r
ADMIN_IMPORT_MATCH_SET\r
\r
\r
-=== *Record Display Attributes*\r
+*Record Display Attributes*\r
+~~~~~~~~~~~~~~~~~~~~~~~~~~~\r
\r
This feature enables you to specify the tags and subfields that will display in records that appear in the import queue. \r
\r
\r
-=== *Record Match Sets*\r
+*Record Match Sets*\r
+^^^^^^^^^^^^^^^^^^^\r
\r
This feature enables you to create custom match points that you can use to accurately match incoming records with existing catalog records. \r
\r
\r
image::/esi/docs/wp-content/uploads/2011/11/Batch_Importing_MARC_Records14.jpg[Batch_Importing_MARC_Records14] \r
\r
-\r
-\r
-\r
-Copyright: 2011 Equinox Software. This work by Equinox Software, Inc. is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.\r
-\r
-Author: Sally Fortin, Equinox Software
\ No newline at end of file
-= Conjoined Items
-===============
+Conjoined Items
+---------------
-== Abstract
+Abstract
+~~~~~~~~
Prior to Evergreen version 2.1, items could be attached to only one bibliographic record. The Conjoined Items feature in Evergreen 2.1 enables catalogers to link items to multiple bibliographic records. This feature will enable more precise cataloging. For example, catalogers will be able to indicate items that are printed back to back, are bilingual, are part of a bound volume, are part of a set, or are available as an e-reader pre-load. This feature will also help the user retrieve more relevant search results. For example, a librarian catalogs a multi-volume festschrift. She can create a bibliographic record for the festschrift and a record for each volume. She can link the items on each volume to the festschrift record so that a patron could search for a volume or the festschrift and retrieve information about both works.
In the example below, a librarian has created a bibliographic record for two bestselling items. These books are available as physical copies in the library, and they are available as e-reader downloads. The librarian will link the copy of the Kindle to the bibliographic records that are available on the e-reader.
-=== Using the Conjoined Items Feature
+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.
UPDATE_COPY - Link items to bibliographic records
-
-Copyright: 2011 Equinox Software. This work by Equinox Software, Inc. is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
-
-Author: Sally Fortin, Equinox Software
-= *Monograph Parts 2.1*\r
+*Monograph Parts*\r
+-----------------\r
\r
This feature will be available in Evergreen version 2.1.\r
\r
*Abstract*\r
+----------\r
\r
*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.\r
\r
e permissions should be assigned at the consorial level to those groups or users that will make use of the features described below.\r
\r
\r
-\r
-*Table of Contents*\r
-\r
-* Add a monograph part to an existing record\r
-\r
+Add a monograph part to an existing record\r
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r
\r
To add a monograph part to an existing record in the catalog: \r
\r
\r
image::/esi/docs/wp-content/uploads/2011/11/monograph_parts5.jpg[monograph_parts5]\r
\r
-\r
-Copyright: 2011 Equinox Software. This work by Equinox Software, Inc. is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.\r
-\r
-Author: Sally Fortin, Equinox Software\r
-= Overlay Existing Catalog Record via Z39.50 Import 2.2\r
-\r
-This feature will be available in Evergreen version 2.2.\r
+Overlay Existing Catalog Record via Z39.50 Import\r
+-------------------------------------------------\r
\r
*Abstract*\r
+~~~~~~~~~~\r
\r
This feature enables you to replace a catalog record with a record obtained through a Z39.50 search. No new permissions or administrative settings are needed to use this feature.\r
\r
*To Overlay an Existing Record via Z39.50 Import:*\r
-\r
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\r
\r
1) Click *Cataloging -> Import Record from Z39.50*\r
\r
15) The screen will refresh in the OPAC View to show that the record has been overlaid.\r
\r
\r
-\r
image::/esi/docs/wp-content/uploads/2011/11/Overlay_Existing_Record_via_Z39.50_Import6.jpg[Overlay_Existing_Record_via_Z39.50_Import6]\r
-\r
-\r
-Copyright: 2011 Equinox Software. This work by Equinox Software, Inc. is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.\r
-\r
-Author: Sally Fortin, Equinox Software\r
-\r
-\r
-\r
Creating the database on a remote server
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
In a production instance of Evergreen, your PostgreSQL server should be
installed on a dedicated server. For PostgreSQL 9.1 and later you should be
able to continue to use the --create-database flag on eg_db_config.pl, without
* 512Mb of RAM
* The staff client uses the TCP protocal on ports 80 and 443 to communicate with the Evergreen server.
-Barcode Scanners
-^^^^^^^^^^^^^^^^
+*Barcode Scanners*
Evergreen will work with virtually any barcode scanner – if it worked with your legacy system it should work on Evergreen.
-Printers
-^^^^^^^^
+*Printers*
Evergreen can use any printer configured for your terminal to print receipts, check-out slips, holds lists, etc. The single exception is spine label printing,
which is still under development. Evergreen currently formats spine labels for output to a label roll printer. If you do not have a roll printer manual formatting may be required.
New features\r
~~~~~~~~~~~~\r
\r
-Cataloging\r
-^^^^^^^^^^\r
+*Cataloging*\r
+\r
+*Prevent bibliographic records from having attached copies*\r
\r
-Prevent bibliographic records from having attached copies\r
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++\r
To enable libraries to designate specific sets of records as only for use\r
as electronic resources, it is possible to configure a bibliographic source\r
such that physical copies or MFHD records may not be attached to records\r
a cataloger from adding volumes or MFHD records to records belonging to that\r
source.\r
\r
-Switch copy location name and library short name in copy editor\r
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\r
+*Switch copy location name and library short name in copy editor*\r
+\r
By default, the copy editor shows the library shortname ('BR1' or 'CONS')\r
followed by the copy location name ('Stacks', 'Reference'). A new workstation\r
setting, under *Admin -> Workstation Administration -> Copy Editor: Copy\r
locations at the consortial level and want to enable quick keyboard navigation\r
to copy locations by typing just the first letters of the copy location.\r
\r
-Reports\r
-^^^^^^^\r
+*Reports*\r
+\r
+\r
+*New views for reporting sources*\r
\r
-New views for reporting sources\r
-+++++++++++++++++++++++++++++++\r
To support the creation of collection development reports, the following\r
reporting sources have been added:\r
\r
\r
// Follow structure from staff client system admin menu.\r
\r
+include::admin/authority_control_sets.txt[]\r
+\r
+include::admin/cn_prefixes_and_suffixes.txt[]\r
+\r
+include::admin/restrict_Z39.50_sources_by_perm_group.txt[]\r
+\r
+\r
\r
Local Administration\r
====================\r
// Follow structure from staff client local admin menu.\r
\r
\r
+include::admin/recent_staff_searches.txt[]\r
+\r
Acquisitions\r
===========\r
\r
\r
This part is intended for staff who are involved in managing and processing acquisitions. \r
\r
+include::acquisitions/receive_items_from_invoice.txt[]\r
+\r
Cataloging\r
==========\r
\r
projects / Evergreen-DocBook.git / commitdiff