Opac: better handling of Date+time formats
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Evergreen |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
Currently, the booking reservations display in the Public Catalog uses a sort of hacky date format (it's just the DATE_FORMAT specified in config.tt2 with some time concatenated at the end): https:/
Some Evergreen libraries use a DATE_FORMAT that includes time, which makes the reservations view repetitive. For example, a reservation might list a due date of "2019-08-03 12:23pm 12:23PM"
One solution might be to add a separate DATETIME_FORMAT option to config.tt2, which would then be used in the reservations tab. Then, if a library wanted to include a time elsewhere in the public catalog interface (say in circulation due dates), they could simply change DATE_FORMAT to DATETIME_FORMAT in the relevant .tt2 file.
Another solution would be to add separate variables that are used for specific purposes, like DUE_DATE_FORMAT, RESERVATION_
What do you all think?
| Jason Stephenson (jstephenson) wrote | #1 |
| Jane Sandberg (sandbergja) wrote | #2 |
| Changed in evergreen: | |
| status: | New → Confirmed |
| Christine Burns (christine-burns) wrote | #3 |
I want to note that the backend code in EGCatLoader and family will need to be made to understand these different formats.
I also want to ask if the scope of this bug is limited to booking and reservations or is the intent to expand this into the entire OPAC?