Item template creation error

Bug #1161384 reported by Elaine Hardy on 2013-03-28
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Evergreen
Medium
Unassigned

Bug Description

PINES catalogers are seeing an issue in 2.3.4 with creating new item templates from an existing template.

If one wants 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 (although some reports on the cataloging list indicate other libraries are seeing other attributes not persisting). 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 attempted 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).

I notice that some of the older templates do not have both "Location/Collection" and "Shelving Location". Those that just have "Shelving Location", the value is the more complete four digit code rather than 1. There also some templates with just "Location/Collection"

Ben Shum (bshum) on 2013-04-01
Changed in evergreen:
status: New → Confirmed
importance: Undecided → Medium

We just ran into this issue also in EG 2.8.4.

Just to speculate, it appears that any time the label changes but the field and type stays the same, two entries are kept, which both try to set the same value. Sometimes one wins, sometimes the other.

So "Shelving Location" was the label pre 2.3.4 and now the label is "Location/Collection". I tried to find when it was changed but didn't have any luck tracking it down.

In our case the name of our stat cats were changed. When the templates were updated and re-saved there were entries for both the new label and the old label. They both have the same field and type referenced.

  "pan2 Pb Ad NF NEW": {
    "Circulate?": {
      "type": "attribute",
      "field": "circulate",
      "value": "t"
    },
    "LARL_NWRL_CONSORTIUM : Item Type": { #(OLD Bad one)
      "value": "333",
      "field": "13",
      "type": "stat_cat"
    },
   "LARL_NWRL_CONSORTIUM : ZZ Old Item Type Code": { #(New Correct One)
      "field": "13",
      "value": "426",
      "type": "stat_cat"
    },
    "Location/Collection": {
      "field": "location",
      "value": "122",
      "type": "attribute"
    }
  },

I think that the copy template code needs some logic to not save entries with different labels but the same field and type to prevent this from happening. Or maybe if it just always updated the labels of the entries to the current value that would take care of the problem.

Eva Cerninakova (ece) wrote :

The same problem still happens in EG 2.10.5

tags: added: cataloging
Meg Stroup (mstroup) on 2019-05-23
tags: added: itemtemplates
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers