4.3 beta 3: Feedback on "Last updated" column

Thank you for including a 'last updated' column. It will go some way to helping people know which resources have been updated.

However, as you say in the release notes, all the entries are for today. Please could this be pre-populated with the data from the updates table of UpdateManager/Updates.db so that the majority of resources have an accurate date from the beginning? Resources that don't have an entry in updates.db could be given the file-creation date of the Logos 4 folder, or perhaps the earliest date in the Updates table.

Second, I think there's some potential for confusion. By 'last-updated', you presumably mean when the most recent install date was, not when the file was actually published. I don't have a better suggestion but I wonder if there is a choice of words that makes this distinction clear.

Find more posts tagged with

Comments

Rosie Perera

However, as you say in the release notes, all the entries are for today. Please could this be pre-populated with the data from the updates table of UpdateManager/Updates.db so that the majority of resources have an accurate date from the beginning? Resources that don't have an entry in updates.db could be given the file-creation date of the Logos 4 folder, or perhaps the earliest date in the Updates table.

Yes, I had the same thought!

Second, I think there's some potential for confusion. By 'last-updated', you presumably mean when the most recent install date was, not when the file was actually published. I don't have a better suggestion but I wonder if there is a choice of words that makes this distinction clear.

How about "Last Downloaded"? Or (same number of letters and a bit prettier): "Latest Download"

Or "Last Installed"?

Dave Hooton

Please could this be pre-populated with the data from the updates table of UpdateManager/Updates.db

How many resources will this actually affect; you indicate "majority" but will it be more useful for an older installation that has many updates vs. a recent installation with no updates?

Dave Hooton

By 'last-updated', you presumably mean when the most recent install date was, not when the file was actually published. I don't have a better suggestion but I wonder if there is a choice of words that makes this distinction clear.

I agree it is ambiguous as it has to accommodate my new resources and updated ones. last-installed is better.

BTW, I second Mark's suggestion.

Thanks

Peter

Mark Barnes

How many resources will this actually affect; you indicate "majority" but will it be more useful for an older installation that has many updates vs. a recent installation with no updates?

In my own case, it's all resources since March 2003. That's a total of 495 resources that would have more accurate dates. (Perhaps there's none before that date because the table wasn't populated before 4.0c beta 1, but there could be some other reason.)

But if someone's only installed recently, then the "last updated" column could just be set to the date of installation.

Dave Hooton

In my own case, it's all resources since March 2003. That's a total of 495 resources that would have more accurate dates. (Perhaps there's none before that date because the table wasn't populated before 4.0c beta 1, but there could be some other reason.)

But if someone's only installed recently, then the "last updated" column could just be set to the date of installation.

Some resources have never been updated, so presumably they are not in Updates.db? If you are still referring to our current installations where does the date of installation come from?

spitzerpl

I would rather Logos focus there attention elsewhere rather then trying to input old dates. The important thing is to know which resources are updated moving forward. Given the system they set up it seems like we will now know that information.

Mark Barnes

Some resources have never been updated, so presumably they are not in Updates.db?

Correct.

If you are still referring to our current installations where does the date of installation come from?

I'm suggesting that resources that have never been updated are either (a) given the date that Logos was installed (you can look this up by seeing when the {random-name} folder was created, or (b) the date when updates started to be recorded in updates.db, whichever is the later.

Bradley Grainger (Logos)

However, as you say in the release notes, all the entries are for today. Please could this be pre-populated with the data from the updates table of UpdateManager/Updates.db so that the majority of resources have an accurate date from the beginning?

No; doing so would introduce complications beyond the scope of this feature.

However, if you do want the dates copied over, I've written a tool that should copy them for you. It's barely tested, unsupported, carries no warranty, back up your files before using, etc. If it works, I'll take full credit; if it destroys your system, I disclaim all responsibility. [:)]

It won't set the "last updated" date correctly for resources from an original DVD install, or resources imported from LDLS3, or resources discovered by using the "scan" command.

7343.SetLastInstalledDate.zip

Mark Barnes

Thanks, Bradley. It worked fine here - I'd made a brief failed attempt with a nested SQL query, so a PHP script was next on my list. You saved me the trouble, and yours will work for people without webservers installed!

Todd Phillips

It won't set the "last updated" date correctly for resources from an original DVD install, or resources imported from LDLS3, or resources discovered by using the "scan" command.

Well, it worked, kinda: it only set the date on 106 resources, and the earliest date set was May 25, 2010. I would have expected to see dates for most of the resources I purchased this year. For example, the only Zondervan resource to get a new date was the NIDOTTE (Jul 2, 2010), the rest (EBC and NIDNTT) still say "Tuesday". Since the Zondervan resources were added in March and April, the NIDOTTE date must be an update, so it just looks like May 25th is the cutoff date for me.

Is it possible I did something to my library that would have removed the dates before May 25th?

SteveF

Well, it worked, kinda

Thanks, Mark

this is a great 'start' to something that could be quite helpful.

Blessings

steve clark

What is the syntax on using the new Last Updated in the Find box?

Bradley Grainger (Logos)

What is the syntax on using the new Last Updated in the Find box?

There is none; the only interaction with that data is to show the column and sort it.

Bohuslav Wojnar

Well, it worked, kinda: it only set the date on 106 resources, and the earliest date set was May 25, 2010.

Similar problem here. For me it is Jule 7th, 2010. Any idea?

Bradley Grainger (Logos)

Well, it worked, kinda: it only set the date on 106 resources, and the earliest date set was May 25, 2010.

Similar problem here. For me it is Jule 7th, 2010. Any idea?

Have you ever deleted the UpdateManager\updates.db file? (If so, any dates that had been stored in it will have been permanently lost.)

Deleting ResourceManager.db will also cause the UpdateManager DB to be cleared (and there may be other triggers, too).

Dave Hooton

However, if you do want the dates copied over, I've written a tool that should copy them for you.

Hi Bradley

I got the following error

DominicM

ok after looking into it more updates.db already has this date of last update to resource that I was asking for [Resources.LocalVersion] , although it would be nice to see it, in that library list at least I know where I can get it from