[open-ils-commits] ***SPAM*** [GIT] Evergreen ILS branch master updated. 028bde53833a7cca0e5dca483f03f4bb6d49495b

Evergreen Git git at git.evergreen-ils.org
Wed Mar 19 16:35: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  028bde53833a7cca0e5dca483f03f4bb6d49495b (commit)
       via  b70e768abe78289675e5967032644751eb5ee15a (commit)
      from  ade704b8a9bb64132fea036bc80a8a0ea920ee55 (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 028bde53833a7cca0e5dca483f03f4bb6d49495b
Author: Remington Steed <rjs7 at calvin.edu>
Date:   Wed Mar 19 15:56:44 2014 -0400

    Docs: Reformat numbered lists into AsciiDoc syntax
    
    This commit improves list formatting in the Batch Importing section by
    converting various hard-coded numbered lists into AsciiDoc syntax. Where
    images are included, those are forced to be inline by adding a '+' to the
    preceeding line. And whitespace was removed from the end of two lines. No
    other changes are included.
    
    Signed-off-by: Remington Steed <rjs7 at calvin.edu>

diff --git a/docs/cataloging/batch_importing_MARC.txt b/docs/cataloging/batch_importing_MARC.txt
index 71ffb11..0b63150 100644
--- a/docs/cataloging/batch_importing_MARC.txt
+++ b/docs/cataloging/batch_importing_MARC.txt
@@ -42,35 +42,33 @@ can add multiple record attributes and MARC tags to customize a record match
 set.
  
 
-1) Click *Cataloging -> MARC Batch Import/Export*.
+. Click *Cataloging -> MARC Batch Import/Export*.
 
-2) Create a new record match set.  Click *Record Match Sets -> New Match Set*.
+. Create a new record match set.  Click *Record Match Sets -> New Match Set*.
 
-3) Enter a name for the record match set.
+. Enter a name for the record match set.
 
-4) Select an *Owning Library* from the drop down menu.  Staff with permissions
+. Select an *Owning Library* from the drop down menu.  Staff with permissions
 at this location will be able to use this record match set.
 
-5) Select a *Match Set Type* from the drop down menu.  You can create a match
+. Select a *Match Set Type* from the drop down menu.  You can create a match
 set for authority records or bibliographic records.
 
-6) Click *Save*.
-
-
+. Click *Save*.
++
 image::media/Batch_Importing_MARC_Records1.jpg[Batch_Importing_MARC_Records1]
 
-
-7) The screen will refresh to list the record match set that you created. Click
+. The screen will refresh to list the record match set that you created. Click
 the link to the record match set.
 
-8) Create an expression that will define the match points for the incoming
+. Create an expression that will define the match points for the incoming
 record.  You can choose from two areas to create a match: *Record Attribute* or
 *MARC Tag and Subfield*.  You can use the Boolean operators AND and OR to
 combine these elements to create a match set.
 
-9) Select a *Record Attribute* from the drop-down menu.
+. Select a *Record Attribute* from the drop-down menu.
 
-10) Enter a *Match Score.*  The *Match Score* indicates the relative importance
+. Enter a *Match Score.*  The *Match Score* indicates the relative importance
 of that match point as Evergreen evaluates an incoming record against an
 existing record. You can enter any integer into this field.  The number that
 you enter is only important as it relates to other match points.  Recommended
@@ -78,42 +76,42 @@ practice is that you create a match score of one (1) for the least important
 match point and assign increasing match points to the power of 2 to working
 points in increasing importance.
 
-11) Check the *Negate?* box if you want to negate the match point. Checking
+. Check the *Negate?* box if you want to negate the match point. Checking
 this box would be the equivalent of applying a Boolean operator of NOT to the
 match point.
-
++
 image::media/Batch_Importing_MARC_Records2.jpg[Batch_Importing_MARC_Records2]
 
-12) Click *Ok.*
+. Click *Ok.*
 
-13) Drag the completed match point under the folder with the 
+. Drag the completed match point under the folder with the
 appropriately-named Boolean folder under the Expression tree.
-
++
 image::media/Batch_Importing_MARC_Records3.jpg[Batch_Importing_MARC_Records3]
-
++
 The match point will nest underneath the folder in the Expression tree.
-
++
 image::media/Batch_Importing_MARC_Records4.jpg[Batch_Importing_MARC_Records4]
 
-14) Enter another *Boolean Operator* to further refine your match set.
-
-15) Click *Boolean Operator*.
+. Enter another *Boolean Operator* to further refine your match set.
 
-16) Select the *OR* operator from the drop down menu.
+. Click *Boolean Operator*.
 
-17) Click *Ok*.
+. Select the *OR* operator from the drop down menu.
 
-18) Drag the operator to the expression tree.
+. Click *Ok*.
 
+. Drag the operator to the expression tree.
++
 image::media/Batch_Importing_MARC_Records5.jpg[Batch_Importing_MARC_Records5]
 
-19) Click *MARC Tag and Subfield*.
+. Click *MARC Tag and Subfield*.
 
-20) Enter a *MARC tag* on which you want the records to match.
+. Enter a *MARC tag* on which you want the records to match.
 
-21) Enter a *subfield* on which you want the records to match.
+. Enter a *subfield* on which you want the records to match.
 
-22) Enter a *Match Score.*  The *Match Score* indicates the relative importance
+. Enter a *Match Score.*  The *Match Score* indicates the relative importance
 of that match point as Evergreen evaluates an incoming record against an
 existing record. You can enter any integer into this field.  The number that
 you enter is only important as it relates to other match points.  Recommended
@@ -121,22 +119,22 @@ practice is that you create a match score of one (1) for the least important
 match point and assign increasing match points to the power of 2 to working
 points in increasing importance.
 
-23) Check the *Negate?* box if you want to negate the match point.  Checking
+. Check the *Negate?* box if you want to negate the match point.  Checking
 this box would be the equivalent of applying a Boolean operator of NOT to the
 match point.
 
-24) Click *Ok.*
-
+. Click *Ok.*
++
 image::media/Batch_Importing_MARC_Records6.jpg[Batch_Importing_MARC_Records6]
 
-25) Drag the completed match point under the folder with the
+. Drag the completed match point under the folder with the
 appropriately-named Boolean folder under the Expression tree. The Expression
 will build across the top of the screen.
 
-26) Add additional MARC tags or record attributes to build the expression tree.
-
-27) Click *Save Changes to Expression*.
+. Add additional MARC tags or record attributes to build the expression tree.
 
+. Click *Save Changes to Expression*.
++
 image::media/Batch_Importing_MARC_Records7.jpg[Batch_Importing_MARC_Records7]
 
 Replace Mode
@@ -146,21 +144,21 @@ Replace Mode enables you to replace an existing part of the expression tree
 with a new record attribute, MARC tag, or Boolean operator.  For example, if
 the top of the tree is AND, in replace mode, you could change that to an OR.
 
-1) Create a working match point.
+. Create a working match point.
 
-2) Click *Enter replace mode*.
+. Click *Enter replace mode*.
 
-3) Highlight the piece of the tree that you want to replace.
+. Highlight the piece of the tree that you want to replace.
 
-4) Drag the replacement piece over the highlighted piece.
+. Drag the replacement piece over the highlighted piece.
 
-5) Click *Exit Replace Mode*.
+. Click *Exit Replace Mode*.
 
 
 Quality Metrics
 ^^^^^^^^^^^^^^^
 
-1) Set the *Quality Metrics for this Match Set*.  Quality metrics are used to
+. Set the *Quality Metrics for this Match Set*.  Quality metrics are used to
 determine the overall quality of a record.  Each metric is given a weight and
 the total quality value for a record is equal to the sum of all metrics that
 apply to that record.  For example, a record that has been cataloged thoroughly
@@ -169,23 +167,23 @@ may want to ensure that the incoming record is of the same or better quality
 than the record that currently exists in your catalog; otherwise, you may want
 the match to fail.  The quality metric is optional.
 
-2) You can create quality metrics based on the record attribute or the MARC Tag
+. You can create quality metrics based on the record attribute or the MARC Tag
 and Subfield.
 
-3) Click *Record Attribute.*
+. Click *Record Attribute.*
 
-4) Select an attribute from the drop down menu.
+. Select an attribute from the drop down menu.
 
-5) Enter a value for the attribute.
+. Enter a value for the attribute.
 
-6.) Enter a match score.  You can enter any integer into this field. The number
+. Enter a match score.  You can enter any integer into this field. The number
 that you enter is only important as it relates to other quality values for the
 current configuration.  Higher scores would indicate increasing quality of
 incoming records. You can, as in the expression match score, increase the
 quality points by increasing subsequent records by a power of 2 (two).
 
-7) Click *Ok*.  
-
+. Click *Ok*.
++
 image::media/Batch_Importing_MARC_Records8.jpg[Batch_Importing_MARC_Records8]
 
 Import Records
@@ -311,5 +309,3 @@ The following *Library Settings* can be configured to apply these default values
 
 * *Vandelay: Default Circulation Modifier* —Default circulation modifier value for imported items
 
