* xref:cataloging:introduction.adoc[Cataloging]
-** xref:cataloging:marc_tag_table.adoc[]
-** xref:cataloging:copy-buckets_web_client.adoc[]
-** xref:cataloging:item_tags_cataloging.adoc[]
-** xref:cataloging:MARC_Editor.adoc[]
-** xref:cataloging:record_buckets.adoc[]
-** xref:cataloging:merge_overlay_bibs.adoc[]
-** xref:cataloging:physical_char_wizard.adoc[]
-** xref:admin:staff_client-return_to_results_from_marc.adoc[]
-** xref:cataloging:batch_importing_MARC.adoc[]
-** xref:cataloging:overlay_record_3950_import.adoc[]
-** xref:cataloging:z39.50_search_enhancements.adoc[]
-** xref:cataloging:monograph_parts.adoc[]
-** xref:cataloging:conjoined_items.adoc[]
-** xref:cataloging:cataloging_electronic_resources.adoc[]
-** xref:cataloging:item_status.adoc[Item Status]
-** xref:cataloging:volcopy_editor.adoc[]
-** xref:cataloging:tpac_copy_edit_links.adoc[]
-** xref:cataloging:holdings_editor_hide_fields.adoc[]
+** xref:cataloging:copy-buckets_web_client.adoc[Item Buckets]
+** xref:cataloging:item_tags_cataloging.adoc[Item Tags]
+** xref:cataloging:MARC_Editor.adoc[Working with the MARC Editor]
+** xref:cataloging:record_buckets.adoc[Record Buckets]
+** xref:cataloging:physical_char_wizard.adoc[MARC 007 Field Physical
+Characteristics Wizard]
+** xref:admin:staff_client-return_to_results_from_marc.adoc[Return to Search
+Results from MARC Record]
+** xref:cataloging:batch_importing_MARC.adoc[Batch Importing MARC Records]
+** xref:cataloging:overlay_record_3950_import.adoc[Overlay Existing Catalog
+Record via Z39.50 Import]
+** xref:cataloging:z39.50_search_enhancements.adoc[Z39.50 Search Enhancements]
+** xref:cataloging:monograph_parts.adoc[Monograph Parts]
+** xref:cataloging:conjoined_items.adoc[Conjoined Items]
+** xref:cataloging:cataloging_electronic_resources.adoc[Cataloging Electronic
+Resources — Finding Them in Catalog Searches]
+** xref:cataloging:item_status.adoc[Using the Item Status interface]
+** xref:cataloging:volcopy_editor.adoc[Using the Holdings Editor]
** xref:cataloging:MARC_batch_edit.adoc[MARC Batch Edit]
-** xref:cataloging:authorities.adoc[Authority Control]
+** xref:cataloging:authorities.adoc[Managing Authorities]
** xref:cataloging:link_checker.adoc[Link Checker]
-** xref:admin:schema_bibliographic.adoc[]
-** xref:admin:marc_templates.adoc[]
+** xref:admin:schema_bibliographic.adoc[Notes about the Bibliographic Schema in
+the Database]
+** xref:admin:marc_templates.adoc[MARC Templates]
-== Working with the MARC Editor ==
+= Working with the MARC Editor =
+:toc:
Editing MARC Records
~~~~~~~~~~~~~~~~~~~~
. When finished, click _Save_. The record will remain open in the editor. You can close the browser window or browser tab. Or you can switch to
another view from the navigation near the top (for example to view it as it appears in the OPAC choose _OPAC View_).
-==== MARC Record Leader and MARC fixed field 008 ====
+=== MARC Record Leader and MARC fixed field 008 ===
You can edit parts of the leader and the 008 field in the MARC Editor via the fixed field editor box displayed above
the MARC record.
-===== To edit the MARC record leader =====
+==== To edit the MARC record leader ====
. Retrieve and display the appropriate record in _MARC Edit_ view.
OPAC icons for text, moving pictures and sound rely on correct MARC coding in the leader, 007, and 008, as do OPAC
search filters such as publication date, item type, or target audience.
-===== MARC Fixed Field Editor Right-Click Context Menu Options =====
+==== MARC Fixed Field Editor Right-Click Context Menu Options ====
The MARC Fixed Field Editor provides suggested values for select fixed fields based on the record type being edited. Users can right-click on the value control for a fixed field and choose the appropriate value from the menu options.
The Evergreen database contains information from the Library of Congress’s MARC 21 format standards that includes possible values for select fixed fields. The right-click context menu options are available for fixed fields whose values are already stored in the database. Fixed fields that do not contain possible values in the database, the user will receive the default web browser menu (such as cut, copy, paste, etc.).
. *config.coded_value_map* defines the set of valid values for many of the fixed fields and the translatable, human-friendly labels for them.
. *config.record_attr_definition* links together the information from the config.marc21_ff_pos_map and config.coded_value_map tables.
-==== Deleting MARC Records ====
+=== Deleting MARC Records ===
You can delete MARC records using the MARC Editor.
-===== To Delete a MARC record =====
+==== To Delete a MARC record ====
. Retrieve and display the appropriate record in the MARC editor.
. Click on the _MARC Edit_ tab.
. In the modal window, click the *OK/Continue* button to remove the MARC record.
image::media/marc_delete_record_3_3.png[The Delete button is located in the Marc Edit tab]
+
+=== MARC Tag-table Service ===
+The tag tables for the web staff client MARC editor are
+stored in the database. The tag-table
+service has the following features:
+
+- specifies whether (sub)fields are optional or mandatory
+- specifies whether (sub)fields are repeatable or not
+- a coded value map can be associated with a subfield to
+ establish a controlled vocabulary for that subfield
+- MARC field and subfield definitions can be overridden
+ by institutions further down in the organizational unit
+ hierarchy. This allows, for example, a library to specify
+ definitions for local MARC tags.
+- values supplied by the tag-table service are used to
+ populate values in context menus in the web staff client
+ MARC editor.
+
+MARC Tag Tables can be found under Administration -> Server Administration -> MARC Tag Tables.
+
+MARC Tag Tables Grid:
+
+image::media/MARC_Tag_Tables_Grid.PNG[Grid view of MARC Tag Tables]
+
+MARC Tag Tables Detail:
+
+image::media/MARC_Tag_Tables_Detail.PNG[Detail view of MARC Tag Tables]
+
+The initial seed data for the in-database tag table is
+derived from the current tooltips XML file.
+
-== MARC Batch Edit ==
+= MARC Batch Edit =
+:toc:
-=== Introduction ===
+== Introduction ==
This function is used to batch edit MARC records either adding a field, removing a field or changing the contents of a field.
**************************************
-=== Setting Up a Batch Edit Session ===
+== Setting Up a Batch Edit Session ==
Record Source::
This includes options to batch edit identifying MARC records in a record bucket, CSV file or by record id.
Go! (button)::
This button runs the action defined by the rule template(s).
-==== Action (Rule Type) ====
+=== Action (Rule Type) ===
Replace::
Replaces the value in a MARC field for a batch of records.
Delete::
Add::
Use this to add a field and its contents to a batch of records.
-==== Other Template Fields ====
+=== Other Template Fields ===
MARC Tag::
This is used to identify the field for adding, replacing, or deleting.
Subfield (optional)::
MARC Data::
Use this to indicate the data to add or used in replacing the existing data.
-==== Advanced Matching Restrictions (Optional) ====
+=== Advanced Matching Restrictions (Optional) ===
Subfield
Regular Expression::
Using PERL syntax for a regular expression to identify the data to be removed or replaced.
. Click *Go!*
. Results page will display indicating the number of records successfully edited
-=== Examples ===
+== Examples ==
-==== Adding a new field to all records ====
+=== Adding a new field to all records ===
. In the _action_ menu, choose _Add_.
. In _MARC Tag_, type the MARC tag number.
. Leave the _Subfields_ field blank.
. In _MARC Data_, type the field you would like to add.
-==== Delete a field if it contains a particular string ====
+=== Delete a field if it contains a particular string ===
. In the _action_ menu, choose _Delete_.
. In _MARC Tag_, type the MARC tag number.
-== Managing Authorities ==
+= Managing Authorities =
+:toc:
-=== Introduction ===
+== Introduction ==
This section describes how you can create, import, view, modify, merge, and delete authority records in Evergreen.
-=== Creating Authorities ===
+== Creating Authorities ==
Currently in Evergreen to create a new authority record, as opposed to importing an authority record, you
need to have a bib record open in the bib MARC editor.
[[importing_authority_records_from_the_staff_client]]
-=== Importing Authorities ===
+== Importing Authorities ==
. Click *Cataloging -> MARC Batch Import/Export.*
. You may create a queue to better track this import project. If you do not create a new queue, it will automatically put your records into a default queue named *-*.
. Don't set a value for Holdings Import Profile, because this doesn't apply to authority records.
=================
-==== Setting up Authority Record Match Sets ====
+=== Setting up Authority Record Match Sets ===
. Click *Cataloging -> MARC Batch Import/Export.*
. Click *Record Match Sets.*
. If you have sufficient privileges, you will be able to click on the *New Match Set*. If you are unable to do so, check that you have the ADMIN_IMPORT_MATCH_SET permission.
Evergreen's internal identifier is in the 901c field. If you have previously exported authority record -- perhaps for an external vendor to do authority cleanup work -- and you want to import them back into your catalog, you may wish to include the 901c field in your match set.
=================
-=== Viewing and Editing Authority Records by Database ID ===
+== Viewing and Editing Authority Records by Database ID ==
The authority record retriever allows catalogers to retrieve a specific
authority record using its database ID. Catalogers can
. View or edit the authority record as needed.
-=== Manage Authorities Interface ===
+== Manage Authorities Interface ==
In Evergreen to view, edit, merge, and delete authority records you would use the *Manage Authorities* interface
through the *Cataloging* menu.
-==== Searching for authorities ====
+=== Searching for authorities ===
To search for authorities in your system, first select the *Cataloging* menu and then select *Manage Authorities*.
Then proceed to fill out the search form.
* | = No attempt to code
-===== Editing authority records =====
+==== Editing authority records ====
Editing an authority record (or merging two authority records) can cause its linked bibliographic records to also update. For example,
if you correct a spelling error in the 150 field of a subject authority record, the relevant 650 field in linked bibliographic records
-== Batch Importing MARC Records ==
+= Batch Importing MARC Records =
+:toc:
-=== Introduction ===
+== Introduction ==
indexterm:[MARC records,importing,using the staff client]
you can apply filters that enable you to generate any errors that may have
occurred during import. You can print, email or export your queue as a CSV file.
-=== Permissions ===
+== Permissions ==
To use match sets to import records, you will need the following permission:
ADMIN_IMPORT_MATCH_SET
-=== Record Display Attributes ===
+== Record Display Attributes ==
This feature enables you to specify the tags and subfields that will display in
records that appear in the import queue.
[[matchsets]]
-=== Record Match Sets ===
+== Record Match Sets ==
This feature enables you to create custom match points that you can use to
accurately match incoming records with existing catalog records.
-==== Creating a Match Set ====
+=== Creating a Match Set ===
In this example, to demonstrate matching on record attributes and MARC tags and
subfields, we will create a record match set that defines a match based on the
+
image::media/Batch_Importing_MARC_Records7.jpg[Batch_Importing_MARC_Records7]
-==== Replace Mode ====
+=== Replace Mode ===
Replace Mode enables you to replace an existing part of the expression tree
with a new record attribute, MARC tag, or Boolean operator. For example, if
. Click *Exit Replace Mode*.
-==== Quality Metrics ====
+=== Quality Metrics ===
. Set the *Quality Metrics for this Match Set*. Quality metrics are used to
determine the overall quality of a record. Each metric is given a weight and
+
image::media/Batch_Importing_MARC_Records8.jpg[Batch_Importing_MARC_Records8]
-=== Merge/Overlay Profiles ===
+== Merge/Overlay Profiles ==
If Evergreen finds a match for an incoming record in the database, you need to identify which fields should be replaced, which should be preserved, and which should be added to the record.
Click the Merge/Overlay Profiles button to create a profile that contains this information.
You can add multiple tags to the specification options, separating each tag with a comma.
-=== Import Item Attributes ===
+== Import Item Attributes ==
If you are importing items with your records, you will need to map the data in
your holdings tag to fields in the item record. Click the *Holdings Import
Profile* button to map this information.
|=============================
-=== Import Records ===
+== Import Records ==
The *Import Records* interface incorporates record match sets, quality metrics,
more merging options, and improved ways to manage your queue. In this example,
-== Cataloging Electronic Resources -- Finding Them in Catalog Searches ==
+= Cataloging Electronic Resources -- Finding Them in Catalog Searches =
+:toc:
There are two ways to make electronic resources visible in the catalog without
adding items to the record:
shelving location(s). In contrast, transcendent electronic resources will appear in
results limited to any shelving location.
-=== Adding a Located URI to the Record ===
+== Adding a Located URI to the Record ==
A Located URI allows you to add the short name for the owning library to the 856
field to indicate which organizational units should be able to find the
resource. The owning organizational unit can be a branch, system, or consortium.
When troubleshooting located URIs, check to make sure there are no spaces either
before or after the organizational unit short name.
-==== Located URI Example 1 ====
+=== Located URI Example 1 ===
The _When enabled, Located URIs will provide visibility behavior identical to
copies_ flag is set to False (default behavior)
belonging to the search library (if it is an exact match, not a child) will sort
to the top.
-==== Located URI Example 2 ====
+=== Located URI Example 2 ===
The _When enabled, Located URIs will provide visibility behavior identical to
copies_ flag is set to True
belonging to the search library (if it is an exact match, not a child) will sort
to the top.
-=== Using Transcendant Bib Sources for Electronic Resources ===
+== Using Transcendant Bib Sources for Electronic Resources ==
Connecting a bib record to a transcendent bib source will make the record
visible in search results regardless of the user's search scope.
-== Conjoined Items ==
+= Conjoined Items =
+:toc:
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 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.
-== Item Buckets ==
+= Item Buckets =
+:toc:
Item buckets are containers copy records can be put into to easily perform batch actions on. Copies stay in buckets until they are removed.
NOTE: The words _copy_ and _item_ are used interchangeably in Evergreen.
-=== Managing Item Buckets ===
+== Managing Item Buckets ==
-==== Creating Item Buckets ====
+=== Creating Item Buckets ===
Item buckets can be created in the _Item Bucket_ interface as well as on the fly when adding items to a bucket from
a catalogue search or from within the _Item Status_ interface. For information on creating buckets on the fly see _Adding Copies to a Bucket_ (needs section ID).
NOTE: The functionality for making buckets publicly visible does not appear to be in place at this time.
-==== Editing Item Buckets ====
+=== Editing Item Buckets ===
1. In the _Item Bucket_ interface click *Buckets* in either the _Pending Copies_ or _Bucket View_ tab.
+
NOTE: The functionality for making buckets publicly visible does not appear to be in place at this time.
-==== Sharing Item Buckets ====
+=== Sharing Item Buckets ===
-===== Finding the Bucket ID =====
+==== Finding the Bucket ID ====
1. With the bucket open, look at the URL for the bucket ID. Share this ID with the staff member who needs access to this bucket.
image::media/copy-bucket-share-1.png[Bucket ID URL]
-===== Opening a Shared Bucket =====
+==== Opening a Shared Bucket ====
. In the _Item Bucket_ interface click *Buckets* in either the _Pending Copies_ or _Bucket View_ tab.
+
+
image::media/copy-bucket-share-4.png[Item Bucket Interface]
-==== Deleting Item Buckets ====
+=== Deleting Item Buckets ===
1. In the _Item Bucket_ interface click *Buckets* in either the _Pending Copies_ or _Bucket View_ tab.
+
6. Refresh your screen.
-=== Adding Copies to a Bucket ===
+== Adding Copies to a Bucket ==
-==== From the Item Bucket Interface ====
+=== From the Item Bucket Interface ===
1. In the _Item Bucket_ interface click on the *Pending Copies* tab.
+
NOTE: Once you have added your selected items to a bucket you can deselect them, select other items on your pending list, and add those items to a different bucket.
-==== From a Catalogue Search ====
+=== From a Catalogue Search ===
1. Retrieve the title through a catalogue search.
2. If it is not your default view click on the *Holdings View* tab.
8. Repeat steps 1 through 7 to add additional items.
-==== From the Scan Item Interface ====
+=== From the Scan Item Interface ===
. Click on _Search_ -> _Search for Copies by Barcode_
. Scan the barcode(s) of the item(s) you wish to add to the bucket.
. Choose the existing bucket that you'd like to add to, or create a new bucket.
-=== Removing Copies from a Bucket ===
+== Removing Copies from a Bucket ==
. Open the _Item Bucket_ interface. By default you are on the *Bucket View* tab.
+
+
. Your bucket will reload and the selected item(s) will no longer be in the bucket.
-=== Editing Copies in a Bucket ===
+== Editing Copies in a Bucket ==
. Open the _Item Bucket_ interface. By default you are on the *Bucket View* tab.
+
+
image::media/copy-bucket-edit-copy-3.png[Item Bucket Interface]
-=== Deleting Copies from the Catalogue ===
+== Deleting Copies from the Catalogue ==
. Open the _Item Bucket_ interface. By default you are on the *Bucket View* tab.
+
. The items have been deleted from the catalogue.
-=== Placing Holds on Copies in a Bucket ===
+== Placing Holds on Copies in a Bucket ==
. Open the _Item Bucket_ interface. By default you are on the *Bucket View* tab.
+
. The hold has been placed.
-=== Transferring Copies to Volumes ===
+== Transferring Copies to Volumes ==
1. Retrieve the title through a catalogue search.
2. If it is not your default view click on the *Holdings View* tab.
+++ /dev/null
-=== Hiding Fields in the Holdings Editor ===
-
-
-A user may hide specific fields in the holdings editor if these fields are not used for cataloging in their organization. Hiding fields that are not used by your organization helps to reduce confusion among staff and also declutters the holdings editor screen.
-
-To hide one or more fields from the holdings editor:
-
-. Retrieve the record.
-+
-[NOTE]
-===================================================================================
-You can retrieve records in many ways, including:
-
-* If you know its database ID, enter it into Cataloging > Retrieve Bib Record by ID.
-
-* If you know its control number, enter it into Cataloging > Retrieve Bib Record by TCN.
-
-* Searching in the catalog.
-
-* Clicking on a link from the Acquisitions or Serials modules.
-===================================================================================
-+
-. Select the *Add Holdings* button. The *Holdings Editor* will display.
-
-. In the Holdings Editor, select the *Defaults* tab.
-+
-image::media/Holdings_Editor_Defaults_Tab.png[Holdings editor defaults tab]
-+
-. On the Defaults tab, uncheck the boxes for the field(s) that you wish to hide. It is not necessary to save this screen; changes are saved automatically.
-+
-image::media/Holdings_Editor_Hide_Display_Defaults.png[Holdings editor display defaults with deselected fields]
-+
-. Select the *Edit* tab; the de-selected fields no longer appear on the holdings editor.
-== Working with holdings templates ==
+= Working with holdings templates =
+:toc:
Setting up holdings templates can save a lot of time when creating items, and they
also improve consistency and accuracy. Any time you find yourself creating multiple
items with the same item-level data, you may wish to create a holdings template
to automate that process.
-=== Creating a new holdings template ===
+== Creating a new holdings template ==
* Open _Administration_ -> _Local Administration_ -> _Holdings Template Editor_.
* Select the desired template attributes by moving through the fields in the
of the screen.
* Press the _Save_ button.
-=== Using a holdings template ===
+== Using a holdings template ==
Whenever you see the holdings editor, you can use data from your templates.
-== Introduction ==
+= Introduction =
+:toc:
This part describes cataloging in Evergreen.
-== Using the Item Status interface ==
+= Using the Item Status interface =
+:toc:
indexterm:[copies]
indexterm:[items]
The Item Status interface is a powerful tool that can give you a lot of information
about specific items in your catalog.
-=== Accessing the Item Status interface ===
+== Accessing the Item Status interface ==
There are three ways to access the item status interface:
-==== Through the Search menu ====
+=== Through the Search menu ===
. Click *Search -> Search for Copies by Barcode*.
. Scan your barcode.
-==== Through the Circulation menu ====
+=== Through the Circulation menu ===
. Click *Circulation -> Item Status*.
. Scan your barcode.
-==== From the OPAC view ====
+=== From the OPAC view ===
. Click *Search -> Search the Catalog*.
. Find a bibliographic record that you are interested in.
in.
-=== Specific fields ===
+== Specific fields ==
-==== Active date ====
+=== Active date ===
indexterm:[active date]
indexterm:[copies,activating]
indexterm:[items,activating]
are typically considered active, and statuses like _In process_ or
_On order_ are typically not.
-=== Printing spine labels ===
+== Printing spine labels ==
indexterm:[spine labels]
indexterm:[printing, spine labels]
Before printing spine labels, you will want to install Hatch
or turn off print headers and footers in your browser.
-include::../../admin/partials/turn-off-print-headers-firefox.adoc[]
+include::admin:partial$turn-off-print-headers-firefox.adoc[]
-include::../../admin/partials/turn-off-print-headers-chrome.adoc[]
+include::admin:partial$turn-off-print-headers-chrome.adoc[]
-==== Creating spine labels ====
+=== Creating spine labels ===
To create spine and item labels for an item (or group of items):
. Take a look at the Label Preview area.
. When you are satisfied with your labels, click the _Print_ button.
-=== Request Items Action ===
+== Request Items Action ==
To place requests from the Item Status interface, select one or more items in List View and select *Actions -> Request Items*. This action can also be invoked for a single item from Item Status Detail View.
-== Item Tags ==
+= Item Tags =
+:toc:
indexterm:[copy tags]
image::media/copytags7.PNG[Item Tags in the OPAC]
-=== Creating and Applying a Item Tag During Cataloging ===
+== Creating and Applying a Item Tag During Cataloging ==
Item tags can be created in the Holdings Editor on the fly while cataloging or viewing an item:
NOTE: It is not possible to remove tags using the Item Bucket interface.
-=== Searching Item Tags ===
+== Searching Item Tags ==
Item Tags can be searched in the public catalog if searching has been enabled via Library Settings. Item Tags can be searched in the Basic and Advanced Search interfaces by selecting Digital Bookplate as the search field. Specific item tags can also be searched using a Keyword search and a specific search syntax.
-==== Digital Bookplate Search Field ====
+=== Digital Bookplate Search Field ===
*Basic Search*
image::media/copytags11.png[Digital Bookplates Search Field Location in Advanced Search]
-==== Keyword Search ====
+=== Keyword Search ===
Item Tags can also be searched by using a Keyword search in the Basic and Advanced search interfaces. Searches need to be constructed using the following syntax:
-== Link Checker ==
+= Link Checker =
+:toc:
The Link Checker enables you to verify the validity of URLs stored in MARC records.
The ability to verify URLs would benefit locations with large electronic resource collections.
-=== Search for URLs ===
+== Search for URLs ==
Search for MARC records that contain URLs that you want to verify.
image::media/Link_Checker1.jpg[Link_Checker1]
-=== View Your Results ===
+== View Your Results ==
If you do not click *Process Immediately*, then you must select the links that you want to verify, and click
*Verify Selected URLs*. If you click *Process Immediately*, then you skip this step, and Evergreen
image::media/Link_Checker6.jpg[Link_Checker6]
-=== Manage Your Sessions ===
+== Manage Your Sessions ==
-==== Edit Columns ====
+=== Edit Columns ===
You can use the *Column Picker* to add and remove columns on any of the *Link Checker* interfaces.
To access the *Column Picker*, right click on any of the column headings. The columns are saved to your user account.
-==== Clone Sessions ====
+=== Clone Sessions ===
You can clone sessions that you run frequently or that have frequently-used parameters that
need only minor adjustments to create new searches. To clone a session:
. In the Session ID column, click *Clone*. A copy of the parameters of that search will appear.
-==== View Verification Attempts ====
+=== View Verification Attempts ===
To view the results of a verification attempt after you have closed the session, click *Cataloging* -> *Link Checker*.
Your link checker sessions appear in a list. To view the results of a session, click the *Open* link in the Session ID column.
+++ /dev/null
-=== MARC Tag-table Service ===
-The tag tables for the web staff client MARC editor are
-stored in the database. The tag-table
-service has the following features:
-
-- specifies whether (sub)fields are optional or mandatory
-- specifies whether (sub)fields are repeatable or not
-- a coded value map can be associated with a subfield to
- establish a controlled vocabulary for that subfield
-- MARC field and subfield definitions can be overridden
- by institutions further down in the organizational unit
- hierarchy. This allows, for example, a library to specify
- definitions for local MARC tags.
-- values supplied by the tag-table service are used to
- populate values in context menus in the web staff client
- MARC editor.
-
-MARC Tag Tables can be found under Administration -> Server Administration -> MARC Tag Tables.
-
-MARC Tag Tables Grid:
-
-image::media/MARC_Tag_Tables_Grid.PNG[Grid view of MARC Tag Tables]
-
-MARC Tag Tables Detail:
-
-image::media/MARC_Tag_Tables_Detail.PNG[Detail view of MARC Tag Tables]
-
-The initial seed data for the in-database tag table is
-derived from the current tooltips XML file.
-
+++ /dev/null
-=== Bibliographic Record Merging and Overlay ===
-
-Catalogers can merge or overlay records in record buckets or using records obtained from a Z39.50 service.
-
-==== Merge Records in Record Buckets ====
-
-1. Click *Cataloging>Record Buckets*.
-2. Create and/or select a record bucket.
-3. Select the records that you want to merge, and click *Actions>Merge Selected Records*.
-
-image::media/marcoverlay1.png[]
-
-4. The Merge Selected Records interface appears.
-5. The records to be merged appear on the right side of the screen. Click *Use as Lead Record* to select a lead record from those that need to be merged.
-
-image::media/marcoverlay2.png[]
-
-6. Select a merge profile from the drop down box.
-
-image::media/marcoverlay3.png[]
-
-7. After you select the profile, you can preview the changes that will be made to the record.
-
-image::media/marcoverlay4.png[]
-
-8. You can change the merge profile at any time; after doing so, the result of the merge will be recalculated. The merge result will also be recalculated after editing the lead record, changing which record is to be used as lead, or removing a record from consideration.
-9. When you are satisfied that you have selected the correct merge profile, click the *Merge* button in the bottom right corner.
-10. Note that merge profiles that contain a preserve field specification are not available to be chosen in this interface, as they would have the effect of reversing which bibliographic record is considered the target of the merge.
-
-==== Track Record Merges ====
-
-When 2 or more bib records are merged in a record bucket, all records involved are stamped with a new merge_date value. For any bib record, this field indicates the last time it was involved in a merge. At the same time, all subordinate records (i.e. those deleted as a product of the merge) are stamped with a merged_to value indicating which bib record the source record was merged with.
-
-In the browser client bib record display, a warning alert now appears along the top of the page (below the Deleted alert) indicating when a record was used in a merge, when it was merged, and which record it was merge with, rendered as a link to the target record.
-
-image::media/merge_tracking.png[merge message with date]
-
-==== Merge Records Using Z39.50 ====
-
-1. Search for a record in the catalog that you want to overlay.
-2. Select the record, and click *MARC View*.
-3. Select *Mark for: Overlay Target*.
-
-image::media/marcoverlay5.png[]
-
-4. Click *Cataloging>Import Record from Z39.50*.
-5. Search for the lead record that you want to overlay within the Z39.50 interface.
-6. Select the desired record, and click *Overlay*.
-
-image::media/marcoverlay6.png[]
-
-7. The record that you have targeted to be overlaid, and the new record, appear side by side.
-
-image::media/marcoverlay7.png[]
-
-8. You can edit the lead record before you overlay the target. To edit the record, click the *Edit Z39.50 Record* button above the lead record.
-9. The MARC editor will appear. You can make your changes in the MARC editor, or you can select the *Flat Text Editor* to make changes. After you have edited the record, click *Modify* in the top right corner, and then *Use Edits* in the bottom right corner. Note that the record you are editing is the version from the Z39.50 server not including any changes that would be made as a result of applying the selected merge file.
-10. You will return to the side-by-side comparison of the records and then can proceed with the overlay.
-11. Once you are satisfied with the record that you want to overlay, select a merge profile from the drop down box, *Choose merge profile*.
-12. Click *Overlay*. The overlay will occur, and you will be taken back to the Z39.50 interface.
-13. Note that the staff client remembers the last merge overlay profile that you selected, so the next time that you open the interface, it will default to that profile. Simply change the profile to make a different selection.
-14. Also note when the merge profile is applied, the Z39.50 record acts as the target of the merge. For example, if your merge profile adds 650 fields, those 650 fields are brought over from the record that already exists in the Evergreen database (i.e., the one that you are overlaying from Z39.50).
-15. Also note that merge profiles that contain a preserve field specification are not available to be chosen in this interface, as they would have the effect of reversing which bibliographic record is considered the target of the merge.
-
-==== New Admin Settings ====
-
-1. Go to *Admin>Local Administration>Library Settings Editor>Upload Default Merge Profile (Z39.50 and Record Buckets)*.
-2. Select a default merge profile, and *click Update Setting*. The merge profiles that appear in this drop down box are those that are created in *MARC Batch Import/Export*. Note that catalogers will only see merge profiles that are allowed by their org unit and permissions.
-== Monograph Parts ==
+= Monograph Parts =
+:toc:
*Monograph Parts* enables you to differentiate between parts of
monographs or other multi-part items. This feature enables catalogers
groups or users that will make use of the features described below.
-=== Add a Monograph Part to an Existing Record ===
+== Add a Monograph Part to an Existing Record ==
To add a monograph part to an existing record in the catalog:
+
image::media/manage_parts_opac.png[Catalog Record showing items with part details]
-=== Monograph Part Merging ===
+== Monograph Part Merging ==
The monograph part list for a bibliographic record may, over time, diverge from
the proscribed format, resulting in multiple labels for what are essentially the
-== Overlay Existing Catalog Record via Z39.50 Import ==
+= Overlay Existing Catalog Record via Z39.50 Import =
+:toc:
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.
-== MARC 007 Field Physical Characteristics Wizard ==
+= MARC 007 Field Physical Characteristics Wizard =
+:toc:
The MARC 007 Field Physical Characteristics Wizard enables catalogers to interact with a database wizard that leads the user step-by-step through the MARC 007 field positions. The wizard displays the significance of the current position and provides dropdown lists of possible values for the various components of the MARC 007 field in a more user-friendly way.
-== Record Buckets ==
+= Record Buckets =
+:toc:
-=== Introduction ===
+== Introduction ==
Record buckets are containers for MARC records. Once records are in a bucket, you can take
various types of actions, including:
* Downloading the MARC files for all records in the bucket, so you can edit them in another
program like http://marcedit.reeset.net[MARCEdit].
-=== Creating Record Buckets ===
+== Creating Record Buckets ==
. Click on _Cataloging_ -> _Record Buckets_.
. On the _Buckets_ menu, click _New Bucket_.
. Give the bucket a name and (optionally) a description.
-=== Adding Records to a Bucket ===
+== Adding Records to a Bucket ==
-==== From the Record Bucket Interface ====
+=== From the Record Bucket Interface ===
. Click on _Cataloging_ -> _Record Buckets_.
. On the _Buckets_ menu, choose the bucket that you'd like to add records to.
. Go to the _Record Query_ tab.
You can use the same boolean operator symbols that are used in the OPAC (_||_ for boolean OR, _&&_ for boolean AND, and _-_ for boolean NOT).
+== Bibliographic Record Merging and Overlay ==
+
+Catalogers can merge or overlay records in record buckets or using records obtained from a Z39.50 service.
+
+=== Merge Records in Record Buckets ===
+
+1. Click *Cataloging>Record Buckets*.
+2. Create and/or select a record bucket.
+3. Select the records that you want to merge, and click *Actions>Merge Selected Records*.
+
+image::media/marcoverlay1.png[]
+
+4. The Merge Selected Records interface appears.
+5. The records to be merged appear on the right side of the screen. Click *Use as Lead Record* to select a lead record from those that need to be merged.
+
+image::media/marcoverlay2.png[]
+
+6. Select a merge profile from the drop down box.
+
+image::media/marcoverlay3.png[]
+
+7. After you select the profile, you can preview the changes that will be made to the record.
+
+image::media/marcoverlay4.png[]
+
+8. You can change the merge profile at any time; after doing so, the result of the merge will be recalculated. The merge result will also be recalculated after editing the lead record, changing which record is to be used as lead, or removing a record from consideration.
+9. When you are satisfied that you have selected the correct merge profile, click the *Merge* button in the bottom right corner.
+10. Note that merge profiles that contain a preserve field specification are not available to be chosen in this interface, as they would have the effect of reversing which bibliographic record is considered the target of the merge.
+
+=== Track Record Merges ===
+
+When 2 or more bib records are merged in a record bucket, all records involved are stamped with a new merge_date value. For any bib record, this field indicates the last time it was involved in a merge. At the same time, all subordinate records (i.e. those deleted as a product of the merge) are stamped with a merged_to value indicating which bib record the source record was merged with.
+
+In the browser client bib record display, a warning alert now appears along the top of the page (below the Deleted alert) indicating when a record was used in a merge, when it was merged, and which record it was merge with, rendered as a link to the target record.
+
+image::media/merge_tracking.png[merge message with date]
+
+=== Merge Records Using Z39.50 ===
+
+1. Search for a record in the catalog that you want to overlay.
+2. Select the record, and click *MARC View*.
+3. Select *Mark for: Overlay Target*.
+
+image::media/marcoverlay5.png[]
+
+4. Click *Cataloging>Import Record from Z39.50*.
+5. Search for the lead record that you want to overlay within the Z39.50 interface.
+6. Select the desired record, and click *Overlay*.
+
+image::media/marcoverlay6.png[]
+
+7. The record that you have targeted to be overlaid, and the new record, appear side by side.
+
+image::media/marcoverlay7.png[]
+
+8. You can edit the lead record before you overlay the target. To edit the record, click the *Edit Z39.50 Record* button above the lead record.
+9. The MARC editor will appear. You can make your changes in the MARC editor, or you can select the *Flat Text Editor* to make changes. After you have edited the record, click *Modify* in the top right corner, and then *Use Edits* in the bottom right corner. Note that the record you are editing is the version from the Z39.50 server not including any changes that would be made as a result of applying the selected merge file.
+10. You will return to the side-by-side comparison of the records and then can proceed with the overlay.
+11. Once you are satisfied with the record that you want to overlay, select a merge profile from the drop down box, *Choose merge profile*.
+12. Click *Overlay*. The overlay will occur, and you will be taken back to the Z39.50 interface.
+13. Note that the staff client remembers the last merge overlay profile that you selected, so the next time that you open the interface, it will default to that profile. Simply change the profile to make a different selection.
+14. Also note when the merge profile is applied, the Z39.50 record acts as the target of the merge. For example, if your merge profile adds 650 fields, those 650 fields are brought over from the record that already exists in the Evergreen database (i.e., the one that you are overlaying from Z39.50).
+15. Also note that merge profiles that contain a preserve field specification are not available to be chosen in this interface, as they would have the effect of reversing which bibliographic record is considered the target of the merge.
+
+=== New Admin Settings ===
+
+1. Go to *Admin>Local Administration>Library Settings Editor>Upload Default Merge Profile (Z39.50 and Record Buckets)*.
+2. Select a default merge profile, and *click Update Setting*. The merge profiles that appear in this drop down box are those that are created in *MARC Batch Import/Export*. Note that catalogers will only see merge profiles that are allowed by their org unit and permissions.
-== Specific fields ==
+= Specific fields =
+:toc:
-=== 264 ===
+== 264 ==
The Public Catalog displays tag 264 information for Publisher, Producer, Distributor, Manufacturer,
and Copyright within a full bib record's summary.
+++ /dev/null
-=== Accessing the holdings editor from a catalog record ===
-
-The bibliographic record detail page displays library holdings, including the call number, shelving location, and item barcode. Within the
-staff client, the holdings list displays a column next to the item barcode(s) containing two links, *view* and *edit*.
-
-image::media/copy_edit_link_1.jpg[Copy Edit Link]
-
-Clicking on the *view* link opens the *Item Status* screen for that specific item.
-
-Clicking on the *edit* link opens the *Holdings Editor* screen for that specific item.
-
-The *edit* link will only be exposed next to copies when the user has the *UPDATE_COPY* permission at the copy owning or circulating library.
-
-== Using the Holdings Editor ==
+= Using the Holdings Editor =
+:toc:
indexterm:[copies,editing]
indexterm:[items,editing]
indexterm:[call numbers,editing]
The Holdings Editor is the tool where you can edit all holdings data.
-=== Specific fields ===
+== Specific fields ==
-==== Acquisitions Cost ====
+=== Acquisitions Cost ===
indexterm:[acquisitions cost]
This field is populated with the invoiced cost of the originating acquisition.
This field will be empty until its originating acquisition is connected to an
invoice.
-==== Item Number ====
+=== Item Number ===
indexterm:[copy number]
indexterm:[item number]
not include an item number in this field, Evergreen will assign your
item a default item number of 1.
-=== Accessing the Holdings Editor by barcode ===
+== Accessing the Holdings Editor by barcode ==
. Click *Search -> Search for Items by Barcode*
. Scan your barcode.
. Right click on the entry in the grid.
. Click *Edit -> Call Numbers and Items* on the actions menu that appears.
+== Accessing the holdings editor from a catalog record ==
+
+The bibliographic record detail page displays library holdings, including the call number, shelving location, and item barcode. Within the
+staff client, the holdings list displays a column next to the item barcode(s) containing two links, *view* and *edit*.
+
+image::media/copy_edit_link_1.jpg[Copy Edit Link]
+
+Clicking on the *view* link opens the *Item Status* screen for that specific item.
+
+Clicking on the *edit* link opens the *Holdings Editor* screen for that specific item.
+
+The *edit* link will only be exposed next to copies when the user has the *UPDATE_COPY* permission at the copy owning or circulating library.
+
+== Hiding Fields in the Holdings Editor ==
+
+
+A user may hide specific fields in the holdings editor if these fields are not used for cataloging in their organization. Hiding fields that are not used by your organization helps to reduce confusion among staff and also declutters the holdings editor screen.
+
+To hide one or more fields from the holdings editor:
+
+. Retrieve the record.
++
+[NOTE]
+===================================================================================
+You can retrieve records in many ways, including:
+
+* If you know its database ID, enter it into Cataloging > Retrieve Bib Record by ID.
+
+* If you know its control number, enter it into Cataloging > Retrieve Bib Record by TCN.
+
+* Searching in the catalog.
+
+* Clicking on a link from the Acquisitions or Serials modules.
+===================================================================================
++
+. Select the *Add Holdings* button. The *Holdings Editor* will display.
+
+. In the Holdings Editor, select the *Defaults* tab.
++
+image::media/Holdings_Editor_Defaults_Tab.png[Holdings editor defaults tab]
++
+. On the Defaults tab, uncheck the boxes for the field(s) that you wish to hide. It is not necessary to save this screen; changes are saved automatically.
++
+image::media/Holdings_Editor_Hide_Display_Defaults.png[Holdings editor display defaults with deselected fields]
++
+. Select the *Edit* tab; the de-selected fields no longer appear on the holdings editor.
-== Z39.50 Search Enhancements ==
+= Z39.50 Search Enhancements =
+:toc:
*Abstract*
projects / evergreen-equinox.git / commitdiff