[Evergreen-catalogers] Item template issue in 2.3.4

[Sarah Childs]

Hi, Elaine.
We're still on 2.2 in Indiana and we've noticed this problem 
periodically with different versions. If I recall correctly creating new 
templates by editing existing templates never worked for us with at 
least one version (2.1 or 2.0?) Looking back, I think we filed a ticket 
internally with 2.1, and were told to wait for the upgrade. The problem 
seemed to be resolved when we moved to 2.2, but in the last month or so 
I've noticed it again. Testing today, it seems to work fine. So it 
doesn't seem to be consistently replicable. Bleh. That's one of the 
reasons I don't think we ever got as far as filing a bug report on this, 
especially since it's a relatively rare problem, with a simple 
workaround. (Creating the template from scratch works) But we do find it 
annoying, and I'd be all for seeing it resolved.

---
Sarah Childs
Senior Cataloger
Hussey-Mayfield Memorial Public Library
250 North Fifth Street
Zionsville, IN 46077
317-873-3149 x13330
sarahc at zionsville.lib.in.us

On 2013-03-26 11:46, Hardy, Elaine wrote:
> 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
> www.georgialibraries.org/pines [1]
> --
> This message has been scanned for viruses and
> dangerous content and is believed to be clean.
> Links:
> ------
> [1] http://www.georgialibraries.org/pines
> _______________________________________________
> Evergreen-catalogers mailing list
> Evergreen-catalogers at list.evergreen-ils.org
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers