In no particular order:
-
Always check settings at the branch level - settings inherit down, except when they don’t
-
Always check which branch is being used (for statistical reporting and circ rules governance): patron branch, item branch, or transaction branch
-
Don’t use shelf location when you need collection codes
-
Don’t use collection codes when you need material types
-
Record any changes that will help you account for significant changes to reported stats down the road, e.g. changes to policy settings, changes to definitions, large weeding projects or fee waives
-
Learn basic T-SQL
-
Connect with people who know SQL and might share useful queries
-
Get familiar with the Polaris database tables (use the CHM file)
-
Create permission groups and NEVER apply permissions individually
-
Regular check-in with your site manager; submit tickets for all questions so that you can track them, refer to them later, escalate them, etc.
-
Get familiar with how holds processing works (especially in large systems or consortia)
-
Restrict access to modify the postal code table
There was a great discussion in the forum, so if you were there please add anything I missed in the comments. If you were not there, what are your top tips?