1 – Name & contact information parameters
Name & contact information parameters set the names and addresses that will be used by RefTracker.
1.0 Library/Organisation name: This name is used to identify your organisation in emails to clients.
The text that you enter here can be reused in RefTracker, such as in templates and QuickText, using the variable {parm_organisation}.
This parameter is translatable.
1.1 Service name: This name is used to identify your reference service in emails to clients.
The text that you enter here can be reused in RefTracker, such as in templates and QuickText, using the variable {parm_service_name}.
This parameter is translatable.
1.2 Welcome message: This is the heading that will be displayed at the top of your client home page. The distribution value says “Welcome to our service”, but you may prefer to include your library name and/or the name of your reference service here. This parameter is translatable.
1.5 Organisation URL: This is the URL of the web page that you want your client users to return to when they choose the library home page link in the bottom left of each page, or behind your library logo, to jump out of RefTracker. It is also made available to staff as the first bookmark in the QuickSearch drop down list of information resources. You might like to specify your library home page, or perhaps a specific page within your site that refers to reference materials available – its your choice, but you need to enter the entire URL e.g. https://www.altarama.com.au. or server/intranet/index.htm
If you do not enter a URL here, these links will not appear for either staff or clients.
1.6 Organisation URL description: This is the text that will appear in the library home page link in the bottom left of each client page, and as the name for this link in the QuickSearch drop down list. Requires parameter 1.5 to be set to be effective. This parameter is translatable.
1.10 Contact phone: Shows in the RefTracker error and offline notification pages via use of its variable {Parm_ContactPhone} in the error templates that are modifiable at System>Utilities>Administration utilities>Template editor (text). If this parameter is blank no phone information will be displayed.
1.11 Contact email: Shows in the RefTracker error and offline notification pages via use of its variable {Parm_ContactEmail} in the error templates that are modifiable at System>Utilities>Administration utilities>Template editor (text). If this parameter is blank no phone information will be displayed.
1.12 Contact URL: Shows in the RefTracker error and offline notification pages via use of its variable {Parm_ContactURL} in the error templates that are modifiable at System>Utilities>Administration utilities>Template editor (text). If this parameter is blank any URL provided in Parameter 1.5 Organisation URL will be displayed.
1.20 Send error reports to: Shows the email address/es that emails describing errors occurring in your system will be sent to. It is normally set to the email address of the Altarama support team in your part of the world (errorreportsAU@altarama.com, errorreportsUK@altarama.com, errorreportsUS@altarama.com). If you would like your own staff, such as your RefTracker system administrator, copied on these reports please add their email address/es to this parameter (separated by a semicolon and no space). All in-house customers should add a local email address to parameter 1.20 so that someone local is advised of these sorts of issues.
Having these emails come directly to Altarama means that Altarama gets a more complete picture of the errors occurring in customer systems, and can diagnose and start working on any required fixes at the earliest possible time.
Another advantage of adding addresses to this parameter is that the email addresses specified here are sent full details of the error being reported (as opposed to the summary message that is sent to the user who experienced the problem and your System administrator.
1.21 Copy user errors to Altarama: Normally (when this parameter is set to the default value of No), errors experienced by lower-level users only get passed through to Altarama if the System admin chooses to onforward them – so that, hopefully, multiple errors only get sent once, after a System administrator has replicated the issue.
Se this parameter to Yes if you want Altarama to immediately see all errors being generated by your system. Altarama might make this change, or ask you to the make the change, in relation to resolving a reported issue.
Exercise:
Consider the effect of these parameters on your library’s requirements. Make any desirable changes, and if you make any, click on Save. Then in Select parameter group choose 2) Policies.