Move MARC templates into the database

Bug #1131238 reported by Jason Stephenson on 2013-02-21
This bug affects 20 people
Affects Status Importance Assigned to Milestone

Bug Description

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) wrote :

There is a discussion thread on this wish list:

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

Yamil (ysuarez) on 2017-01-30
tags: added: authority
tags: removed: authority
Anna Goben (agoben) wrote :

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

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers