Comment 13 for bug 1772062

Meg,

Templates in the XUL client are much more forgiving than those in the web client.

One thing I have noticed is that, if a template is created with a default set to the default value (status as In Process, for example), then the value in the editor will not necessarily display but will apply. Defaults aren't as obvious in the web client. My findings:

    Circulate?: Yes/True
    Status: In process
    Circulation library (if single volume added; from owning library)
    Reference?: No/False
    OPAC Visible?: Yes/True
    Holdable?: Yes/True
    Quality: Good (PINES has not implemented)
    Copy status: in process
    Circulation Library (Populates from workstation library, will need to change if Templates is for specific branch. If used for adding multiple volumes for different branches/libraries leave the value in editor <unset> so that the Circ library will populate from owning library for each branch/library)
    Fine level: normal
    Duration: normal

If you are using the default values, it isn't necessary to include them in a template. I don't think it breaks the template, they may just not display 100% of the time.

An aside --- if you use circ modifiers, you don't need to use circ as Type. That attribute is for use in conjunction with using MARC fixed field Type for circ rules and is for when you want the item to circ differently. For example, if a book and accompanying CD are cataloged as Type: a (language material) and you bundle them together and want them to circ as a kit -- Circ as type would be set to kit. I don't see where using them with circ modifiers would cause issues with a template applying, however.

We have observed that when a template fails, for whatever reason, it will not apply many of the settings. Or will apply them incorrectly. In those cases, you can't successfully save & exit, even if the tab closes, items won't be created. And once the template fails, it never works again.

I don't recall whether I have had problems with the dropdown menu with a failed template. It does sound familiar but I don't do enough live cataloging to recall. I mainly do testing and database cleanup.

Since we have also observed that a successfully applied template will not always display some of the attributes, it is unnerving to go ahead and save. I have my columns in Holdings View set up so that I can see most attributes but since there is not room enough in the grid to really see them it can take time to verify they are correct.