1 Primo Best Practices Andrew Walsh Team Lead, NA Primo Support Teams andrew.walsh@exlibrisgroup.com
Copyright Statement 2 All of the information and material inclusive of text, images, logos, product names is either the property of, or used with permission by Ex Libris Ltd. The information may not be distributed, modified, displayed, reproduced in whole or in part without the prior written permission of Ex Libris Ltd. TRADEMARKS Ex Libris, the Ex Libris logo, Aleph, Alma, SFX, SFXIT, MetaLib, DigiTool, Verde, Primo, Voyager, MetaSearch, MetaIndex and other Ex Libris products and services referenced herein are trademarks of Ex Libris, and may be registered in certain jurisdictions. All other product names, company names, marks and logos referenced may be trademarks of their respective owners. DISCLAIMER The information contained in this document is compiled from various sources and provided on an "AS IS" basis for general information purposes only without any representations, conditions or warranties whether express or implied, including any implied warranties of satisfactory quality, completeness, accuracy or fitness for a particular purpose. Ex Libris, its subsidiaries and related corporations ("Ex Libris Group") disclaim any and all liability for all use of this information, including losses, damages, claims or expenses any person may incur as a result of the use of this information, even if advised of the possibility of such loss or damage. Ex Libris Ltd., 2014
Agenda 3
Introduction 4 Who am I?
A Quote 5
Agenda 6
FE Best Practices 7 Custom Files Use a customized directory in fe_web Use an Institution or View sub-directory in customized Replicate the fe_web structure as needed Labels & Codes Use a foreign language Make your codes different from your labels (fct_books vs. books) View Search Scope changes Edit the View Search Scope Save the View Search scope Edit all Tabs containing the View Search Scope Save the Tab Deploy the View
External Linking 8 DO NOT DO NOT USE search.do Unapproved & Unsupported DO Use dlsearch.do el Commons Total Care request information using a case Permalink Added in v4.6 Under the Actions menu
Port Forwarding 9 DO NOT DO NOT USE mod-jk Unsupported & Unapproved Do not put Primo behind a Proxy DO Use IP Tables or a Layer-7 aware device Add the proxy to the link Primo provides Open a case for assistance
Static HTMLs 10 DO NOT Edit the default static HTML files DO Copy the files to a customized sub-directory Update the View to use the customized version Keep a log of what was changed (e.g. diff) SP/HF Compare the customized file with post-sp file Update the customized file as appropriate
CSS Files 11 DO NOT Edit the default CSS files Customize a copy the default CSS files DO Only customizations in new CSS file Add CSS file to the CSS File Set Run a Deploy after updating a CSS file
JavaScript 12 DO NOT Include a new version of jquery Edit a default file DO Include your own JavaScript code Use the header or footer Make it easy to disable
Agenda 13
BE Best Practices 14 Pipes Schedule for off-peak hours Recommend once a day processing Once a Pipe has run it cannot be deleted Indexing No more than four (4) times per day Schedule for off-peak hours Schedule Indexing with DidYouMean once a week General Check Pipe Error Page Regularly Pipes can have many errors and still be successful Ensure IT knows how to check Pipes & Processes
Normalization Rules 15 DO NOT CHANGE control/recordid control/sourceid control/sourcerecordid Test extensively Use customized test records Focus on edge cases If no Sandbox, create a test Data Source RTA Triple check the NR rules used by your Pipe & by RTA Triple check the display/availlibrary rules
DeDup & FRBR 16 DeDup Make sure every record has a unique ID candidate vector Make sure every record has a unique ID matching vector If no unique ID, use control/recordid Disable rules for invalid unique ID FRBR Don t create FRBR vectors for common titles Watch out for records that have collections of titles Testing FRBR & DeDup Testing Tools available in the BE N.B. FRBR & DeDup are non-transitive A=B, B=C, A C
MetaLib 17 MetaLib user for Primo MUST match the MetaLib Institution Code Owns the QuickSets searched by Primo Updating a MetaLib QuickSet Edit the View Search Scope Confirm the list of MetaLib QuickSets is correct Save the View Search Scope Edit and re-save any Tab using the View Search Scope Deploy the View PDS MetaLib must use the same PDS server as Primo DO NOT add the Primo server to the MetaLib on-campus list
Oracle Best Practices 18 DO NOT DO ANYTHING DO Open a Case
Agenda 19
General Best Practices 20 Primo SP/HF Keep up to date Review Release Notes & Known Issues Pay attention to Implementation Notes Especially if you are Total Care or Multi-Tenant Direct Log File Cleanup 1 Check monthly Use BE interface Follow Institutional Document Retention Policies OS Patches 2 Apply at least every quarter DO NOT update any software in /exlibris
Topology Best Practices 21 All-In-One Schedule Pipes & Processes during off-peak hours Set reasonable expectations regarding downtime 2-Tier MFE Monitor BE log for Master FE failover Restart both SE Indexers when the Master FE changes Ensure SP/HF applied to p4_2 on BE server N+1 MFE N must always be greater than 1 (i.e. min 6 servers) Restart SE Indexer first; then failover remaining SEs During SE failover search results are missing 1/N records
My Personal Recommendations 22 Technical Seminar Come as often as you can Send as many people as you can Open Cases Open Early Open Often Include lots of details Cases What you are trying to achieve? Expected Results Actual Results Detailed replication steps
Agenda 23
Resources 24 Primo System Administration Guide Primo Technical Guide Primo Back Office Guide Primo Version 4 Highlights Primo Release Notes & Known Issues
Agenda 25
Thank You! 26 Thank You! andrew.walsh@exlibrisgroup.com