[Evergreen-catalogers] Item template issue in 2.3.4

[Janet Schrader]

CWMARS is on REL 2.3. A few libraries have reported that some fields change in existing templates. One reported that the status changed to 'missing'. Another reported that the circ modifier and age-based hold protection fields become 'unset' but not consistently. Two libraries have reported problems applying templates to items created as orders in Acquisitions when the templates have particular stat cat fields.

We have 170 libraries and hundreds of tech service staff using thousands of copy templates. We do not do any cataloging at the central site so don't use templates except for training. These problems represent less than 1% of our membership so we are not sure it's a bug. 



Janet

Janet Schrader
C/W MARS Inc.
Supervisor of Bibliiographic Services
67 Millbrook Street, Suite 201
Worcester, MA 01606
tel: 508-755-3323 ext. 25
fax: 508-757-7801
jschrader at cwmars.org


-----Original Message-----
From: evergreen-catalogers-bounces at list.evergreen-ils.org [mailto:evergreen-catalogers-bounces at list.evergreen-ils.org] On Behalf Of Tina Ji (Project Sitka)
Sent: Tuesday, March 26, 2013 12:10 PM
To: evergreen-catalogers at list.evergreen-ils.org
Subject: Re: [Evergreen-catalogers] Item template issue in 2.3.4

We had a couple of similar incidents on 2.2.X with the same symptom as you described. We ended up with creating the template from scratch, which means not applying any template, but setting up the field values directly once the Copy Editor is open. If I remember correctly, in one case we used the old template name with a success.



Quoting "Hardy, Elaine" <ehardy at georgialibraries.org>:

> PINES catalogers are seeing an issue in 2.3.4 with creating new item 
> templates from an existing template. I could not find a bug report in 
> Launchpad and before I pursue it further thought I would check with 
> everyone to see if they have noticed it as well.
>
>
>
> If you  want to create a template from an existing template and change 
> the Location/Collection under Location (1), that change does not 
> always persist after saving the template with a new name. Other 
> attributes do persist if changed. Sometimes, the Location/Collection 
> does change and sometimes checking back later finds the changes have 
> propagated. Other times not. When we look at the exported templates, 
> some of the changed templates show the changed Location/Collection and 
> some do not. Those that do don't necessarily show the changed template 
> when it is applied in the copy editor. For example:
>
>
>
> "test template issue 2": {
>
>                              },
>
>                              "Location/Collection": {
>
>                                            "value": "2587",
>
>                                            "type": "attribute",
>
>                                            "field": "location"
>
>                              },
>
>                              "Shelving Location": {
>
>                                            "value": 1,
>
>                                            "type": "attribute",
>
>                                            "field": "location"
>
> },
>
> "test location issue": {
>
>                              },
>
>                              "Location/Collection": {
>
>                                            "value": "4133",
>
>                                            "type": "attribute",
>
>                                            "field": "location"
>
>                              },
>
>                              "Shelving Location": {
>
>                                            "value": 1,
>
>                                            "type": "attribute",
>
>                                            "field": "location"
>
>
>
> For both of the above templates, based on the changed location in the 
> copy editor, the value for the location should be the same. Test 
> location issue has retained the value of the original template (and, 
> yes, I did apply before I saved the new template). To make matters 
> even odder, when I apply test template issue 2 in the copy editor, it 
> does not apply the location for 2587 (magazine), it applies 4133 (stacks).
>
>
>
> Has anyone else noted this problem? If so, were you able to resolve it?
>
>
>
> Elaine
>
>   _____
>
>
> J. Elaine Hardy
> PINES Bibliographic Projects & Metadata Manager Georgia Public Library 
> Service
> 1800 Century Place, Ste 150
> Atlanta, Ga. 30345-4304
>
> 404.235-7128
> 404.235-7201, fax
> ehardy at georgialibraries.org
> www.georgialibraries.org
>  <http://www.georgialibraries.org/pines> 
> www.georgialibraries.org/pines
>
>
>
>
>



Tina Ji
1-888-848-9250
Trainer/Help Desk Specialist
BC Libraries Cooperative/Sitka


_______________________________________________
Evergreen-catalogers mailing list
Evergreen-catalogers at list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers