Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
changelog [2019/11/04 15:11] – [Release 6.1 - currently under development] demiankatz | changelog [2019/11/15 18:30] – [Release 6.1 - currently under development] demiankatz |
---|
New features: | New features: |
| |
| * An optional [[configuration:email_alerts|Email Alerts]] feature can be enabled to allow users to subscribe to saved searches in order to be notified about new search results. |
* [[configuration:combining_search_types#multi-column_search|Combined Multi-Column Search]] now optionally supports search types (author, title, subject, etc.). | * [[configuration:combining_search_types#multi-column_search|Combined Multi-Column Search]] now optionally supports search types (author, title, subject, etc.). |
* Users can now change their email addresses in their accounts (though this feature is disabled by default -- see the config.ini change_email setting and [[https://github.com/vufind-org/vufind/pull/1401|pull request #1401]] for details). | * Users can now change their email addresses in their accounts (though this feature is disabled by default -- see the config.ini change_email setting and [[https://github.com/vufind-org/vufind/pull/1401|pull request #1401]] for details). |
| * The filter interface changes introduced in release 6.0 have been further improved, making the user experience more consistent. |
* Added "Email" authentication method to allow login by receiving a link in an email (see [[https://github.com/vufind-org/vufind/pull/1409|pull request #1409]]). | * Added "Email" authentication method to allow login by receiving a link in an email (see [[https://github.com/vufind-org/vufind/pull/1409|pull request #1409]]). |
* Added "PasswordAccess" authentication method to allow login using a single credential rather than a username/password combination (see [[https://github.com/vufind-org/vufind/pull/1394|pull request #1394]]). | * Added "PasswordAccess" authentication method to allow login using a single credential rather than a username/password combination (see [[https://github.com/vufind-org/vufind/pull/1394|pull request #1394]]). |
* It is now possible to limit site permissions on a global or controller-specific basis through configuration files, making it easier to manage protected content. See [[https://github.com/vufind-org/vufind/pull/1395|pull request #1395]] for details. | * It is now possible to limit site permissions on a global or controller-specific basis through configuration files, making it easier to manage protected content. See [[https://github.com/vufind-org/vufind/pull/1395|pull request #1395]] for details. |
* Improved support for running VuFind behind a reverse proxy (such as Apache's mod_proxy); see [[https://github.com/vufind-org/vufind/pull/1429|pull request #1429]] for details. | * Improved support for running VuFind behind a reverse proxy (such as Apache's mod_proxy); see [[https://github.com/vufind-org/vufind/pull/1429|pull request #1429]] for details. |
| * Added a [[development:plugins:doi_linkers|DOI Linker]] plugin for [[https://unpaywall.org/|Unpaywall]]. |
* Added support for storing VuFind sessions in [[https://redis.io/|Redis]]. | * Added support for storing VuFind sessions in [[https://redis.io/|Redis]]. |
* Hierarchical [[configuration:facets|facets]] sort options can now be configured independently for search results, home page listings and advanced search options; see [[https://github.com/vufind-org/vufind/pull/1389|pull request #1389]]. | * Hierarchical [[configuration:facets|facets]] sort options can now be configured independently for search results, home page listings and advanced search options; see [[https://github.com/vufind-org/vufind/pull/1389|pull request #1389]]. |
* :!: Be sure to run a database upgrade to reflect table changes (see also the [[development:architecture:database_schema#release_61|database changelog]]). | * :!: Be sure to run a database upgrade to reflect table changes (see also the [[development:architecture:database_schema#release_61|database changelog]]). |
* :!: The new email login capability adds some new features to the authentication logic along with some minor refactoring; if you have custom authentication code, you should review [[https://github.com/vufind-org/vufind/pull/1409|pull request #1409]] to be sure you are not impacted by it. | * :!: The new email login capability adds some new features to the authentication logic along with some minor refactoring; if you have custom authentication code, you should review [[https://github.com/vufind-org/vufind/pull/1409|pull request #1409]] to be sure you are not impacted by it. |
| * :!: Templates related to search filters have been changed significantly to fix a bug introduced in release 6.0 and to improve the revised functionality; if you have customized the filters.phtml template, or a template that includes filters.phtml, you should adjust to match the changes in [[https://github.com/vufind-org/vufind/pull/1482|pull request #1482]], [[https://github.com/vufind-org/vufind/pull/1499|pull request #1499]] and [[https://github.com/vufind-org/vufind/pull/1500|pull request #1500]] (plus this subsequent [[https://github.com/vufind-org/vufind/commit/1be2ac19500da9c5491087e41e4d98d0895aa0ff|bug fix commit]]). |
* :!: The itemLimit setting used for paginating holdings in some ILS drivers (Alma/Demo) has been moved from the "Holds" configuration to the more appropriate "Holdings" configuration. If you have taken advantage of this feature in a custom driver or if you have changed it in your driver's .ini file, you should move the setting -- see [[https://github.com/vufind-org/vufind/pull/1463|PR #1463]]. | * :!: The itemLimit setting used for paginating holdings in some ILS drivers (Alma/Demo) has been moved from the "Holds" configuration to the more appropriate "Holdings" configuration. If you have taken advantage of this feature in a custom driver or if you have changed it in your driver's .ini file, you should move the setting -- see [[https://github.com/vufind-org/vufind/pull/1463|PR #1463]]. |
* Some minor improvements have been made to item status display logic; if you notice an unexpected change in behavior, see [[https://github.com/vufind-org/vufind/pull/1466|pull request #1466]] for details. | * Some minor improvements have been made to item status display logic; if you notice an unexpected change in behavior, see [[https://github.com/vufind-org/vufind/pull/1466|pull request #1466]] for details. |
| * Some changes to record collection creation have been made for performance reasons, but they should not change behavior; see [[https://github.com/vufind-org/vufind/pull/1488|#1488]] for details. |
* The title_sort field MARC indexing rule has been made more explicit, instead of using a custom method. In the unlikely event that you have customized the getSortableTitle method in SolrMarc, you may need to adjust your settings. See [[https://github.com/vufind-org/vufind/pull/1393|pull request #1393]]. | * The title_sort field MARC indexing rule has been made more explicit, instead of using a custom method. In the unlikely event that you have customized the getSortableTitle method in SolrMarc, you may need to adjust your settings. See [[https://github.com/vufind-org/vufind/pull/1393|pull request #1393]]. |
* The default controller permission is now "null" rather than "false" -- this is functionally identical, but it is a change needed to support the new configuration options in [[https://github.com/vufind-org/vufind/pull/1395|pull request #1395]]. In the unlikely situation that you have customized a controller with an accessPermission property of false, you will be unable to override it with the new configuration settings unless you change the value to null first. | * The default controller permission is now "null" rather than "false" -- this is functionally identical, but it is a change needed to support the new configuration options in [[https://github.com/vufind-org/vufind/pull/1395|pull request #1395]]. In the unlikely situation that you have customized a controller with an accessPermission property of false, you will be unable to override it with the new configuration settings unless you change the value to null first. |