Bug 23030 - Installation and last update date in About
Summary: Installation and last update date in About
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: About (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
: 32326 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-06-01 17:33 UTC by Christopher Brannon
Modified: 2025-01-08 01:09 UTC (History)
3 users (show)

See Also:
GIT URL:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Brannon 2019-06-01 17:33:13 UTC
Would like to see the install date (or last upgrade date, or both) in About.
Comment 1 Katrin Fischer 2023-10-08 10:28:19 UTC
*** Bug 32326 has been marked as a duplicate of this bug. ***
Comment 2 Rebecca Coert 2025-01-07 20:49:25 UTC
I would also like to see a line (or lines) be added to the "About Koha" page, Server Information tab, that records the date & time of the last server upgrade (either when a full xx.xx upgrade, point release, or test server DB sync occurs).  This would help us troubleshoot issues with our third-party vendors.
Comment 3 David Cook 2025-01-08 01:06:47 UTC
This is an interesting one...

Working as a vendor, I'm not going to want every software release to do a database update. Sometimes a software release might include just a 1 character change after all. Ideally, an update of a live system should be run as fast as possible to minimize any downtime.

But...  perhaps C4::Installer::update() or 4::Installer::SetVersion() could record a date of update in the database when it has a database update to do anyway.

--

Another idea is rather than an install/upgrade date/timestamp we could do a "build" date/timestamp. With this idea, every software update would be captured, so long as it was made via the full software deployment process and not as a hot fix. 

That's something I've been pondering for a while. As part of the Koha build, a file could be generated that includes a timestamp and possibly other build information. 

(The trick here is that it would be a system-wide file and not an instance-specific file, so we'd either need to add a line to koha-conf.xml which isn't great from an upgrade point of view, or we'd need to come up with an alternative idea for how to find the file. For example, we could use a Perl module to find the /usr/share/koha/lib and then work backwards from there. This is a method used by some web frameworks, so there is some precedent there.)
Comment 4 David Cook 2025-01-08 01:09:31 UTC
Technically, I suppose we could do both of the above ideas, because they tell you similar but different things.

One is when your database was last upgraded, and the other one is the age of your software build.

(I don't see how "test server DB sync" could work here, although I suppose some tooling could be added to koha-restore. But personally we don't use that to restore databases.)