-
-

commit b70e768abe78289675e5967032644751eb5ee15a
Author: Remington Steed <rjs7 at calvin.edu>
Date:   Mon Jan 13 09:44:55 2014 -0500

    Document new 2.5 feature in Acq docs
    
    This commit adds documentation in two places for the new Acq feature
    "Opportunistic Acquisitions In-Process Copy Overlay". First, a short
    note is added to the "Load MARC Order Records" doc. Second, the feature
    is described more thoroughly in the "Batch Importing MARC Records" doc.
    Also, this commit cleans up a hard-coded ordered list and a few small
    wording and formatting problems.
    
    Signed-off-by: Remington Steed <rjs7 at calvin.edu>

diff --git a/docs/acquisitions/vandelay_acquisitions_integration.txt b/docs/acquisitions/vandelay_acquisitions_integration.txt
index 59620d6..b1f98a1 100644
--- a/docs/acquisitions/vandelay_acquisitions_integration.txt
+++ b/docs/acquisitions/vandelay_acquisitions_integration.txt
@@ -15,10 +15,10 @@ For detailed instructions on record matching and importing, see
 Basic Upload Options
 ~~~~~~~~~~~~~~~~~~~~
 . Click *Acquisitions* -> *Load MARC Order Records*.
-. If you want to upload the MARC records to a new purchase order, then click
-the check box adjacent to Create Purchase Order.
+. If you want to upload the MARC records to a new purchase order, then
+check _Create Purchase Order_.
 . If you want to activate the purchase order at the time of creation, then
-click the check box adjacent to _Activate Purchase Order_.
+check _Activate Purchase Order_.
 . Enter the name of the *Provider*. The text will auto-complete.
 . Select an org unit from the drop down menu. The context org unit is the org
 unit responsible for placing and managing the order. It defines what org unit
@@ -57,7 +57,7 @@ the following options.
   .. *Merge on Best Match* - If more than one match is found in the catalog for
   a given record, Evergreen will attempt to perform the best match as defined
   by the match score.
-. To only import records that has a quality equal to or greater than the
+. To only import records that have a quality equal to or greater than the
 existing record, enter a *Best/Single Match Minimum Quality Ratio*.  Divide the
 incoming record quality score, as determined by the match set's quality
 metrics, by the record quality score of the best match that exists in the 
@@ -73,8 +73,9 @@ profile that allows the user to import holdings attached to a lower quality
 record without replacing the existing (target) record with the incoming record.
 This field is optional.
 . If your order records contain holdings information, by default, Evergreen 
-will load them as acquisitions copies. Select *Load Items for Imported Records*
-to automatically load them as live copies that display in the catalog.
+will load them as acquisitions copies. (Note: These can be overlayed with real copies
+during the MARC batch importing process.) Or you can select *Load Items for
+Imported Records* to load them as live copies that display in the catalog.
 
 Default Upload Settings
 ~~~~~~~~~~~~~~~~~~~~~~~
diff --git a/docs/cataloging/batch_importing_MARC.txt b/docs/cataloging/batch_importing_MARC.txt
index e024a17..71ffb11 100644
--- a/docs/cataloging/batch_importing_MARC.txt
+++ b/docs/cataloging/batch_importing_MARC.txt
@@ -199,38 +199,37 @@ incoming record.  We will import the record according to the guidelines set by
 our record match set, quality metrics, and merge/overlay choices that we will
 select.
 
+. Select a *Record Type* from the drop down menu.
 
-1) Select a *Record Type* from the drop down menu.
-
-2) Create a queue to which you can upload your records, or add you records to
+. Create a queue to which you can upload your records, or add you records to
 an existing queue.  Queues are linked to match sets and a holdings import
 profile. You cannot change a holdings import or record match set for a queue.
 
-3) Select a *Record Match Set* from the drop down menu.
+. Select a *Record Match Set* from the drop down menu.
 
-4) Select a *Holdings Import Profile* if you want to import holdings that are
+. Select a *Holdings Import Profile* if you want to import holdings that are
 attached to your records.
 
-5) Select a *Record Source* from the drop down menu.
+. Select a *Record Source* from the drop down menu.
 
-6) Select a *Merge Profile*.  Merge profiles enable you to specify which tags
+. Select a *Merge Profile*.  Merge profiles enable you to specify which tags
 should be removed or preserved in incoming records.
 
-7) Choose one of the following import options if you want to auto-import
+. Choose one of the following import options if you want to auto-import
 records:
 
