⧼vector-jumptocontent⧽

Admin/System Tools/Regenerate Abstracts: Difference between revisions

From EPrints Documentation
Added page about Regenerate Abstracts page
 
mNo edit summary
Line 2: Line 2:
This page pertains to the '''Regenerate Abstracts''' button in the '''[[Admin/System Tools|System Tools]]''' tab of the '''[[Admin]]''' web page for your repository web interface.
This page pertains to the '''Regenerate Abstracts''' button in the '''[[Admin/System Tools|System Tools]]''' tab of the '''[[Admin]]''' web page for your repository web interface.


The ''Regenerate Abstracts''' button updates the timestamp in the archive's <tt>var/abstracts.timestamp</tt> file to the current time.  This file is used whenever an abstract page is requested, if the current (server-side) cache for this abstract page is older that the timestamp in this file, then the abstract page is regenerated.  This is better than regenerating all abstracts pages immediately.  As a repository gets larger the time to regenerate all abstract pages gets longer and can put a high load on the server.
The '''Regenerate Abstracts''' button updates the timestamp in the archive's <tt>var/abstracts.timestamp</tt> file to the current time.  This file is used whenever an abstract page is requested, if the current (server-side) cache for this abstract page is older that the timestamp in this file, then the abstract page is regenerated.  This is better than regenerating all abstracts pages immediately.  As a repository gets larger the time to regenerate all abstract pages gets longer and can put a high load on the server.
 
If you actually want to regenerate abstract pages use the ''[[API:bin/generate_abstracts|bin/generate_views]]''' script.

Revision as of 21:09, 4 March 2022

This page pertains to the Regenerate Abstracts button in the System Tools tab of the Admin web page for your repository web interface.

The Regenerate Abstracts button updates the timestamp in the archive's var/abstracts.timestamp file to the current time. This file is used whenever an abstract page is requested, if the current (server-side) cache for this abstract page is older that the timestamp in this file, then the abstract page is regenerated. This is better than regenerating all abstracts pages immediately. As a repository gets larger the time to regenerate all abstract pages gets longer and can put a high load on the server.

If you actually want to regenerate abstract pages use the bin/generate_views' script.