| 2024-02-23 14:42:13 |
Galen Charlton |
description |
This is a metabug for enhancements to reduce the number of things that can be configured in Evergreen only by editing files on the server. There are many areas where there is no particular reason why a staff interface administrative interface couldn't work, and moving away from server-side configuration will increase the ability of library staff to make necessary changes quickly.
Known existing bugs that fall in this category include:
* Bug 1365073 - ZIP/postal code lookup table should be moved to the database
* Bug 1131238 - Move MARC templates into the database
* Bug 1901930 - Evergreen SIP2Mediator Support (included because it would move configuration of SIP2 service accounts to the database)
Other ideas that don't currently have separate bugs include:
* OPAC templates. Several ways that this could be done, but my broad idea is to add a template editor to Evergreen that would allow staff to quickly iterate and test changes before deploying them to production. Built-in revision control would be nice, if not necessary.
* OPAC virtual host definitions.
* Cronjobs. One idea is that there would be a standalone job runner that would take its configuration from the database.
* Added content settings
* Acq MARC order reader settings
* Asterisk
* Auth proxy
* Z39.50 server configuration |
This is a metabug for enhancements to reduce the number of things that can be configured in Evergreen only by editing files on the server. There are many areas where there is no particular reason why a staff interface administrative interface couldn't work, and moving away from server-side configuration will increase the ability of library staff to make necessary changes quickly.
Known existing bugs that fall in this category include:
* Bug 1365073 - ZIP/postal code lookup table should be moved to the database
* Bug 1131238 - Move MARC templates into the database
* Bug 1901930 - Evergreen SIP2Mediator Support (included because it would move configuration of SIP2 service accounts to the database)
Other ideas that don't currently have separate bugs include:
* OPAC templates. Several ways that this could be done, but my broad idea is to add a template editor to Evergreen that would allow staff to quickly iterate and test changes before deploying them to production. Built-in revision control would be nice, if not necessary.
* OPAC virtual host definitions.
* Cronjobs. One idea is that there would be a standalone job runner that would take its configuration from the database.
* Added content settings
* Acq MARC order reader settings
* Asterisk
* Auth proxy
* Z39.50 server configuration
* MARC stream importer settings |
|
