[open-ils-commits] ***SPAM*** [GIT] Evergreen ILS branch master updated. 07e00d082410670d33606720b7f077cd8fa31257
Evergreen Git
git at git.evergreen-ils.org
Thu Aug 7 17:46:07 EDT 2014
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Evergreen ILS".
The branch, master has been updated
via 07e00d082410670d33606720b7f077cd8fa31257 (commit)
from 50c39d81e9f9404b2d9835c1c24e3f6ea22556f9 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 07e00d082410670d33606720b7f077cd8fa31257
Author: Yamil Suarez <yamil at yamil.com>
Date: Thu Aug 7 17:40:41 2014 -0400
Docs: various AsciiDoc formatting fixes for docs
Fixed the 'bad first character' error, the bad apostrophe error. Removed various UTF-8 chars.
Fixed some numbered list formatting, to take out redundant manual numerals…
for example:
. 1 item
. 2 item
. 3 item
became:
. item
. item
. item
also added "=" to wrap around breaks in numbered lists
for example:
. Right-click on the value control for the fixed field that needs to be edited.
image::media/ffrc1.jpg[]
. Select the appropriate value for the fixed field from the menu options.
became:
. Right-click on the value control for the fixed field that needs to be edited.
+
image::media/ffrc1.jpg[]
+
. Select the appropriate value for the fixed field from the menu options.
Signed-off-by: Yamil Suarez <yamil at yamil.com>
diff --git a/docs/admin/MARC_RAD_MVF_CRA.txt b/docs/admin/MARC_RAD_MVF_CRA.txt
index 05aae81..db15401 100644
--- a/docs/admin/MARC_RAD_MVF_CRA.txt
+++ b/docs/admin/MARC_RAD_MVF_CRA.txt
@@ -1,4 +1,4 @@
-MARC Record Attributes
+MARC Record Attributes
----------------------
The MARC Record Attribute Definitions support the ingesting, indexing, searching, filtering, and delivering of bibliographic record attributes.
@@ -19,11 +19,11 @@ image::media/radmvcolumn_1.jpg[]
To edit an existing record attribute definition and set the *Multi-valued?* field to *True*:
-. 1 Click *Admin* on the menu bar
-. 2 Hover over *Server Administration* and click *MARC Record Attributes*
-. 3 Double-click on the row of the record attribute definition that needs to be edited
-. 4 Select the *Multi-valued?* checkbox
-. 5 Click *Save*
+. Click *Admin* on the menu bar
+. Hover over *Server Administration* and click *MARC Record Attributes*
+. Double-click on the row of the record attribute definition that needs to be edited
+. Select the *Multi-valued?* checkbox
+. Click *Save*
image::media/editrad_2.jpg[]
@@ -45,11 +45,11 @@ Within the Coded Value Maps screen, there is a column named *Composite Definitio
To edit an existing record attribute definition and set the *Composite attribute?* field to True:
-. 1 Click *Admin* on the menu bar
-. 2 Hover over *Server Administration* and click *MARC Record Attributes*
-. 3 Double-click on the row of the record attribute definition that needs to be edited
-. 4 Select the *Composite attribute?* checkbox
-. 5 Click *Save*
+. Click *Admin* on the menu bar
+. Hover over *Server Administration* and click *MARC Record Attributes*
+. Double-click on the row of the record attribute definition that needs to be edited
+. Select the *Composite attribute?* checkbox
+. Click *Save*
image::media/radcatrue_5.jpg[]
@@ -68,13 +68,13 @@ To modify the *Composite Attribute Entry Definition*, any Boolean Operator can b
To modify the *Composite Attribute Entry Definition*:
-. 1 Click *Add Child* for the specific Boolean Operator that needs to be modified, and a new window will open
-. 2 Select which *Record Attribute* needs to be represented in the structure under that particular Boolean Operator
-. 3 Select the *Attribute Type* from the dropdown options
-. 4 Select the *Value* of the Attribute Type from the dropdown options (dropdown options will be based on the Attribute Type selected)
-. 5 Click *Submit*
-. 6 The *Composite Data Expression* should now include the modification
-. 7 Once all modifications have been made, click *Save Changes* on the Composite Attribute Entry Definitions page
+. Click *Add Child* for the specific Boolean Operator that needs to be modified, and a new window will open
+. Select which *Record Attribute* needs to be represented in the structure under that particular Boolean Operator
+. Select the *Attribute Type* from the dropdown options
+. Select the *Value* of the Attribute Type from the dropdown options (dropdown options will be based on the Attribute Type selected)
+. Click *Submit*
+. The *Composite Data Expression* should now include the modification
+. Once all modifications have been made, click *Save Changes* on the Composite Attribute Entry Definitions page
image::media/modifycde_7.jpg[]
diff --git a/docs/cataloging/MARC_Fixed_Field.txt b/docs/cataloging/MARC_Fixed_Field.txt
index b363e5f..8ae9c60 100644
--- a/docs/cataloging/MARC_Fixed_Field.txt
+++ b/docs/cataloging/MARC_Fixed_Field.txt
@@ -1,21 +1,23 @@
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. For the fixed fields that do not already contain possible values in the database, the user will see the basic clipboard operation options (such as cut, copy, paste, etc.).
+
*To Access the MARC Fixed Field Editor Right-Click Context Menu Options:*
-. 1 Within the bibliographic record that needs to be edited, select *Actions for this Record*.
-. 2 Click *MARC Edit*.
-. 3 Make sure that the Flat-Text Editor checkbox is not selected and that you are not using the Flat-Text Editor interface.
-. 4 Right-click on the value control for the fixed field that needs to be edited.
+. Within the bibliographic record that needs to be edited, select *Actions for this Record*.
+. Click *MARC Edit*.
+. Make sure that the Flat-Text Editor checkbox is not selected and that you are not using the Flat-Text Editor interface.
+. Right-click on the value control for the fixed field that needs to be edited.
++
image::media/ffrc1.jpg[]
-
-. 5 Select the appropriate value for the fixed field from the menu options.
-
++
+. Select the appropriate value for the fixed field from the menu options.
++
image::media/ffrc2.jpg[]
-
-. 6 Continue editing the MARC record, as needed. Once you are finished editing the record, click *Save Record*.
++
+. Continue editing the MARC record, as needed. Once you are finished editing the record, click *Save Record*.
Changing the values in the fixed fields will also update the appropriate position in the Leader or 008 Field and other applicable fields (such as the 006 Field).
@@ -30,9 +32,10 @@ It may be necessary for MARC Editor users to first correctly pad the fixed field
*Administration*
The Evergreen database already contains information from the Library of Congress’s MARC 21 format standards that includes possible values for select fixed fields. Users may also add values to these and other fixed fields through the MARC Coded Value Maps interface. Once new values are added, the right-click context menu for the selected fixed field will display those values in the MARC Editor for any Record Type that utilizes that fixed field.
There are three relevant tables that contain the values that display in the fixed field context menu options:
-. 1 *config.marc21_ff_pos_map* describes, for the given record type, where a fixed field is located, its start position, and its length.
-. 2 *config.coded_value_map* defines the set of valid values for many of the fixed fields and the translatable, human-friendly labels for them.
-. 3 *config.record_attr_definition* links together the information from the config.marc21_ff_pos_map and config.coded_value_map tables.
+
+. *config.marc21_ff_pos_map* describes, for the given record type, where a fixed field is located, its start position, and its length.
+. *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.
diff --git a/docs/cataloging/physical_char_wizard.txt b/docs/cataloging/physical_char_wizard.txt
index 59054e8..f4deb2b 100644
--- a/docs/cataloging/physical_char_wizard.txt
+++ b/docs/cataloging/physical_char_wizard.txt
@@ -1,22 +1,23 @@
-MARC 007 Field Physical Characteristics Wizard
+MARC 007 Field Physical Characteristics Wizard
-----------------------------------------------
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.
*To Access the MARC 007 Field Physical Characteristics Wizard for a Record that Does Not Already Contain the 007 Field (i.e. Creating the 007 Field from Scratch):*
-. 1 Within the bibliographic record that needs to be edited, select *Actions for this Record*.
-. 2 Click *MARC Edit*.
-. 3 Make sure that the Flat-Text Editor checkbox is not selected and that you are not using the Flat-Text Editor interface.
-. 4 Right-click in the MARC field column.
+. Within the bibliographic record that needs to be edited, select *Actions for this Record*.
+. Click *MARC Edit*.
+. Make sure that the Flat-Text Editor checkbox is not selected and that you are not using the Flat-Text Editor interface.
+. Right-click in the MARC field column.
++
image::media/pcw1.jpg[]
-
-. 5 Click *Add/Replace 007*. The 007 row will appear in the record.
-. 6 Right-click in the 007 textbox field.
-
++
+. Click *Add/Replace 007*. The 007 row will appear in the record.
+. Right-click in the 007 textbox field.
++
image::media/pcw2.jpg[]
-
-. 7 Click *Physical Characteristics Wizard*.
++
+. Click *Physical Characteristics Wizard*.
image::media/pcw3.jpg[]
@@ -55,20 +56,21 @@ Continue editing the MARC record, as needed. Once the user is finished editing t
image::media/pcw9.jpg[]
*To Access the MARC 007 Field Physical Characteristics Wizard for a Record that Already Contains the 007 Field (i.e. Edit an Existing 007 Field):*
-. 1 Within the bibliographic record that needs to be edited, select *Actions for this Record*.
-. 2 Click *MARC Edit*.
-. 3 Right-click in the 007 textbox field.
-. 4 Click *Physical Characteristics Wizard*.
+. Within the bibliographic record that needs to be edited, select *Actions for this Record*.
+. Click *MARC Edit*.
+. Right-click in the 007 textbox field.
+. Click *Physical Characteristics Wizard*.
++
image::media/pcw10.jpg[]
-
-. 5 Click the *Previous* and *Next* buttons to navigate forward and backward through the various positions. The current position that the wizard is on will be indicated by bold font.
-. 6 Each position will display a label that describes the significance of that position. For the position that needs to be edited, choose its appropriate value from the dropdown options.
-
++
+. Click the *Previous* and *Next* buttons to navigate forward and backward through the various positions. The current position that the wizard is on will be indicated by bold font.
+. Each position will display a label that describes the significance of that position. For the position that needs to be edited, choose its appropriate value from the dropdown options.
++
image::media/pcw11.jpg[]
-
-. 7 Once all edits of the 007 field are made, click *OK*.
-. 8 After finishing all other edits to the MARC record, click *Save Record*.
++
+. Once all edits of the 007 field are made, click *OK*.
+. After finishing all other edits to the MARC record, click *Save Record*.
[NOTE]
If the user edits an existing 007 field that does not already account for the skipped positions, then Evergreen will not automatically generate where the skipped positions should be in the 007 field. It is recommended that users delete the existing 007 field and start with a new 007 field, to ensure that Evergreen appropriately accounts for the obsolete positions for the Category of Material selected.
@@ -76,9 +78,9 @@ If the user edits an existing 007 field that does not already account for the sk
*Administration*
The information driving the MARC 007 Field Physical Characteristics Wizard is already a part of the Evergreen database. This data can be customized by individual sites and / or updated when the Library of Congress dictates new values or positions in the 007 field.
There are three relevant tables where the information that drives the wizard is stored:
-. 1 *config.marc21_physical_characteristic_type_map* contains the list of materials, or values, for the positions of the 007 field.
-. 2 *config.marc21_physical_characteristic_subfield_map* contains rows that list the meaning of the various positions in the 007 field for each Category of Material.
-. 3 *config.marc21_physical_characteristic_value_map* lists all of the values possible for all of the positions in the config.marc21_physical_characteristic_subfield_map table.
+. *config.marc21_physical_characteristic_type_map* contains the list of materials, or values, for the positions of the 007 field.
+. *config.marc21_physical_characteristic_subfield_map* contains rows that list the meaning of the various positions in the 007 field for each Category of Material.
+. *config.marc21_physical_characteristic_value_map* lists all of the values possible for all of the positions in the config.marc21_physical_characteristic_subfield_map table.
diff --git a/docs/opac/tpac_meta_record_holds.txt b/docs/opac/tpac_meta_record_holds.txt
index 8cecc03..6d89551 100644
--- a/docs/opac/tpac_meta_record_holds.txt
+++ b/docs/opac/tpac_meta_record_holds.txt
@@ -1,4 +1,4 @@
-TPAC Metarecord Search and Metarecord Level Holds
+TPAC Metarecord Search and Metarecord Level Holds
-------------------------------------------------
Metarecords are compilations of individual bibliographic records that represent the same work. This compilation allows for several records to be represented on a single line on the TPAC search results page, which can help to reduce result duplications.
diff --git a/docs/serials/D-subscription-ASCV.txt b/docs/serials/D-subscription-ASCV.txt
index 1d07c94..390ec1e 100644
--- a/docs/serials/D-subscription-ASCV.txt
+++ b/docs/serials/D-subscription-ASCV.txt
@@ -19,7 +19,7 @@ image::media/ascv-sub.jpg[Creating a Subscription]
. Add new subscriptions to a serials record that exists in the catalog.
. Create a subscription
. Click New Subscription.
-. Select an owning library. The owning library indicates the organizational unit(s) whose staff can use this subscription. This menu is populated with the shortnames that you created for your libraries in the organizational units tree in Admin . Server Administration . Organizational Units. The rule of parental inheritance applies to this list. For example, if a system is made the owner of a subscription, then users, with appropriate permissions, at the branches within the system could also use this subscription.
+. Select an owning library. The owning library indicates the organizational unit(s) whose staff can use this subscription. This menu is populated with the shortnames that you created for your libraries in the organizational units tree in Admin -> Server Administration -> Organizational Units. The rule of parental inheritance applies to this list. For example, if a system is made the owner of a subscription, then users, with appropriate permissions, at the branches within the system could also use this subscription.
. Enter the date that the subscription begins in the start date. Recommended practice is that you select the date from the drop down calendar although you can manually enter a date. Owning library and start date are required fields in the new subscription pop up box.
. Enter the date that the subscription ends in the end date. Recommended practice is to select a date from the drop down calendar, but you can manually enter a date, also.
. Enter the difference between the nominal publishing date of an issue and the date that you expect to receive your copy in the Expected Date Offset. For example, if an issue is published the first day of each month, but you receive the copy two days prior to the publication date, then enter -2 days into this field.
@@ -68,25 +68,25 @@ Creating a Routing List
Within Alternate Serial Control View, you have the option to create routing lists for selected streams. Routing lists enable you to designate specific users and/or departments that serial items need to be routed to upon receiving. These routing lists can now display user addresses when you receive the items. This feature is particularly useful for working with homebound patrons.
-Create a Routing List in Alternate Serial Control View that will display the User’s Address:
+Create a Routing List in Alternate Serial Control View that will display the User's Address:
-. 1 Select the checkbox for the stream that needs a routing list
+. Select the checkbox for the stream that needs a routing list
-. 2 Click *Routing List for Selected Stream*
+. Click *Routing List for Selected Stream*
-. 3 Click the *Reader (barcode):* radio button and enter the user’s barcode into the field
+. Click the *Reader (barcode):* radio button and enter the user's barcode into the field
-. 4 Click *Add*
+. Click *Add*
-. 5 Click *Save Changes*
+. Click *Save Changes*
image::media/Added_User_to_Routing_Slip.jpg[]
-When you receive the item in *Serials Batch Receive* or from within Alternate Serial Control’s *Batch Item Receive*, the routing list will print the user’s address. For more information, see the chapter on Batch Receiving.
+When you receive the item in *Serials Batch Receive* or from within Alternate Serial Control's *Batch Item Receive*, the routing list will print the user's address. For more information, see the chapter on Batch Receiving.
image::media/Address_on_Routing_Slip.jpg[]
-The default template can be configured to not include the user’s mailing or billing address on the routing list. Libraries already using customized templates will not be affected.
+The default template can be configured to not include the user's mailing or billing address on the routing list. Libraries already using customized templates will not be affected.
Creating a Caption and Pattern
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -117,7 +117,7 @@ Page 1: Enumerations
image::media/cap-wiz-num.jpg[Enumeration]
-. To add an enumeration, check the box adjacent to Use enumerations.. The enumerations conform to $a-$h of the 853,854, and 855 MARC tags.
+. To add an enumeration, check the box adjacent to Use enumerations. The enumerations conform to $a-$h of the 853,854, and 855 MARC tags.
. A field for the First level will appear. Enter the enumeration for the first level. A common first level enumeration is volume, or "v."
. Click Add Enumeration.
. A field for the Second level will appear. Enter the enumeration for the second level. A common first level enumeration is number, or "no."
-----------------------------------------------------------------------
Summary of changes:
docs/admin/MARC_RAD_MVF_CRA.txt | 36 ++++++++++----------
docs/cataloging/MARC_Fixed_Field.txt | 29 +++++++++-------
docs/cataloging/physical_char_wizard.txt | 52 +++++++++++++++--------------
docs/opac/tpac_meta_record_holds.txt | 2 +-
docs/serials/D-subscription-ASCV.txt | 20 ++++++------
5 files changed, 72 insertions(+), 67 deletions(-)
hooks/post-receive
--
Evergreen ILS
More information about the open-ils-commits
mailing list