* 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]
. 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.
+
+++ /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.
+++ /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.
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.
+++ /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.
-
. 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.
projects / working / Evergreen.git / commitdiff