last_touched

[jarrod-dalton]

It would be useful for project management purposes to have a last_touched timestamp associated with each project. This could be based on when the metadata were last updated, or when the last file update was made within the project files.

The more I think about it, the more I lean toward using the last update to the metadata as opposed to the timestamps on the project files.

This could lead to helper functions like zombie_projects(time = "60 days") and zombie_ideas(time = "6 months"), which are essentially just wrappers for projects() and ideas().

I guess this functionality could just be implemented as a parameter to projects() and ideas() as opposed to helper functions, but where's the fun in that? (We could actually do both.)

[NikKrieger]

The more I think about it, the more I lean toward using the last update to the metadata as opposed to the timestamps on the project files.

This would involve somehow tracking the last time the project's specific row was altered. Do you envision an additional column?

[jarrod-dalton]

Now that I'm thinking about it even more, a true "last touched" timestamp would be the max of any file changes or updates to the metadata. Although, changing some small detail on the metadata is a rather superficial definition of "touching" a project.

Is it easier to use the file timestamps? If so, let's go with that. Note that, at this point, this minor functionality is probably not worth more than an hour or so of effort. I'm just as happy to table this for some unspecified time in the future (yes I see the irony there).