Jump to content
Wiki Home
EPrints Home
Bazaar
Files
Main menu
Main menu
move to sidebar
hide
Navigation
Front Page
EPrints 3 Manual
EPrints Training Course
EPrints Glossary
Installing EPrints
How-to Configure EPrints
EPrints 3.2+ API
EPrints 3 Reference
EPrints Plugins
Wiki
All categories
Recent changes
Main Page
Help
EPrints Documentation
Search
Search
Appearance
Log in
Request account
Personal tools
Log in
Request account
Pages for logged out editors
learn more
Contributions
Talk
Editing
EPrints Cron Jobs
(section)
Page
Discussion
British English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== Default Cron Jobs == There are various different cron jobs you may want to deploy. Below is a template crontab for a vanilla EPrints repositories without extra plugins or ingredients installed. {{template:EPrints_Crontab_Template}} The <code>generate_views</code> cron job is to ensure both menu and listing pages for browse views (found under http://HOSTNAME/views/ and its sub-pages) are updated. Browse views menu and listing pages are typically cached for 24 hours. However, by regenerating these by cron job every 24 hours, they will load more quickly, as they won't needed to be regenerated on-the-fly because the cache has expired. If you have a large EPrints repository with lots of different browse views, you may find this cron job takes several hours to complete. The <code>send_alerts</code> cron jobs send out emails on a daily, weekly or monthly basis. The most common use of these is to send emails to editors reminding them of items they need to review. Updates on results from saved searches also use the script to send out emails. Other plugins or ingredients may add to the types of email that can be sent out by this scripts. The <code>lift_embargos</code> cron job checks over all embargoed documents in eprint records and removes the access restriction on these documents if the embargo date has been reached. It is useful to retain the out from this script as the embargo date will also be unset and sometimes this information is required retrospectively, so such a logs file is the most straightforward way of retrieving this. (There are certain flags you can set for <code>lift_embargos</code> if you need the embargo date retained. The <code>generate_sitemap</code> cron job generates a XML sitemap at http://HOSTNAME/sitemap.xml. This sitemap contains links to one or more numbered site maps each of which contain entries for each eprint abstract page in the live archive. As new items are likely to be added continual, it is important to regular update this sitemap to include these new items. The <code>issues_audit</code> cron job analyses eprints records in the whole, detecting things like those that have the same or similar title.
Summary:
Please note that all contributions to EPrints Documentation may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
EPrints Documentation:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)