Comment 3 for bug 276360

Need additional information in order to implement.

1. What is the exact criteria for determining when a growl-like notification should be presented to the user? Is the criteria the same for all image data sources or do the time spans vary by observatory/measurement?

2. Need data set describing the known availability of each data source to encode into the API. How will this dataset be kept up-to-date for ongoing and future missions?

I would recommend toggling the visibility of the out-of-date layer to OFF whenever the imagery is grossly out-of-date. The growl-like notification would explain why this has occured and offer an option to the user to toggle it back On. This action would be an implicit aknowledgement that they understand the descrepancy between the requested time and the time of the displayed imagery.