Hi,

Can anyone point me in the direction of a setting to prevent eprints from identifying a view as being out of date (eg > 24 hours old)and needing rebuilt?  Likewise abstracts etc.

Essentially for some infrastructure maintenance we need to put the repository filesystem into a read only state for about 72 hours, so it can still serve content (and record access etc into MYSQL) but can’t update the documents, html, cfg.d folders etc.

I’ve got the cron jobs pegged so they won’t run any of the ‘generate_*’ jobs during the maintenance window, but I’m having trouble pinning down how eprints is determining whether a view has expired and needs to be rebuilt.

Thanks in advance for any help.

Alan