Move MARC templates into the database

[Jason Stephenson]

MARC bib templates currently reside in the web server file system and are universal for an entire Evergreen installation. This means that all libraries on a single Evergreen instance have to share the same set of MARC templates. There cannot be a different set for library X or for academic vs. public libraries in a mixed consortium.

Additionally, new templates are added by configuring opensrf.xml. This means that, at a minimum, the opensrf.settings service needs to be restarted whenever a new MARC template is added.

Relocating the storage of MARC templates from the filesystem to the database could alleviate both of these situations. The visibility of the templates could be controlled by permissions so that catalogers only see those templates that they need. Catalogers could also be able to create their own templates and save them for later without requiring access to the server or without asking the staff who do have such access to make the changes/additions for them. This ability can also be controlled by permissions. Finally, by moving the templates to the database, any new templates should show up whenever a cataloger refreshes the template list view rather than requiring a restart of opensrf services.

[Lynn Floyd (lfloyd)]

There is a discussion thread on this wish list: http://list.evergreen-ils.org/pipermail/evergreen-catalogers/2016-April/000605.html

Looking more at what some of us want Marc templates to do.

[Anna Goben (agoben)]

This has come up again as we're switching to all RDA templates.

[Elizabeth Thomsen (et-8)]

This is also a priority for libraries with growing of Library of Things collections.

[Ruth Frasur Davis (redavis)]

This is still a desirable feature, and I hope that the conversation can be reignited.

[Mary C. Wilson (mcwilson6)]

This would be an amazing addition to Evergreen for catalogers! I would love to be able to create a "local" MARC template for my library's use only. This would be very helpful for titles that are very similar and a detailed template could save a lot of typing time. For example, one for the 100+ juvenile kits I have to catalog would be a big time-saver.

[Kate Coleman (katecoleman)]

+1 I realize this wishlist item is rather old, but being able to have our own MARC templates, and edit the ones that are currently there, would give a lot of autonomy and customization option to Evergreen libraries.

[Joan Kranich (jkranich)]

+1

[Elizabeth Thomsen (et-8)]

Confirming that this has not been addressed in 3.10 or 3.11, and that is still a much-desired enhancement.

[Carol Witt (carolwitt)]

I'm going to reboost this because we've recently had another question about it from one of our libraries.

Carol

[Jennifer Pringle (jpringle-u)]

We are very much in favour of this.

In case it's useful for anyone coming across this bug here's the workaround we currently use: http://docs.libraries.coop/sitka/_using_library_specific_marc_templates.html