| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| legacy:installation:migration_notes [2015/12/14 16:42] – ↷ Links adapted because of a move operation demiankatz | legacy:installation:migration_notes [2015/12/14 18:12] – ↷ Links adapted because of a move operation demiankatz |
|---|
| Check the Solr configuration in the solr directory and the SolrMarc configuration in the import directory. These are not touched by the upgrade script and will most likely require some manual adjustments. | Check the Solr configuration in the solr directory and the SolrMarc configuration in the import directory. These are not touched by the upgrade script and will most likely require some manual adjustments. |
| |
| 1.1's Solr schema has some differences from 1.0.x's (to support new features like [[:tracking_record_changes|tracking record changes]], to eliminate some unused legacy fields, and to resolve issues like [[http://vufind.org/jira/browse/VUFIND-259|VUFIND-259]] and [[http://vufind.org/jira/browse/VUFIND-322|VUFIND-322]]). The upgrade script does not attempt to merge your customizations to the Solr schema or SolrMarc MARC mappings with the new installation. You will have to do this by hand. | 1.1's Solr schema has some differences from 1.0.x's (to support new features like [[indexing:tracking_record_changes|tracking record changes]], to eliminate some unused legacy fields, and to resolve issues like [[http://vufind.org/jira/browse/VUFIND-259|VUFIND-259]] and [[http://vufind.org/jira/browse/VUFIND-322|VUFIND-322]]). The upgrade script does not attempt to merge your customizations to the Solr schema or SolrMarc MARC mappings with the new installation. You will have to do this by hand. |
| |
| Once you are satisfied with your SolrMarc configuration, [[indexing:re-indexing|REINDEX ALL OF YOUR RECORDS]]. Attempting to run 1.1 with a 1.0.x-generated index will not work correctly. | Once you are satisfied with your SolrMarc configuration, [[indexing:re-indexing|REINDEX ALL OF YOUR RECORDS]]. Attempting to run 1.1 with a 1.0.x-generated index will not work correctly. |
| * VuFind's Javascript files have been moved around so that more JS code is contained inside the theme directories. This allows the introduction of a new {js} Smarty tag that includes Javascript files in [[legacy:vufind_1.x_developer_manual:user_interface_customization#theme_inheritance|theme inheritance]], which makes local customization easier than it used to be. However, it means that if you have hard-coded Javascript paths in your custom templates, you should replace them with appropriate {js} calls, and if you have customized any of the ajax.js files previously found under the web/services directory, you will need to move your customizations to the renamed files in the web/interface/themes/[your_theme]/js directory. | * VuFind's Javascript files have been moved around so that more JS code is contained inside the theme directories. This allows the introduction of a new {js} Smarty tag that includes Javascript files in [[legacy:vufind_1.x_developer_manual:user_interface_customization#theme_inheritance|theme inheritance]], which makes local customization easier than it used to be. However, it means that if you have hard-coded Javascript paths in your custom templates, you should replace them with appropriate {js} calls, and if you have customized any of the ajax.js files previously found under the web/services directory, you will need to move your customizations to the renamed files in the web/interface/themes/[your_theme]/js directory. |
| * All AJAX calls have been changed to use JSON instead of XML, and the AJAX handlers in the various web/services subdirectories have been consolidated into fewer files in the web/services/AJAX directory. If you have customized any AJAX-related code, you will need to do some work to reconcile it with the new layout... but take comfort in the fact that the new method makes everything significantly less complicated! | * All AJAX calls have been changed to use JSON instead of XML, and the AJAX handlers in the various web/services subdirectories have been consolidated into fewer files in the web/services/AJAX directory. If you have customized any AJAX-related code, you will need to do some work to reconcile it with the new layout... but take comfort in the fact that the new method makes everything significantly less complicated! |
| * The [[legacy:vufind_1.x_developer_manual:supporting_a_new_metadata_format|record driver]] interface has been slightly changed to move real-time holdings lookup inside the record drivers, rather than having it hard-coded in the Record/Holdings controller. This makes it easier for you to control which records VuFind looks up in your ILS. If you are using custom record drivers, you may need to make some minor adjustments to account for changes to getHoldings(), but for most common applications this will not make a difference to you. You may also need to implement the new getXML method introduced for [[:tracking_record_changes#oai-pmh_server_functionality|OAI-PMH server support]]. | * The [[legacy:vufind_1.x_developer_manual:supporting_a_new_metadata_format|record driver]] interface has been slightly changed to move real-time holdings lookup inside the record drivers, rather than having it hard-coded in the Record/Holdings controller. This makes it easier for you to control which records VuFind looks up in your ILS. If you are using custom record drivers, you may need to make some minor adjustments to account for changes to getHoldings(), but for most common applications this will not make a difference to you. You may also need to implement the new getXML method introduced for [[indexing:tracking_record_changes#oai-pmh_server_functionality|OAI-PMH server support]]. |
| * Thumbnail URL generation (using bookcover.php) is now largely controlled by the getThumbnail method of the record driver -- this allows easier customization/overriding without huge amounts of template editing, but you may have to update custom templates if they are doing inline generation of bookcover.php links. | * Thumbnail URL generation (using bookcover.php) is now largely controlled by the getThumbnail method of the record driver -- this allows easier customization/overriding without huge amounts of template editing, but you may have to update custom templates if they are doing inline generation of bookcover.php links. |
| |
| === Automation === | === Automation === |
| |
| If you want to take advantage of the new [[:alphabetical_heading_browse|alphabetical heading browse]], be aware that you will need to add heading generation to your automated update process in order to keep the browse lists in sync with your index. | If you want to take advantage of the new [[indexing:alphabetical_heading_browse|alphabetical heading browse]], be aware that you will need to add heading generation to your automated update process in order to keep the browse lists in sync with your index. |
| |
| ===== Upgrading to 1.0.1 ===== | ===== Upgrading to 1.0.1 ===== |
