Public catalog: create tt2 file for local text
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
New
|
Wishlist
|
Unassigned |
Bug Description
While working on documentation recently, I noticed there was a page that describes all of the different tpac files that should be updated with your local policies/text - http://
Rather than forcing new users to update all of these individual files, I would like to propose that we bundle several of these into one file whose main purpose is to hold local text that we expect libraries to customize before using their catalogs. For example, the file might contain the text that is in main_refund_
It would require existing Evergreen sites to do a bit of work moving the text when they upgraded, but I think it would be easier for new Evergreen sites to get their catalogs up and running.
Having strings that represent library policy statements bundled into a single resource file strikes me as something that would have been a reasonable design choice when TPAC was getting started, but the current approach is also a valid choice. Having the policy text split out keeps each part next to the context where the user is meant to read it, allowing for structural and design changes to be coordinated with changes to the text. For example, a library might elect to link out to a policy rather than quote it.
We're not starting with a blank slate, however; is there an argument to be made reducing the number of files to be edited by three (or so) is worth imposing a mandatory upgrade action?