From dc43de7bc781bb40b2779b3102948085c106baf6 Mon Sep 17 00:00:00 2001 From: Cheyenne Jones <44786394+Cheyenne-jones@users.noreply.github.com> Date: Mon, 5 Nov 2018 12:29:18 -0800 Subject: [PATCH] Docs: Updating Terminology This updates outdated terms like copy, volume, and copy location with the up-to-date item, call number, and shelving location. Signed-off-by: Cheyenne Jones <44786394+Cheyenne-jones@users.noreply.github.com> Signed-off-by: Jane Sandberg --- .../admin/Best_Hold_Selection_Sort_Order.adoc | 8 +-- docs/admin/SMS_messaging.adoc | 4 +- docs/admin/age_hold_protection.adoc | 6 +- docs/admin/aged_circs.adoc | 4 +- docs/admin/copy_statuses.adoc | 42 +++++++------- docs/admin/copy_tags_admin.adoc | 56 +++++++++---------- docs/admin/floating_groups.adoc | 16 +++--- docs/admin/hold_driven_recalls.adoc | 4 +- docs/admin/librarysettings.adoc | 36 ++++++------ docs/admin/phonelist.adoc | 10 ++-- docs/admin/sitemap_admin.adoc | 2 +- .../describing_your_people.adoc | 2 +- .../importing_via_staff_client.adoc | 16 +++--- .../migrating_your_data.adoc | 16 +++--- .../ordering_materials.adoc | 16 +++--- docs/cataloging/batch_importing_MARC.adoc | 16 +++--- .../cataloging_electronic_resources.adoc | 6 +- docs/cataloging/copy_tags_cataloging.adoc | 18 +++--- 18 files changed, 139 insertions(+), 139 deletions(-) diff --git a/docs/admin/Best_Hold_Selection_Sort_Order.adoc b/docs/admin/Best_Hold_Selection_Sort_Order.adoc index a25b51ca27..bf17c59413 100644 --- a/docs/admin/Best_Hold_Selection_Sort_Order.adoc +++ b/docs/admin/Best_Hold_Selection_Sort_Order.adoc @@ -1,7 +1,7 @@ Best-Hold Selection Sort Order ------------------------------ -Best-Hold Selection Sort Order allows libraries to configure customized rules for Evergreen to use to select the best hold to fill at opportunistic capture. When a copy is captured for a hold upon check-in, Evergreen evaluates the holds in the system that the item could fill. Evergreen uses a set of rules, or a Best-Hold Selection Sort Order, to determine the best hold to fill with the item. In previous version of Evergreen, there were two sets of rules for Evergreen to use to determine the best hold to fulfill: Traditional and FIFO (First In, First Out). Traditional uses Org Unit Proximity to identify the nearest hold to fill. FIFO follows a strict order of first-in, first-out rules. This feature allows new, custom Best-Hold Selection Sort Orders to be created. Existing Best-Hold Selection Sort Orders can also be modified. +Best-Hold Selection Sort Order allows libraries to configure customized rules for Evergreen to use to select the best hold to fill at opportunistic capture. When a item is captured for a hold upon check-in, Evergreen evaluates the holds in the system that the item could fill. Evergreen uses a set of rules, or a Best-Hold Selection Sort Order, to determine the best hold to fill with the item. In previous version of Evergreen, there were two sets of rules for Evergreen to use to determine the best hold to fulfill: Traditional and FIFO (First In, First Out). Traditional uses Org Unit Proximity to identify the nearest hold to fill. FIFO follows a strict order of first-in, first-out rules. This feature allows new, custom Best-Hold Selection Sort Orders to be created. Existing Best-Hold Selection Sort Orders can also be modified. Preconfigured Best-Hold Orders @@ -23,7 +23,7 @@ To create a new Best-Hold Selection Sort Order, go to *Administration -> Server . Click *Create New*. . Assign your Best-Hold Selection Sort Order a *Name*. -. Next, use the *Move Up* and *Move Down* buttons to arrange the fields in the order that you would like Evergreen to check when looking for the best hold to fill with a copy at opportunistic capture. +. Next, use the *Move Up* and *Move Down* buttons to arrange the fields in the order that you would like Evergreen to check when looking for the best hold to fill with an item at opportunistic capture. . Click *Save Changes* to create your custom Best-Hold Selection Sort Order. image::media/best_hold_sort_order1.jpg[Best-Hold Selection Sort Order] @@ -35,7 +35,7 @@ To edit an existing Best-Hold Selection Sort Order, go to *Administration -> Ser . Click *Edit Existing*. . Choose the Best-Hold Selection Sort Order that you would like to edit from the drop down menu. -. Next, use the *Move Up* and *Move Down* buttons to arrange the fields in the new order that you would like Evergreen to check when looking for the best hold to fill with a copy at opportunistic capture. +. Next, use the *Move Up* and *Move Down* buttons to arrange the fields in the new order that you would like Evergreen to check when looking for the best hold to fill with an item at opportunistic capture. . Click *Save Changes* to save your edits. Choosing the Best-Hold Selection Sort Order @@ -57,4 +57,4 @@ Permissions to use this Feature ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To administer the custom Best-Hold Selection Sort Order interface, you need the following permission: -* ADMIN_HOLD_CAPTURE_SORT \ No newline at end of file +* ADMIN_HOLD_CAPTURE_SORT diff --git a/docs/admin/SMS_messaging.adoc b/docs/admin/SMS_messaging.adoc index 181c1880db..91797c764c 100644 --- a/docs/admin/SMS_messaging.adoc +++ b/docs/admin/SMS_messaging.adoc @@ -2,12 +2,12 @@ SMS Text Messaging ------------------ The SMS Text Messaging feature enables users to receive hold notices via text message. Users can opt-in to this hold notification as their default setting for all holds, or they -can receive specific hold notifications via text message. Users can also send call numbers and copy locations via text message. +can receive specific hold notifications via text message. Users can also send call numbers and item locations via text message. Administrative Setup ~~~~~~~~~~~~~~~~~~~~ -You cannot receive text messages from Evergreen by default. You must enable this feature to receive hold notices and copy information from Evergreen via text message. +You cannot receive text messages from Evergreen by default. You must enable this feature to receive hold notices and item information from Evergreen via text message. Enable Text Messages ^^^^^^^^^^^^^^^^^^^^ diff --git a/docs/admin/age_hold_protection.adoc b/docs/admin/age_hold_protection.adoc index 11b6350825..22bc48e030 100644 --- a/docs/admin/age_hold_protection.adoc +++ b/docs/admin/age_hold_protection.adoc @@ -7,7 +7,7 @@ Age hold protection prevents new items from filling holds requested for pickup a You can define the protection period in *Administration* -> *Server Administration* -> *Age Hold Protect Rules*. -The protection period when applied to a copy record can start with the copy record create date (default) or active date. You can change this setting in *Administration* -> *Local Administration* -> *Library Settings Editor*: Use Active Date for Age Protection. +The protection period when applied to a item record can start with the item record create date (default) or active date. You can change this setting in *Administration* -> *Local Administration* -> *Library Settings Editor*: Use Active Date for Age Protection. In addition to time period, you can set the proximity value to define which organizational units are allowed to act as pickup libraries. The proximity values affect holds as follows: @@ -15,9 +15,9 @@ In addition to time period, you can set the proximity value to define which org * "1" allows holds where pickup library = owning library, parent, and child organizational units * "2" allows holds where pickup library = owning library, parent, child, and/or sibling organizational units -Age protection only applies to individual copy records. You cannot configure age protection rules in hold policies. +Age protection only applies to individual item records. You cannot configure age protection rules in hold policies. Active date display in OPAC ~~~~~~~~~~~~~~~~~~~~~~~~~~~ -If a library uses the copy's active date to calculate holds age protection, the active date will display with the copy details instead of the create date in the staff client view of the catalog. Libraries that do not enable the _Use Active Date for Age Protection_ library setting will continue to display the create date. \ No newline at end of file +If a library uses the item's active date to calculate holds age protection, the active date will display with the item details instead of the create date in the staff client view of the catalog. Libraries that do not enable the _Use Active Date for Age Protection_ library setting will continue to display the create date. diff --git a/docs/admin/aged_circs.adoc b/docs/admin/aged_circs.adoc index 098b9c17f2..e71402d3e3 100644 --- a/docs/admin/aged_circs.adoc +++ b/docs/admin/aged_circs.adoc @@ -21,7 +21,7 @@ There are four global flags used for aging circulations. 1. Historical Circulation Retention Age - determines the timeframe for aging circulations based on transaction age (7 days, 14 days, 30 days, etc). -2. Historical Circulations Per Copy - determines how many circulations to keep (ex. 1, 2, 3). If set to 1, Evergreen will always keep the last (most recent) circulation. +2. Historical Circulations Per Item - determines how many circulations to keep (ex. 1, 2, 3). If set to 1, Evergreen will always keep the last (most recent) circulation. 3. Historical Circulations use most recent xact_finish date instead of last circ's (true or false) @@ -39,7 +39,7 @@ Data that is not aged includes: * open transactions (i.e. checked out) * closed transactions with unpaid fines * closed transactions with unpaid bills -* the last X circulation(s) (determined by historical circulations per copy flag) +* the last X circulation(s) (determined by historical circulations per item flag) [TIP] diff --git a/docs/admin/copy_statuses.adoc b/docs/admin/copy_statuses.adoc index 41aabebdbf..5c6d67600d 100644 --- a/docs/admin/copy_statuses.adoc +++ b/docs/admin/copy_statuses.adoc @@ -1,35 +1,35 @@ -Copy Status +Item Status ----------- -To navigate to the copy status editor from the staff client menu, select -*Administration* -> *Server Administration* -> *Copy Statuses*. +To navigate to the item status editor from the staff client menu, select +*Administration* -> *Server Administration* -> *Item Statuses*. -The Copy Status Editor is used to add, edit and delete statuses of copies in +The Item Status Editor is used to add, edit and delete statuses of items in your system. For each status, you can set the following properties: -* Holdable - If checked, users can place holds on copies in this status, +* Holdable - If checked, users can place holds on items in this status, provided there are no other flags or rules preventing holds. If unchecked, -users cannot place holds on copies in this status. -* OPAC Visible - If checked, copies in this status will be visible in the -public catalog. If unchecked, copies in this status will not be visible in the +users cannot place holds on items in this status. +* OPAC Visible - If checked, items in this status will be visible in the +public catalog. If unchecked, items in this status will not be visible in the public catalog, but they will be visible when using the catalog in the staff client. -* Sets copy active - If checked, moving a copy that does not yet have an -active date to this status will set the active date. If the copy already has +* Sets item active - If checked, moving an item that does not yet have an +active date to this status will set the active date. If the item already has an active date, then no changes will be made to the active date. If unchecked, -this status will never set the copy's active date. -* Is Available - If checked, copies with this status will appear in catalog +this status will never set the item's active date. +* Is Available - If checked, items with this status will appear in catalog searches where "limit to available" is selected as a search filter. Also, -copies with this status will check out without status warnings. +items with this status will check out without status warnings. By default, the "Available" and "Reshelving" statuses have the "Is Available" -flag set. The flag may be applied to local/custom statuses via the copy status +flag set. The flag may be applied to local/custom statuses via the item status admin interface. -Evergreen comes pre-loaded with a number of copy statuses. +Evergreen comes pre-loaded with a number of item statuses. -.Stock copy statuses and default settings +.Stock item statuses and default settings [options="header"] |============================================== |ID|Name|Holdable|OPAC Visible|Sets copy active @@ -53,7 +53,7 @@ Evergreen comes pre-loaded with a number of copy statuses. |17|Lost and Paid|false|false|false |============================================== -Adding Copy Statuses +Adding Item Statuses ~~~~~~~~~~~~~~~~~~~~ . In the _New Status_ field, enter the name of the new status you wish to add. @@ -67,7 +67,7 @@ status. image::media/copy_status_add.png[Adding copy statuses] -Deleting Copy Statuses +Deleting Item Statuses ~~~~~~~~~~~~~~~~~~~~~~ . Highlight the statuses you wish to delete. Ctrl-click to select more than one @@ -78,15 +78,15 @@ status. image::media/copy_status_delete.png[Deleting copy statuses] [NOTE] -You will not be able to delete statuses if copies currently exist with that +You will not be able to delete statuses if items currently exist with that status. -Editing Copy Statuses +Editing Item Statuses ~~~~~~~~~~~~~~~~~~~~~ . Double click on a status name to change its name. Enter the new name. . To change whether a status is holdable, visible in the OPAC, or sets the -copy's active date, check or uncheck the relevant checkbox. +item's active date, check or uncheck the relevant checkbox. . Once you have finished editing the statuses, remember to click Save Changes. diff --git a/docs/admin/copy_tags_admin.adoc b/docs/admin/copy_tags_admin.adoc index f79fc94b0f..092e229c99 100644 --- a/docs/admin/copy_tags_admin.adoc +++ b/docs/admin/copy_tags_admin.adoc @@ -1,7 +1,7 @@ -Copy Tags (Digital Bookplates) +Item Tags (Digital Bookplates) ------------------------------ -Copy Tags allow staff to apply custom, pre-defined labels or tags to items. Copy tags are visible in the public catalog and are searchable in both the staff client and public catalog based on configuration. This feature was designed to be used for Digital Bookplates to attach donation or memorial information to items, but may be used for broader purposes to tag items. +Item Tags allow staff to apply custom, pre-defined labels or tags to items. Item tags are visible in the public catalog and are searchable in both the staff client and public catalog based on configuration. This feature was designed to be used for Digital Bookplates to attach donation or memorial information to items, but may be used for broader purposes to tag items. Administration @@ -9,10 +9,10 @@ Administration New Permissions: -* ADMIN_COPY_TAG_TYPES: required to create a new tag type under *Server Administration->Copy Tag Types* -* ADMIN_COPY_TAG: required to create a new tag under *Local Administration->Copy Tags* +* ADMIN_COPY_TAG_TYPES: required to create a new tag type under *Server Administration->Item Tag Types* +* ADMIN_COPY_TAG: required to create a new tag under *Local Administration->Item Tags* -NOTE: The existing permission UPDATE_COPY is required to assign a tag to a copy +NOTE: The existing permission UPDATE_COPY is required to assign a tag to a item New Library Settings: @@ -20,56 +20,56 @@ New Library Settings: * OPAC: Enable Digital Bookplate Search: when set to _True_ for a given org unit, the digital bookplate search option will be available in the catalog. -Creating Copy Tags +Creating item Tags ~~~~~~~~~~~~~~~~~~ -There are two components to this feature: Copy Tag Types and Copy Tags. +There are two components to this feature: Item Tag Types and Item Tags. -Copy Tag Types are used to define the type of tag, such as “Bookplates” or “Local History Notes”, as well as the organizational unit scope for use of the tag type. +Item Tag Types are used to define the type of tag, such as “Bookplates” or “Local History Notes”, as well as the organizational unit scope for use of the tag type. -Copy Tags are associated with a Copy Tag Type and are used to configure the list of tags that can be applied to copies, such as a list of memorial or donation labels, that are applicable to a particular organizational unit. +Item Tags are associated with a Item Tag Type and are used to configure the list of tags that can be applied to copies, such as a list of memorial or donation labels, that are applicable to a particular organizational unit. -Create Copy Tag Types +Create Item Tag Types ^^^^^^^^^^^^^^^^^^^^^ -. Go to *Administration->Server Administration->Copy Tag Types*. -. In the upper left hand corner, click *New Record*. A dialog box will appear. Assign the following to create a new Copy Tag Type: -.. *Code*: a code to identify the copy tag type. -.. *Label*: a label that will appear in drop down menus to identify the copy tag type. -.. *Owner*: the organizational unit that can see and use the copy tag type. -. Click *Save* and the new Copy Tag Type will appear in the list. Next create the associated Copy Tags. +. Go to *Administration->Server Administration->Item Tag Types*. +. In the upper left hand corner, click *New Record*. A dialog box will appear. Assign the following to create a new Item Tag Type: +.. *Code*: a code to identify the item tag type. +.. *Label*: a label that will appear in drop down menus to identify the item tag type. +.. *Owner*: the organizational unit that can see and use the item tag type. +. Click *Save* and the new Item Tag Type will appear in the list. Next create the associated Item Tags. image::media/copytags1.PNG[] image::media/copytags2.PNG[] -Create Copy Tags +Create Item Tags ^^^^^^^^^^^^^^^^ -. Go to *Administration->Local Administration->Copy Tags*. -. In the upper left hand corner, click *New Record*. A dialog box will appear. Assign the following to create a new Copy Tag: -.. *Copy Tag Type*: select the Copy Tag Type with which you want to associate the new Copy Tag. -.. *Label*: assign a label to the new copy tag. -.. *Value*: assign a value to the new copy tag. This will display in the catalog. -.. *Staff Note*: a note may be added to guide staff in when to apply the copy tag. -.. *Is OPAC Visible?*: If a copy tag is OPAC Visible, it can be searched for and viewed in the OPAC and the staff catalog. If a copy tag is not OPAC Visible, it can only be searched for and viewed in the staff catalog. +. Go to *Administration->Local Administration->Item Tags*. +. In the upper left hand corner, click *New Record*. A dialog box will appear. Assign the following to create a new Item Tag: +.. *Item Tag Type*: select the Item Tag Type with which you want to associate the new Item Tag. +.. *Label*: assign a label to the new item tag. +.. *Value*: assign a value to the new item tag. This will display in the catalog. +.. *Staff Note*: a note may be added to guide staff in when to apply the item tag. +.. *Is OPAC Visible?*: If a item tag is OPAC Visible, it can be searched for and viewed in the OPAC and the staff catalog. If a item tag is not OPAC Visible, it can only be searched for and viewed in the staff catalog. .. *Owner*: select the organization unit at which this tag can be seen and used. -. Click *Save* and the new Copy Tag will appear in the list. +. Click *Save* and the new Item Tag will appear in the list. image::media/copytags3.PNG[] image::media/copytags4.PNG[] -Managing Copy Tags +Managing Item Tags ~~~~~~~~~~~~~~~~~~ Editing Tags ^^^^^^^^^^^^ -Existing copy tags can be edited by selecting a tag and clicking *Actions->Edit Record* or right-clicking on a tag and selecting *Edit Record*. The dialog box will appear and you can modify the copy tag. Click *Save* to save any changes. Changes will be propagated to any copies that the tag has been attached to. +Existing item tags can be edited by selecting a tag and clicking *Actions->Edit Record* or right-clicking on a tag and selecting *Edit Record*. The dialog box will appear and you can modify the item tag. Click *Save* to save any changes. Changes will be propagated to any items that the tag has been attached to. Deleting Tags ^^^^^^^^^^^^^ -Existing copy tags can be deleted by selecting a tag and clicking *Actions->Delete Record* or right-clicking on a tag and selecting *Delete Record*. Deleting a tag will delete the tag from any copies it was attached to in the catalog. +Existing item tags can be deleted by selecting a tag and clicking *Actions->Delete Record* or right-clicking on a tag and selecting *Delete Record*. Deleting a tag will delete the tag from any items it was attached to in the catalog. diff --git a/docs/admin/floating_groups.adoc b/docs/admin/floating_groups.adoc index 9238d443cf..0aea2e618e 100644 --- a/docs/admin/floating_groups.adoc +++ b/docs/admin/floating_groups.adoc @@ -1,16 +1,16 @@ Floating Groups =============== -Before floating groups copies could float or not. If they floated then they floated everywhere, with no restrictions. +Before floating groups items could float or not. If they floated then they floated everywhere, with no restrictions. -After floating groups where a copy will float is defined by what group it has been assigned to. +After floating groups where an item will float is defined by what group it has been assigned to. Floating Groups --------------- Each floating group comes with a name and a manual flag, plus zero or more group members. The name is used solely for selection and display purposes. -The manual flag dictates whether or not the "Manual Floating Active" checkin modifier needs to be active for a copy to float. This allows for greater control over when items float. It also prevents automated checkins via SIP2 from triggering floats. +The manual flag dictates whether or not the "Manual Floating Active" checkin modifier needs to be active for an item to float. This allows for greater control over when items float. It also prevents automated checkins via SIP2 from triggering floats. Floating Group Members ~~~~~~~~~~~~~~~~~~~~~~ @@ -25,7 +25,7 @@ The org unit and all descendants are included, unless max depth is set, in which Stop Depth ~~~~~~~~~~ -The stop depth is the highest point from the current copy circ library to the checkin library for the item that will be traversed. If the item has to go higher than the stop depth on the tree the member rule in question is ignored. +The stop depth is the highest point from the current item circ library to the checkin library for the item that will be traversed. If the item has to go higher than the stop depth on the tree the member rule in question is ignored. Max Depth ~~~~~~~~~ @@ -55,7 +55,7 @@ One member: Float Within System ~~~~~~~~~~~~~~~~~~~ -This would permit a copy to float anywhere within a system, but would return to the system if it was returned elsewhere. +This would permit an item to float anywhere within a system, but would return to the system if it was returned elsewhere. One member: @@ -67,7 +67,7 @@ One member: Float To All Branches ~~~~~~~~~~~~~~~~~~~~~ -This would permit a copy to float to any branch, but not to sublibraries or bookmobiles. +This would permit an item to float to any branch, but not to sublibraries or bookmobiles. One member: @@ -79,7 +79,7 @@ One member: Float To All Branches Within System ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -This would permit a copy to float to any branch in a system, but not to sublibraries or bookmobiles, and returning to the system if returned elsewhere. +This would permit an item to float to any branch in a system, but not to sublibraries or bookmobiles, and returning to the system if returned elsewhere. One member: @@ -91,7 +91,7 @@ One member: Float Between BR1 and BR3 ~~~~~~~~~~~~~~~~~~~~~~~~~ -This would permit a copy to float between BR1 and BR3 specifically, excluding sublibraries and bookmobiles. +This would permit an item to float between BR1 and BR3 specifically, excluding sublibraries and bookmobiles. It would consist of two members, identical other than the org unit: diff --git a/docs/admin/hold_driven_recalls.adoc b/docs/admin/hold_driven_recalls.adoc index 05c60f8d2a..c2059c4898 100644 --- a/docs/admin/hold_driven_recalls.adoc +++ b/docs/admin/hold_driven_recalls.adoc @@ -36,10 +36,10 @@ of circulating items, library settings must be changed as follows: and maximum fine* setting. If set, this applies the specified fine rules to the current circulation period for the recalled item. -When a hold is placed and no available copies are found by the hold targeter, +When a hold is placed and no available items are found by the hold targeter, the recall logic checks to see if the recall threshold and return interval settings are set; if so, then the hold targeter checks the currently -checked-out copies to determine if any of the currently circulating items at +checked-out items to determine if any of the currently circulating items at the designated pickup library have a loan duration longer than the recall threshold. If so, then the eligible item with the due date nearest to the current date is recalled. diff --git a/docs/admin/librarysettings.adoc b/docs/admin/librarysettings.adoc index 4935ce35d1..37fce55408 100644 --- a/docs/admin/librarysettings.adoc +++ b/docs/admin/librarysettings.adoc @@ -79,11 +79,11 @@ values. |Allow funds to be rolled over without bringing money along|Allow funds to be rolled over without bringing the money along. This makes money left in the old fund disappear, modeling its return to some outside entity.|True/False| |Allows patrons to create automatic holds from purchase requests.|Allows patrons to create automatic holds from purchase requests.|True/False| |Default circulation modifier|Sets the default circulation modifier for use in acquisitions.|Text| -|Default copy location|Sets the default copy location(shelving location) for use in acquisitions.|Selection list| +|Default copy location|Sets the default item location(shelving location) for use in acquisitions.|Selection list| |Fund Spending Limit for Block|When the amount remaining in the fund, including spent money and encumbrances, goes below this percentage, attempts to spend from the fund will be blocked.|Number| |Fund Spending Limit for Warning|When the amount remaining in the fund, including spent money and encumbrances, goes below this percentage, attempts to spend from the fund will result in a warning to the staff.|Number| |Rollover Distribution Formulae Funds|During fiscal rollover, update distribution formulae to use new funds|True/False| -|Set copy creator as receiver|When receiving a copy in acquisitions, set the copy "creator" to be the staff that received the copy|True/False| +|Set copy creator as receiver|When receiving am item in acquisitions, set the item "creator" to be the staff that received the item|True/False| |Temporary barcode prefix|Temporary barcode prefix added to temporary item records.|Text| |Temporary call number prefix|Temporary call number prefix|Text| |Upload Activate PO|Activate the purchase order by default during ACQ file upload|True/False| @@ -111,11 +111,11 @@ values. |Allow email notify|Permit email notification when a reservation is ready for pick-up.|True/false| |Elbow room|Elbow room specifies how far in the future you must make a reservation on an item if that item will have to transit to reach its pick-up location. It secondarily defines how soon a reservation on a given item must start before the check-in process will opportunistically capture it for the reservation shelf.|Duration| |Default Classification Scheme|Defines the default classification scheme for new call numbers: 1 = Generic; 2 = Dewey; 3 = LC|Number|It has effect on call number sorting. -|Default copy status (fast add)|Default status when a copy is created using the "Fast Item Add" interface.|Selection list|Default: In process -|Default copy status (normal)|Default status when a copy is created using the normal volume/copy creator interface.|Selection list| +|Default copy status (fast add)|Default status when an item is created using the "Fast Item Add" interface.|Selection list|Default: In process +|Default copy status (normal)|Default status when an item is created using the normal volume/copy creator interface.|Selection list| |Defines the control number identifier used in 003 and 035 fields||Text| -|Delete bib if all copies are deleted via Acquisitions line item cancellation.||True/False| -|Delete volume with last copy|Automatically delete a volume when the last linked copy is deleted.|True/False|Default TRUE +|Delete bib if all items are deleted via Acquisitions line item cancellation.||True/False| +|Delete volume with last copy|Automatically delete a volume when the last linked item is deleted.|True/False|Default TRUE |Maximum Parallel Z39.50 Batch Searches|The maximum number of Z39.50 searches that can be in-flight at any given time when performing batch Z39.50 searches|Number| |Maximum Z39.50 Batch Search Results|The maximum number of search results to retrieve and queue for each record + Z39 source during batch Z39.50 searches|Number| |Spine and pocket label font family|Set the preferred font family for spine and pocket labels. You can specify a list of fonts, separated by commas, in order of preference; the system will use the first font it finds with a matching name. For example, "Arial, Helvetica, serif".|Text| @@ -172,8 +172,8 @@ values. |Suppress hold transits group|To create a group of libraries to suppress Hold Transits among them. All libraries in the group should use the same unique value. Leave it empty if transits should not be suppressed.|Text| |Suppress non-hold transits group|To create a group of libraries to suppress Non-Hold Transits among them. All libraries in the group should use the same unique value. Leave it empty if Non-Hold Transits should not be suppressed.|Text| |Suppress popup-dialogs during check-in.|When set to True, no pop-up window for exceptions on check-in. But the accompanying sound will be played.|True/False| -|Target copies for a hold even if copy's circ lib is closed|If this setting is true at a given org unit or one of its ancestors, the hold targeter will target copies from this org unit even if the org unit is closed (according to the Org Unit's closed dates.).|True/False|Set the value to True if you want to target copies for holds at closed circulating libraries. Set the value to False, or leave it unset, if you do not want to enable this feature. -|Target copies for a hold even if copy's circ lib is closed IF the circ lib is the hold's pickup lib|If this setting is true at a given org unit or one of its ancestors, the hold targeter will target copies from this org unit even if the org unit is closed (according to the Org Unit's closed dates) IF AND ONLY IF the copy's circ lib is the same as the hold's pickup lib.|True/False| Set the value to True if you want to target copies for holds at closed circulating libraries when the circulating library of the item and the pickup library of the hold are the same. Set the value to False, or leave it unset, if you do not want to enable this feature. +|Target copies for a hold even if copy's circ lib is closed|If this setting is true at a given org unit or one of its ancestors, the hold targeter will target items from this org unit even if the org unit is closed (according to the Org Unit's closed dates.).|True/False|Set the value to True if you want to target items for holds at closed circulating libraries. Set the value to False, or leave it unset, if you do not want to enable this feature. +|Target copies for a hold even if copy's circ lib is closed IF the circ lib is the hold's pickup lib|If this setting is true at a given org unit or one of its ancestors, the hold targeter will target items from this org unit even if the org unit is closed (according to the Org Unit's closed dates) IF AND ONLY IF the item's circ lib is the same as the hold's pickup lib.|True/False| Set the value to True if you want to target items for holds at closed circulating libraries when the circulating library of the item and the pickup library of the hold are the same. Set the value to False, or leave it unset, if you do not want to enable this feature. |Truncate fines to max fine amount||True/False|Default:TRUE |Use Lost and Paid copy status|Use Lost and Paid copy status when lost or long overdue billing is paid|True/False| |Void Long-Overdue Item Billing When Returned||True/False| @@ -231,7 +231,7 @@ values. |Default item price|Replacement charge for lost items if price is unset in the *Copy Editor*. Does not apply if item price is set to $0|Number(dollars)| |Disable Patron Credit|Do not allow patrons to accrue credit or pay fines/fees with accrued credit|True/False| |Leave transaction open when long overdue balance equals zero|Leave transaction open when long-overdue balance equals zero. This leaves the long-overdue copy on the patron record when it is paid|True/False| -|Leave transaction open when lost balance equals zero|Leave transaction open when lost balance equals zero. This leaves the lost copy on the patron record when it is paid|True/False| +|Leave transaction open when lost balance equals zero|Leave transaction open when lost balance equals zero. This leaves the lost item on the patron record when it is paid|True/False| |Long-Overdue Materials Processing Fee|The amount charged in addition to item price when an item is marked Long-Overdue|Number|Currency |Lost materials processing fee|The amount charged in addition to item price when an item is marked lost.| Number|Currency |Maximum Item Price|When charging for lost items, limit the charge to this as a maximum.|Number|Currency @@ -255,7 +255,7 @@ values. [options="header",separator="!"] !=========================== !Setting!Description!Data type!Notes -!Alert on empty bib records!Alert staff when the last copy for a record is being deleted.!True/False! +!Alert on empty bib records!Alert staff when the last item for a record is being deleted.!True/False! !Button bar!If TRUE, the staff client button bar appears by default on all workstations registered to your library; staff can override this setting at each login.!True/False! !Cap results in Patron Search at this number.!The maximum number of results returned per search. If 100 is set up here, any search will return 100 records at most.!Number! !Default Country for New Addresses in Patron Editor!This is the default Country for new addresses in the patron editor.!Text! @@ -340,15 +340,15 @@ values. |FIFO|Force holds to a more strict First-In, First-Out capture. Default is SAVE-GAS, which gives priority to holds with pickup location the same as checkin library.|True/False|Applies only to multi-branch libraries. Default is SAVE-GAS. |Hard boundary||Number| |Hard stalling interval||Duration| -|Has local copy alert|If there is an available copy at the requesting library that could fulfill a hold during hold placement time, alert the patron.|True/False| -|Has local copy block|If there is an available copy at the requesting library that could fulfill a hold during hold placement time, do not allow the hold to be placed.|True/False| -|Max foreign-circulation time|Time a copy can spend circulating away from its circ lib before returning there to fill a hold|Duration|For multi-branch libraries. -|Maximum library target attempts|When this value is set and greater than 0, the system will only attempt to find a copy at each possible branch the configured number of times|Number|For multi-branch libraries. +|Has local copy alert|If there is an available item at the requesting library that could fulfill a hold during hold placement time, alert the patron.|True/False| +|Has local copy block|If there is an available item at the requesting library that could fulfill a hold during hold placement time, do not allow the hold to be placed.|True/False| +|Max foreign-circulation time|Time a item can spend circulating away from its circ lib before returning there to fill a hold|Duration|For multi-branch libraries. +|Maximum library target attempts|When this value is set and greater than 0, the system will only attempt to find a item at each possible branch the configured number of times|Number|For multi-branch libraries. |Minimum estimated wait|When predicting the amount of time a patron will be waiting for a hold to be fulfilled, this is the minimum estimated length of time to assume an item will be checked out.|Duration | -|Org unit target weight|Org Units can be organized into hold target groups based on a weight. Potential copies from org units with the same weight are chosen at random.|Number| +|Org unit target weight|Org Units can be organized into hold target groups based on a weight. Potential items from org units with the same weight are chosen at random.|Number| |Reset request time on un-cancel|When a hold is uncancelled, reset the request time to push it to the end of the queue|True/False| -|Skip for hold targeting|When true, don't target any copies at this org unit for holds|True/False| -|Soft boundary|Holds will not be filled by copies outside this boundary if there are holdable copies within it.|Number | +|Skip for hold targeting|When true, don't target any items at this org unit for holds|True/False| +|Soft boundary|Holds will not be filled by items outside this boundary if there are holdable items within it.|Number | |Soft stalling interval|For this amount of time, holds will not be opportunistically captured at non-pickup branches.|Duration| For multiple branch libraries |Use Active Date for age protection|When calculating age protection rules use the Active date instead of the Creation Date.|True/False|Default TRUE @@ -364,7 +364,7 @@ For multiple branch libraries |Setting|Description|Data type|Notes |Change reshelving status interval|Amount of time to wait before changing an item from “Reshelving” status to “available”|Duration| The default is at midnight each night for items with "Reshelving" status for over 24 hours. -|Claim never checked out: mark copy as missing|When a circ is marked as claims-never-checked-out, mark the copy as missing|True/False| +|Claim never checked out: mark copy as missing|When a circ is marked as claims-never-checked-out, mark the item as missing|True/False| |Claim return copy status|Claims returned copies are put into this status. Default is to leave the copy in the Checked Out status|Selection list| |Courier code|Courier Code for the library. Available in transit slip templates as the %courier_code% macro.|Text| |Juvenile age threshold|Upper cut-off age for patrons to be considered juvenile, calculated from date of birth in patron accounts|Duration (years)| diff --git a/docs/admin/phonelist.adoc b/docs/admin/phonelist.adoc index a54f04234c..bb617c8b5b 100644 --- a/docs/admin/phonelist.adoc +++ b/docs/admin/phonelist.adoc @@ -102,7 +102,7 @@ afternoon and there was no new information to gather. The program does indicate that it has already looked at a particular hold or overdue and will skip it on later runs. This prevents duplicates to the same patron in the same run. It will, however, -create a `duplicate` for the same patron if a different copy is put +create a `duplicate` for the same patron if a different item is put on hold for that patron in between two runs. The specific content of the CSV file will vary if you are looking at @@ -112,7 +112,7 @@ appropriate sections below. Holds ----- -The `phonelist` program will return a list of patrons with copies on +The `phonelist` program will return a list of patrons with items on hold by default, so long as you do not use the `overdue` parameter. You may optionally get a number of items that patron currently has on hold by adding the `addcount` parameter. @@ -127,15 +127,15 @@ patrons with email notification of holds>> as described below. | Name | Patron's name first and last. | Phone | Patron's phone number. | Barcode | Patron's barcode. -| Count | Number of copies on hold, if `addcount` parameter is used, otherwise this column is not present in the file. +| Count | Number of items on hold, if `addcount` parameter is used, otherwise this column is not present in the file. |===================================== Overdues -------- If you add the `overdue` parameter, you can get a list of patrons with -overdue copies instead of a list of patrons with copies on the hold -shelf. By default, this will give you a list of patrons with copies +overdue items instead of a list of patrons with items on the hold +shelf. By default, this will give you a list of patrons with items that are 14 days overdue. If you'd like to specify a different number of days you can add the number after the parameter with an equals sign: diff --git a/docs/admin/sitemap_admin.adoc b/docs/admin/sitemap_admin.adoc index 50bcd82186..f6bfdff8ca 100644 --- a/docs/admin/sitemap_admin.adoc +++ b/docs/admin/sitemap_admin.adoc @@ -23,7 +23,7 @@ before running the script. Sitemap details ~~~~~~~~~~~~~~~ -The sitemap generator script includes located URIs as well as copies +The sitemap generator script includes located URIs as well as items listed in the `asset.opac_visible_copies` materialized view, and checks the children or ancestors of the requested libraries for holdings as well. diff --git a/docs/admin_initial_setup/describing_your_people.adoc b/docs/admin_initial_setup/describing_your_people.adoc index 55c0f9f7f5..0258694838 100644 --- a/docs/admin_initial_setup/describing_your_people.adoc +++ b/docs/admin_initial_setup/describing_your_people.adoc @@ -306,7 +306,7 @@ WHERE ppl.code IN ('UPDATE_MARC', 'CREATE_MARC', 'IMPORT_MARC'); ------------------------------------------------------------------------------ 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 +out items 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): diff --git a/docs/admin_initial_setup/importing_via_staff_client.adoc b/docs/admin_initial_setup/importing_via_staff_client.adoc index 286f1797d0..294cb49cc2 100644 --- a/docs/admin_initial_setup/importing_via_staff_client.adoc +++ b/docs/admin_initial_setup/importing_via_staff_client.adoc @@ -15,7 +15,7 @@ of getting materials into Evergreen: Staff client batch record imports --------------------------------- -The staff client has a utility for importing batches of bibliographic and copy +The staff client has a utility for importing batches of bibliographic and item records available through *Cataloging > MARC Batch Import/Export*. In addition to importing new records, this interface can be used to match incoming records to existing records in the database, add or overlay MARC fields in the existing @@ -33,9 +33,9 @@ When to use the MARC Batch Importer * When importing in batches of up to 500 to 1,000 records. * When you need the system to match those incoming records to existing records and overlay or add fields to the existing record. -* When you need to add copies to existing records in the system. +* When you need to add items to existing records in the system. -WARNING: If you are importing copies that do not have barcodes or call numbers, you +WARNING: If you are importing items that do not have barcodes or call numbers, you must enable the _Vandelay Generate Default Barcodes_ and _Vandelay Default Barcode Prefix (vandelay.item.barcode.prefix)_ settings. @@ -100,16 +100,16 @@ image::media/record_quality_metrics.png[] Import Item Attributes ~~~~~~~~~~~~~~~~~~~~~~ -If you are importing copies with your records, you will need to map the data in -your holdings tag to fields in the copy record. Click the *Holdings Import +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. . Click the *New Definition* button to create a new mapping for the holdings tag. . Add a *Name* for the definition. . Use the *Tag* field to identify the MARC tag that contains your holdings information. -. Add the subfields that contain specific copy information to the appropriate - copy field. +. Add the subfields that contain specific item information to the appropriate + item field. . At a minimum, you should add the subfields that identify the *Circulating Library*, the *Owning Library*, the *Call Number* and the *Barcode*. . For more details, see the full list of import fields. @@ -160,7 +160,7 @@ records. . Click the *Import Records* button . Provide a unique name for the queue where the records will be loaded . Identify the match set that should be used for matching -. If you are importing copies, identify the *Import Item Attributes* definition +. If you are importing items, identify the *Import Item Attributes* definition in the Holdings Import Profile . Select a record source . Select the overlay/merge profile that defines which fields should be diff --git a/docs/admin_initial_setup/migrating_your_data.adoc b/docs/admin_initial_setup/migrating_your_data.adoc index 83d2286b70..f272d846ea 100644 --- a/docs/admin_initial_setup/migrating_your_data.adoc +++ b/docs/admin_initial_setup/migrating_your_data.adoc @@ -5,7 +5,7 @@ Introduction ------------ When you migrate to Evergreen, you generally want to migrate the bibliographic -records and copy information that existed in your previous library system. For +records and item information that existed in your previous library system. For anything more than a few thousand records, you should import the data directly into the database rather than use the tools in the staff client. While the data that you can extract from your legacy system varies widely, this section @@ -16,7 +16,7 @@ data formats so that you can then load the data into the database in bulk. Making electronic resources visible in the catalog -------------------------------------------------- -Electronic resources generally do not have any call number or copy information +Electronic resources generally do not have any call number or item information associated with them, and Evergreen enables you to easily make bibliographic records visible in the public catalog within sections of the organizational unit hierarchy. For example, you can make a set of bibliographic records @@ -147,17 +147,17 @@ and a label suffix. Label prefixes and suffixes do not affect the sort order of the label. 'Copies' connect call numbers to particular instances of that resource at a -particular library. Each copy has a barcode and must exist in a particular copy +particular library. Each item has a barcode and must exist in a particular item location. Other optional attributes of items include circulation modifier, -which may affect whether that copy can circulate or for how long it can -circulate, and OPAC visibility, which controls whether that particular copy +which may affect whether that item can circulate or for how long it can +circulate, and OPAC visibility, which controls whether that particular item should be visible in the public catalog. 'Parts' provide more granularity for items, primarily to enable patrons to place holds on individual parts of a set of items. For example, an encyclopedia might be represented by a single bibliographic record, with a single call number representing the label for that encyclopedia at a given library, with 26 -items representing each letter of the alphabet, with each copy mapped to a +items representing each letter of the alphabet, with each item mapped to a different part such as _A, B, C, ... Z_. To migrate this data into your Evergreen system, you will create another @@ -192,7 +192,7 @@ CREATE TABLE staging_materials ( For the purposes of this example migration of call numbers, items, and parts, we assume that you are able to create a tab-delimited file containing values -that map to the staging table properties, with one copy per line. For example, +that map to the staging table properties, with one item per line. For example, the following 5 lines demonstrate how the file could look for 5 different items, with non-applicable attribute values represented by _\N_, and 3 of the items connected to a single call number and bibliographic record via parts: @@ -217,7 +217,7 @@ COPY staging_items (bibkey, callnum, callnum_prefix, item_type, owning_lib, barcode, part) FROM 'holdings.tsv'; ------------------------------------------------------------------------------ -Generate the copy locations you need to represent your holdings: +Generate the item locations you need to represent your holdings: [source,sql] ------------------------------------------------------------------------------ diff --git a/docs/admin_initial_setup/ordering_materials.adoc b/docs/admin_initial_setup/ordering_materials.adoc index 71af69e26a..d5fb0a465c 100644 --- a/docs/admin_initial_setup/ordering_materials.adoc +++ b/docs/admin_initial_setup/ordering_materials.adoc @@ -17,7 +17,7 @@ When should libraries use acquisitions? * When you want to import large batches of records to quickly get your on-order titles into the system. -If your library simply wants to add on-order copies to the catalog so that +If your library simply wants to add on-order items to the catalog so that patrons can view and place holds on titles that have not yet arrived, acquisitions may be more than you need. Adding those on-order records via cataloging is a simpler option that works well for this use case. @@ -140,8 +140,8 @@ Providers are the vendors from whom you order titles. Distribution Formulas (Optional) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ If you are ordering for a multi-branch library system, distribution formulas -are a useful way to specify the number of copies that should be distributed to -specific branches and copy locations. +are a useful way to specify the number of items that should be distributed to +specific branches and item locations. . To create a distribution formula, select *Administration -> Acquisitions Administration -> Distribution Formulas*. Click the *New Formula* button. Enter @@ -161,10 +161,10 @@ acquisitions workflow. These settings can be found at *Administration -> Local Administration -> Library Settings Editor*. * Default circulation modifier - Automatically applies a default circulation - modifier to all of your acquisitions copies. Useful if you use a specific - circulation modifier for on-order copies. -* Default copy location - Automatically applies a default copy location (e.g. - On Order) to acquisitions copies. + modifier to all of your acquisitions items. Useful if you use a specific + circulation modifier for on-order items. +* Default copy location - Automatically applies a default item location (e.g. + On Order) to acquisitions items. * Temporary barcode prefix - Applies a unique prefix to the barcode that is automatically generated during the acquisitions process. * Temporary call number prefix - Applies a unique prefix to the start of the @@ -174,7 +174,7 @@ Preparing for order record loading ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ If your library is planning to upload order records in a batch, you need to add some information to your provider records so that Evergreen knows how to map -the copy data contained in the order record. +the item data contained in the order record. . Retrieve the record for the provider that has supplied the order records by selecting *Administration -> Acquisitions Administration -> Providers*. Click on diff --git a/docs/cataloging/batch_importing_MARC.adoc b/docs/cataloging/batch_importing_MARC.adoc index ca403cbbfa..c1c776db56 100644 --- a/docs/cataloging/batch_importing_MARC.adoc +++ b/docs/cataloging/batch_importing_MARC.adoc @@ -219,16 +219,16 @@ You can add multiple tags to the specification options, separating each tag with Import Item Attributes ~~~~~~~~~~~~~~~~~~~~~~ -If you are importing copies with your records, you will need to map the data in -your holdings tag to fields in the copy record. Click the *Holdings Import +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. . Click the *New Definition* button to create a new mapping for the holdings tag. . Add a *Name* for the definition. . Use the *Tag* field to identify the MARC tag that contains your holdings information. -. Add the subfields that contain specific copy information to the appropriate - copy field. +. Add the subfields that contain specific item information to the appropriate + item field. . At a minimum, you should add the subfields that identify the *Circulating Library*, the *Owning Library*, the *Call Number* and the *Barcode*. @@ -258,7 +258,7 @@ identify the MARC tag that contains your holdings information. |Deposit Amount || |Holdable || |OPAC Visible || -|Overlay Match ID || The copy ID of an existing copy to overlay +|Overlay Match ID || The copy ID of an existing item to overlay |Parts Data || Of the format `PART LABEL 1\|PART LABEL 2`. |Price || |Private Note || @@ -266,9 +266,9 @@ identify the MARC tag that contains your holdings information. |Reference || |Shelving Location || |Stat Cat Data || Of the format `CATEGORY 1\|VALUE 1\|\|CATEGORY 2\|VALUE 2`. -If you are overlaying existing copies which already have stat cats +If you are overlaying existing items which already have stat cats attached to them, the overlay process will keep those values unless the -incoming copies contain updated values for matching categories. +incoming items contain updated values for matching categories. |Status || |================== @@ -389,7 +389,7 @@ image::media/Batch_Importing_MARC_Records14.jpg[Batch_Importing_MARC_Records14] Default Values for Item Import ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Evergreen now supports additional functionality for importing items through *Cataloging* -> *MARC Batch Import/Export*. When items are imported via a *Holdings Import Profile* in *Cataloging* -> *MARC Batch Import/Export*, Evergreen will create an item-level record for each copy. If an item barcode, call number, copy location, or circulation modifier is not set in the embedded holdings, Evergreen will apply a default value based on the configured Library Settings. A default prefix can be applied to the auto-generated call numbers and item barcodes. +Evergreen now supports additional functionality for importing items through *Cataloging* -> *MARC Batch Import/Export*. When items are imported via a *Holdings Import Profile* in *Cataloging* -> *MARC Batch Import/Export*, Evergreen will create an item-level record for each copy. If an item barcode, call number, shelving location, or circulation modifier is not set in the embedded holdings, Evergreen will apply a default value based on the configured Library Settings. A default prefix can be applied to the auto-generated call numbers and item barcodes. The following *Library Settings* can be configured to apply these default values to imported items: diff --git a/docs/cataloging/cataloging_electronic_resources.adoc b/docs/cataloging/cataloging_electronic_resources.adoc index febb266bda..c4a2af90a7 100644 --- a/docs/cataloging/cataloging_electronic_resources.adoc +++ b/docs/cataloging/cataloging_electronic_resources.adoc @@ -1,7 +1,7 @@ Cataloging Electronic Resources -- Finding Them in Catalog Searches ------------------------------------------------------------------- There are two ways to make electronic resources visible in the catalog without -adding copies to the record: +adding items to the record: . Adding a Located URI to the record . Attaching the record to a bib source that is transcendent @@ -12,8 +12,8 @@ is useful if all libraries have access to the same electronic resources. Another difference between the two approaches is that electronic resources with Located URI's never appear in results where the search is limited to a specific -copy location(s). In contrast, transcendent electronic resources will appear in -results limited to any copy location. +shelving location(s). In contrast, transcendent electronic resources will appear in +results limited to any shelving location. Adding a Located URI to the Record ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ diff --git a/docs/cataloging/copy_tags_cataloging.adoc b/docs/cataloging/copy_tags_cataloging.adoc index 90b387bbdf..03c48866bc 100644 --- a/docs/cataloging/copy_tags_cataloging.adoc +++ b/docs/cataloging/copy_tags_cataloging.adoc @@ -3,19 +3,19 @@ Copy Tags Copy Tags allow staff to apply custom, pre-defined labels or tags to items. Copy tags are visible in the public catalog and are searchable in both the staff client and public catalog based on configuration. This feature was designed to be used for Digital Bookplates to attach donation or memorial information to items, but may be used for broader purposes to tag items. -Copy tags can be created ahead of time in the Administration module (See the Administration section of this documentation for more information.) and then applied to copies or they can be created on the fly during the cataloging process. +Copy tags can be created ahead of time in the Administration module (See the Administration section of this documentation for more information.) and then applied to items or they can be created on the fly during the cataloging process. -Adding Existing Copy Tags to Copies +Adding Existing Copy Tags to Items ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Copy Tags can be added to existing copies or to new copies as they are cataloged. To add a copy tag: +Copy Tags can be added to existing items or to new items as they are cataloged. To add a copy tag: . In the _Copy Editor_, click on *Copy Tags*. A dialog box called _Manage Copy Tags_ will appear. image::media/copytags5.PNG[] . Select the *Tag Type* from the drop down menu and start typing in the Tag field to bring up tag suggestions from the existing copy tags. Select the tag and click *Add Tag*, then click *OK*. -.. If you are cataloging a new copy, make any other changes to the item record. +.. If you are cataloging a new item, make any other changes to the item record. . Click *Save & Exit*. The copy tag will now appear in the catalog. image::media/copytags6.png[] @@ -31,10 +31,10 @@ Copy tags can be created in the Copy Editor on the fly while cataloging or view . Select the *Tag Type* from the drop down menu and type in the new Tag you want to apply to the item. Click *Add Tag*, then click *OK*. The new tag will be created and attached to the item. It will be owned by the organization unit your workstation is registered to. The tag can be modified under *Admin->Local Administration->Copy Tags*. -Removing Copy Tags from Copies +Removing Copy Tags from Items ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -To remove a copy tag from a copy: +To remove a copy tag from a item: . In the Copy Editor, click on *Copy Tags*. A dialog box called _Manage Copy Tags_ will appear. . Click *Remove* next to the tag you would like to remove, and click *OK*. @@ -43,14 +43,14 @@ To remove a copy tag from a copy: image::media/copytags8.PNG[] -Adding Copy Tags to Copies in Batch +Adding Copy Tags to Items in Batch ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Copy tags can be added to multiple copies in batch using _Copy Buckets_. After adding the items to a copy bucket: +Copy tags can be added to multiple items in batch using _Copy Buckets_. After adding the items to a copy bucket: . Go to *Cataloging->Copy Buckets->Bucket View* and select the bucket from the Buckets drop down menu. . Select the copies to which you want to add the copy tag and go to *Actions->Apply Tags* or right-click and select *Apply Tags*. The _Apply Copy Tags_ dialog box will appear. -. Select the *Tag Type* and enter the *Tag*. Click *Add Tag*, then click *OK*. The copy tag will now be attached to the copies. +. Select the *Tag Type* and enter the *Tag*. Click *Add Tag*, then click *OK*. The copy tag will now be attached to the items. image::media/copytags9.PNG[] -- 2.43.2