[open-ils-commits] [GIT] Evergreen ILS branch master updated. 03dc0514b36020d39755cc6e75234db23c52c207

Evergreen Git git at git.evergreen-ils.org
Tue Mar 15 11:07:54 EDT 2016


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  03dc0514b36020d39755cc6e75234db23c52c207 (commit)
       via  b59bba3ecd45b01986449246b8e760ab752d3dd8 (commit)
       via  5e24cf1ef4353c49fbc39c7a6db33e277cace908 (commit)
      from  345fd7440224cd72ddca821e6eaa6973f3733eb5 (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 03dc0514b36020d39755cc6e75234db23c52c207
Author: Jane Sandberg <sandbej at linnbenton.edu>
Date:   Mon Mar 14 16:34:43 2016 -0700

    docs: reorganizing, adding information about importing authority records using vandelay
    
    Signed-off-by: Galen Charlton <gmc at esilibrary.com>

diff --git a/docs/cataloging/authorities.txt b/docs/cataloging/authorities.txt
index a907931..c068c4f 100644
--- a/docs/cataloging/authorities.txt
+++ b/docs/cataloging/authorities.txt
@@ -1,11 +1,9 @@
-Manage Authorities
-------------------
+Managing Authorities
+--------------------
+This section describes how you can create, import, view, modify, merge, and delete authority records in Evergreen.
 
-In Evergreen to view, edit, merge, and delete authority records you would use the *Manage Authorities* interface 
-through the *Cataloging* menu.
-
-[TIP]
-=================
+Creating Authorities
+~~~~~~~~~~~~~~~~~~~~
 Currently in Evergreen to create a new authority record, as opposed to importing an authority record, you 
 need to have a bib record open in the bib MARC editor. 
 
@@ -16,11 +14,48 @@ New Authority from this field_, then select either _Create Immediately_ or _Crea
 * If you 
 choose _Create and Edit..._, after the authority MARC editor opens you need to click on the _Save_ button
 to finally add the new authority record to your system.
+
+
+Importing Authorities
+~~~~~~~~~~~~~~~~~~~~~
+. Click *Cataloging -> MARC Batch Import/Export.*
+. You may create a queue to better track this import project.  If you do not create a new queue, it will automatically put your records into a default queue named *-*.
+. Don't set a value for Holdings Import Profile, because this doesn't apply to authority records.
+. Select a file of authority data and put it in the *File to Upload* field.
+. Make sure all the settings are correct, then press *Upload.*
+. Evergreen will automatically assign a thesaurus based on the *Subj* fixed field, which is character 11 in the 008 field.
+
+[TIP]
+=================
+If you are importing authorities from an external vendor and want to track this, you may wish to set a unique Record Source. 
+=================
+
+
+
+Setting up Authority Record Match Sets
+++++++++++++++++++++++++++++++++++++++
+. Click *Cataloging -> MARC Batch Import/Export.*
+. Click *Record Match Sets.*
+. If you have sufficient privileges, you will be able to click on the *New Match Set*.  If you are unable to do so, check that you have the ADMIN_IMPORT_MATCH_SET permission.
+. Give your new set a descriptive name, an owning library, and a match set type of *authority.*
+. Click on the blue hyperlinked name of the match set you just created to add criteria.
+. You can match against MARC tag/subfield entries, against a record's normalized heading + thesaurus.
+
+[TIP]
+=================
+Evergreen's internal identifier is in the 901c field. If you have previously exported authority record -- perhaps for an external vendor to do authority cleanup work -- and you want to import them back into your catalog, you may wish to include the 901c field in your match set.
 =================
 
+Manage Authorities Interface
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+In Evergreen to view, edit, merge, and delete authority records you would use the *Manage Authorities* interface 
+through the *Cataloging* menu.
+
+
 
 Searching for authorities
-~~~~~~~~~~~~~~~~~~~~~~~~~
++++++++++++++++++++++++++
 
 To search for authorities in your system, first select the *Cataloging* menu and then select *Manage Authorities*. 
 Then proceed to fill out the search form. 
@@ -54,4 +89,4 @@ _Edit_, _Mark for Merge_, _Delete_
 * s = Sears List of Subject Headings
 * v = Repertoire de vedettes-matiere
 * z = Other
-* | = No attempt to code
\ No newline at end of file
+* | = No attempt to code

commit b59bba3ecd45b01986449246b8e760ab752d3dd8
Author: Jane Sandberg <sandbej at linnbenton.edu>
Date:   Mon Feb 29 16:00:15 2016 -0800

    docs: Adding instructions for setting up due time in the patron's myopac display
    
    Signed-off-by: Galen Charlton <gmc at esilibrary.com>

diff --git a/docs/admin_initial_setup/designing_your_catalog.txt b/docs/admin_initial_setup/designing_your_catalog.txt
index 3c122ac..91948a3 100644
--- a/docs/admin_initial_setup/designing_your_catalog.txt
+++ b/docs/admin_initial_setup/designing_your_catalog.txt
@@ -383,6 +383,23 @@ You may also change the default number of facets appearing under each category
 by editing the _facet.default_display_count_ value in _config.tt2_. The default 
 value is 5.
 
+Change Date Format in Patron Account View
+-----------------------------------------
+Libraries with same-day circulations may want their patrons to be able to view
+the due *time* as well as due date when they log in to their OPAC account.  To
+accomplish this, go to _opac/myopac/circs.tt2_.  Find the line that reads:
+
+----
+[% date.format(due_date, DATE_FORMAT) %]
+----
+
+Replace it with:
+
+----
+[% date.format(due_date, '%D %I:%M %p') %]
+----
+
+
 Including External Content in Your Public Interface
 ---------------------------------------------------
 

commit 5e24cf1ef4353c49fbc39c7a6db33e277cace908
Author: Jane Sandberg <sandbej at linnbenton.edu>
Date:   Mon Feb 29 15:42:31 2016 -0800

    docs: Adding section about facet_groups in advanced search
    
    Signed-off-by: Galen Charlton <gmc at esilibrary.com>

diff --git a/docs/admin_initial_setup/designing_your_catalog.txt b/docs/admin_initial_setup/designing_your_catalog.txt
index 81e5fec..3c122ac 100644
--- a/docs/admin_initial_setup/designing_your_catalog.txt
+++ b/docs/admin_initial_setup/designing_your_catalog.txt
@@ -339,6 +339,26 @@ For example, if you delete the line:
 the language field will no longer appear on your advanced search page. Changes
 will appear immediately after you save your changes.
 
+You can also add fields based on Search Facet Groups that you create in the
+staff client's Local Administration menu. This can be helpful if you want to
+simplify your patrons' experience by presenting them with only certain
+limiters (e.g. the most commonly used languages in your area).  To do this,
+
+. Click *Admin -> Local Administration -> Search Facet Groups*.
+. Click *New*.
+. Enter descriptive values into the code and label fields.  The owner needs to
+be set to your consortium.
+. Once the Facet Group is created, click on the blue hyperlinked code value.
+. Click the *New* button to create the necessary values for your field.
+. Go to the _opac/parts/config.tt2_ file, and add a line like the following,
+where *Our Library's Field* is the name you'd like to be displayed next to
+your field, and *facet_group_code* is the code you've added using the staff
+client.
+
+---
+ {adv_label => l("Our Library's Field"), adv_filter => "facet_group_code"},
+---
+
 Changing the display of facets and facet groups
 -----------------------------------------------
 

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

Summary of changes:
 .../admin_initial_setup/designing_your_catalog.txt |   37 ++++++++++++++
 docs/cataloging/authorities.txt                    |   53 ++++++++++++++++---
 2 files changed, 81 insertions(+), 9 deletions(-)


hooks/post-receive
-- 
Evergreen ILS


More information about the open-ils-commits mailing list