-a. *Merge on Single Match* - Using the Record Match Set, Evergreen will only
+.. *Merge on Single Match* - Using the Record Match Set, Evergreen will only
 attempt to perform the merge/overlay action if only one match was found in the
 catalog.
 
-b. *Merge on Best Match* - If more than one match is found in the catalog for a
+.. *Merge on Best Match* - If more than one match is found in the catalog for a
 given record, Evergreen will attempt to perform the merge/overlay action with
 the best match as defined by the match score and quality metric.
-
++
 NOTE: Quality ratio affects only the *Merge on Single Match* and *Merge on Best
 Match* options.
 
-8) Enter a *Best/Single Match Minimum Quality Ratio.*  Divide the incoming
+. Enter a *Best/Single Match Minimum Quality Ratio.*  Divide the incoming
 record quality score by the record quality score of the best match that might
 exist in the catalog.  By default, Evergreen will assign any record a quality
 score of 1 (one).  If you want to ensure that the inbound record is only
@@ -240,8 +239,7 @@ have twice the quality of an existing record, then you should enter a 2 (two)
 in this field.  If you want to bypass all quality restraints, enter a 0 (zero)
 in this field.
 
-
-9) Select an *Insufficient Quality Fall-Through Profile* if desired.  This
+. Select an *Insufficient Quality Fall-Through Profile* if desired.  This
 field enables you to indicate that if the inbound record does not meet the
 configured quality standards, then you may still import the record using an
 alternate merge profile.  This field is typically used for selecting a merge
@@ -249,40 +247,48 @@ profile that allows the user to import holdings attached to a lower quality
 record without replacing the existing (target) record with the incoming record.
 This field is optional.  
 
-10) *Browse* to find the appropriate file, and click *Upload*.  The files will
-be uploaded to a queue.
+. Under *Copy Import Actions*, choose _Auto-overlay In-process Acquisitions
+Copies_ if you want to overlay temporary copies that were created by the
+Acquisitions module.  The system will attempt to overlay copies that:
 
-image::media/Batch_Importing_MARC_Records9.jpg[Batch_Importing_MARC_Records9]
+* have associated lineitem details (that is, they were created by the acquisitions process),
+* that lineitem detail has the same owning_lib as the incoming copy's owning_lib, and
+* the current copy associated with that lineitem detail is _In process_.
 
-11) The screen will display records that have been uploaded to your queue.
-  
+. *Browse* to find the appropriate file, and click *Upload*.  The files will
+be uploaded to a queue.
++
+image::media/marc_batch_import_acq_overlay.png[Batch Importing MARC Records]
+
+. The screen will display records that have been uploaded to your queue.
++
 image::media/Batch_Importing_MARC_Records15.jpg[Batch_Importing_MARC_Records15]
 
-12) If Evergreen indicates that matching records exist, then click the
+. If Evergreen indicates that matching records exist, then click the
 *Matches* link to view the matching records.  Check the box adjacent to the
 existing record that you want to merge with the incoming record. 
-
++
 image::media/Batch_Importing_MARC_Records10.jpg[Batch_Importing_MARC_Records10]
 
-13) Click *Back to Import Queue*.
+. Click *Back to Import Queue*.
 
-14) Check the boxes of the records that you want to import, and click *Import
+. Check the boxes of the records that you want to import, and click *Import
 Selected Records*, or click *Import All Records*.
 
-15) A pop up window will offer you the same import choices that were present on
+. A pop up window will offer you the same import choices that were present on
 the *Import Records* screen.  You can choose one of the import options, or
 click *Import*.
++
+image::media/marc_batch_import_popup.png[Batch Importing MARC Records Popup]
 
-image::media/Batch_Importing_MARC_Records9.jpg[Batch_Importing_MARC_Records9]
-
-16) The screen will refresh.  The *Queue Summary* indicates that the record was
+. The screen will refresh.  The *Queue Summary* indicates that the record was
 imported.  The *Import Time* column records the date that the record was
 imported.
-
++
 image::media/Batch_Importing_MARC_Records12.jpg[Batch_Importing_MARC_Records12] 
 
-17) Search the catalog to confirm that the record was imported.
-
+. Search the catalog to confirm that the record was imported.
++
 image::media/Batch_Importing_MARC_Records14.jpg[Batch_Importing_MARC_Records14] 
 
 

-----------------------------------------------------------------------

Summary of changes:
 .../vandelay_acquisitions_integration.txt          |   13 +-
 docs/cataloging/batch_importing_MARC.txt           |  166 ++++++++++----------
 2 files changed, 91 insertions(+), 88 deletions(-)


hooks/post-receive
-- 
Evergreen ILS


More information about the open-ils-commits mailing list