- Avoid locking the tables for too long or creating a massive transaction in case the table has accumulated records for a longer time.

* Reverted deletion of getExpiredQuery() and added command line parameters for specifying batch size and sleep time.

* Don't sleep after last batch.

- Resolves VUFIND-1192.

- Resolves VUFIND-1184.

- Fixes problems with RSS feed, saved search, etc.

- Plain angle brackets are a standard way of delimiting a URI in email (see e.g. ftp://ftp.rfc-editor.org/in-notes/rfc3986.txt Appendix C) and help with long URLs that would otherwise wrap (and even if the link would initially work, it would often fail if forwarded as quoted).

Conflicts:
	module/VuFind/src/VuFind/Search/Tags/Results.php

- Resolves VUFIND-1191.

getUniqueResources, getUniqueTags, and getUniqueUsers was failing due to mySQL5.7 compatibility issues. The error being thrown by mySQL was: Expression #1 of SELECT list is not in GROUP BY clause and contains nonaggregated column which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by

To fix, we have to either turn off the only_full_group_by option or specifically select the columns that are used instead of selecting *.

See: https://dev.mysql.com/doc/refman/5.7/en/group-by-handling.html for more info.

PostgreSQL was failing due to fields being present in ORDER but missing from GROUP BY. This has also been corrected.

* replaced all hard coded links in HelpTranslations with links build by view helper (otherwise links will fail if vufind is not installed in site root) (#749)

* adds removeCachedData() to ILS\Driver\AbstractBase to allow explicit removal of cached data (#747)

* replaced all hard coded links in HelpTranslations with links build by view helper (otherwise links will fail if vufind is not installed in site root) (#749)

Add a heading for the lightbox facet list, init lightbox_facets js only if available and translate 'more' properly in JS.

- All searches now go to Search/Results; all tag views go to Tag/Home; search handler name is consistent between both places.

- Avoids some nasty side effects of hidden filters (like broken autocomplete).

- There are two contexts in which a tag may be retrieved; one is using a search from the search menu, in which case we want to do fuzzy matching, including support for wildcard characters. The other is when a user clicks on a tag name on a record. In this case, we want to do exact matching, because the user has selected a specific known entity. These changes enable the code to tell the search case from the standard click case with the use of a hidden filter applied by the search controller.