From: Dan Scott <dan@coffeecode.net>
Date: Wed, 20 Jul 2011 19:23:32 +0000 (-0400)
Subject: Refine the 506 $3 punctuation decision
X-Git-Url: https://old-git.evergreen-ils.org/?a=commitdiff_plain;h=1599c30075a64e44f9788b155906f22f4506bae9;p=contrib%2FConifer.git

Refine the 506 $3 punctuation decision

From Graham Staffen:

My definitive answer (until I develop a revised definitive answer) is
that a period would always punctuate the end of the subfield except in
two instances: 1) a closing parenthesis, 2) a closing square bracket. I
have this from our MARC coding trainer who could think of no other
instances when a period is not employed.

Signed-off-by: Dan Scott <dscott@laurentian.ca>
---

diff --git a/tools/ebooks/prep_ebook_records.py b/tools/ebooks/prep_ebook_records.py
index efe34d9f58..7a607e9ba2 100644
--- a/tools/ebooks/prep_ebook_records.py
+++ b/tools/ebooks/prep_ebook_records.py
@@ -496,7 +496,7 @@ def add_restriction(new_record, options):
 
     # Add a period if the authorization ends with a number or letter
     authnote = options['authorization']
-    if re.match(r'[a-zA-Z0-9]', authnote[-1]):
+    if authnote[-1] not in '.)]':
         authnote += '.'
 
     for library in options['libraries']: