User ID

UID

Assign a unique identifier — login ID — for each staff member.

Enter an alphabetic, numeric, or alphanumeric character string, without embedded spaces, of no more than 25 characters total.

Input Values

VALUE

This field is populated after a record is updated, with the User ID and constructed full name values, in both "Last, First Middle" and "First Middle Last" name order.

Enter any other (unique) values, in separate occurrences, that will be useful shortcuts (e.g., nicknames) in doing data entry in one of the databases that uses the application users records as an authority (e.g.,the Management Notes field in all databases; Accessioned by in Accessions; Inventoried by in the Catalog).

Direct input of one of these alternative values will automatically be translated into the official User name in the field or subfield for which the record is an authority.

Last Name

LAST

Enter the user's last name.

First Name

FIRST

Enter the user's first name.

Middle Name/Initial

MID

Optionally, enter the user's middle name or initial.

User

USER and USERF

(not shown in form) The full-name values in these fields are constructed when you update the record to facilitate searching and for use in reports and representing users in the data records:

USER: Lastname, First Middle

USERF: First Middle Lastname

Salutation

SAL

Select a title/honorific from the list box.

Values: Mr., Mrs., Ms., or Dr.

Modify the listbox to add other titles.

Employee Number

UNUM

(optional) Enter the unique identifying number or barcode assigned within your organization to the employee.

Date Hired/Terminate

DATE

(optional) Use the two subfields of this field to maintain a history of start and termination dates.

Type/Class

TYPE

(optional) Use this field to classify the type of employment associated with the staff person. Modify the listbox to reflect the types of values applicable in your institution.

Authority. Listbox values (.KCALIST) record: USERCLASSES

Lookup/Picklist Settings

Settings in the two fields of this section establish the names that will be displayed in the Picklist and the validation action that will be taken when staff enter valid user names/IDs directly.

Valid values — i.e., those set to Accept or Confirm — will be included in the Picklist display and validated with direct input.

     Action

ACT

Select from the list box one of these values:

Accept: to establish the person as a currently valid user.
Confirm: to establish the user as valid but with some conditional-use. The Message (see below) that you fill in to describe the condition will be generated in an information Alert.
Reject: to remove the name (e.g., for retired employees) as being valid but to keep the record for historical reasons (see also the Delete option in the Edit form, in the Application Access field group).

     Message

MSG

For any records set to Confirm or Reject, use this field to provide an explanatory message that will be generated in the information or error Alert. The field is limited to 1024 characters.

Security Permissions

ACCES

(required) Settings in these two subfields determine the records users have access to among those released to the Public Catalog. (Index displays are also restricted to words and full terms from those records to which the user has access.)

Subfields: level |g group

• If you are not implementing record-level restrictions, use the default values delivered with the application: Unrestricted |g OPENACCESS.
• If you are implementing record level and/or file-level restrictions, assign all users to the default values and, in addition, insert occurrences to add each combination of security level/access groups that apply, e.g., Confidential |g MGT.

The same field and list of values in each subfield are also used in Catalog records to represent the required access permissions. When Catalog records are created, a QCODE field is constructed that combines the two subfield elements, e.g., Unrestricted-OPENACCESS. This QCODE field is used automatically by STAR when Staff and Public Catalog searches are executed, with $QCODE settings in the current user's login record that are constructed from data you provide in this field.

     Security Level

ACCES|_

In the first subfield, accept the default. If you are implementing record-level restrictions, add new occurrences to assign the user to the one or more other levels that you have established (e.g., for Confidential; Secret).

Authority. Listbox values (.KCALIST) record: SECURITY-LEVEL

     Group

ACCES|g

In the second subfield, accept the default. If you are implementing record-level restrictions, select from among other groups that you have established (e.g., MGT; LEGAL).

Authority. Listbox values (.KCALIST) record: SECURITY-GROUPS

QCODE

Security Code

(not in form; is automatically constructed after you add or edit a record, and constructed $QCODE value is added to the Dollar Variable field of the USERS record) This value is constructed automatically from the occurrences of security level and-group data you specify in the application users record, in a combined form of, e.g: level1-group1\level2-group2.

If a user belongs to more than one combination level-group, the list for the USERS record will be constructed with the backslash so that STAR will OR the values together in applying record-level and index display restrictions.

Acess Codes for Other Systems

(optional) Use this management field to track the assignment of access codes for online systems that require users to identify themselves.

     Code/ID

SACOD|_

Enter in this first subfield separate occurrences for assigned codes/IDs used in accessing one or more of the online services.

     Type

SACOD|t

Use this second subfield to relate each code/ID to the online service to which it applies.

Authority. Listbox values (.KCALIST) record: USERACCESSCODES

Department

DPT

(optional) Use to associate a staff person with his or her department/unit.

Authority. Listbox values (.KCALIST) record: DEPARTMENTS

Address/Mail Stop

ADDR

Enter an internal address, e.g., a mailstop, or a full address using individual occurrences for each address line. These data are used in generating a valid address for selected task reports that incorporate data from this database.

Telephone Number

TEL

Enter one or more occurrences of telephone numbers or extensions and, as applicable, use the second subfield for a contact note.

Mobile Telephone Number

CELL

Enter the staff member's cell phones and use the second subfield for a contact note.

Fax Number

FAX

Enter one or more occurrences for fax numbers and applicable notes.

Email Address

EMAIL

Enter one or more occurrences for email addresses.

Notes

NOTES

Use this long-text field for more contact data or additional information about the user.

Application User Type

ATYPE

Except for the anonymous-user login record (or other end-user login records you create for implementing security permissions), choose between the two Staff-... options so that the users will be considered valid (and included in the Picklist) for fields controlled by this database.

STAR Login Password

PW

(required) Passwords can be alphabetic, numeric, or alphanumeric, up to 14 characters in length.

Delete STAR Application Login Record

—

[edit form only] When this checkbox is checked, the STAR User ID and Password fields will be emptied and the USERS record deleted in an automatic global operation.

Alternatively, to keep the record for historical purposes, change the Picklist Action setting to Reject (see first field group).

Application Welcome Name

WNAME

[$ARCHUSER; Staff session only] Enter the staff member's name or nickname, to be used by the system on the Welcome line in the upper right-hand corner of each session page.

No. of Logins

NLOGS

If you set a number greater than 1, the same STAR Application User ID can be used multiple times, up to the maximum of this value and the availability of license slots at any given time.

In Staff session user records: set this field to a minimum of 1 or, if you have a sufficient number of full licenses, to a higher number so that the user can start another session if he or she did not Exit properly and is still considered to be an active user by STAR Web.
In the anonymous-user Public Catalog session login record: Set this field to the maximum of your search-only licenses or a number representing a combined total of search-only and some of your full licenses.

License Group

LIC

If you have implemented groups in the STARLICENSES database to reserve sessions for users in particular groups (e.g., Staff session users), enter a valid Group Name.

For more information, see the STAR System Management manual or contact Customer Support to assist you in setting up license reservations.

Notify Flag

NOTFY

This setting is used only in classic STAR and STAR Client to implement the generation of messages to the desktop when globals have been completed.

Interface

IF

This field determines the Interface (and license type) available to the user, from among these choices:

For Staff session users: set this field to STAR Web, which allows for both searching and data entry in SKCA. If the same ID will also be used with any of the other STAR interfaces, enter additional occurrences to authorize access, e.g., classic STAR, STAR Manager.
For the anonymous-user Public Catalog session record: set this field to STAR Web Search

More information about this field is available in two STARdoc files in the "sysman" folder: the STAR System Management manual section on Security (see secure.pdf or, for STAR/Windows systems, securew.pdf,) and in the Controlling Access to STAR by Interface document (see access.pdf).

Application Prefix

APRE

Unless you have worked with Cuadra Support to replicate the application, assign the default prefix for the Customer Version: LThis prefix ($APP-PREFIX setting) is used to distinguish the CA and Customer versions of the STAR databases and globals. The CA version prefix is: M

Web Sessions

WSESS

This repeating field is used to construct the $WEB setting in the USERS record. Specify whether the user can access one or both of the STAR Web sessions, represented by a path/file name for the .web session file.

For staff login records: select the second of the two, to provide access to the Staff session and, in a separate occurrence, the first of the two, to allow access also to the Public Catalog session.
For the anonymous-user record: select only the first of the two session files.

Web SERVER Database

WSERV

(protected) This $WEBSERVER name represents the standard application system database that is used for search-related specifications.

Web Group

WGRP

This $WEBGROUP setting applies only to Staff session users. Use the default at startup for all staff members. Over time, you may decide to set up different group names in the listbox for sharing Staff session saved searches.

Additional Variables

ODV

This field is used to enable and configure features of the Public Catalog session.

Clicking the Public Catalog link in the Staff session uses the anonymous-user login, so that the enabled/configured features will apply.

If staff members log into the Public Catalog session, the settings in their own records apply.

This field is also used to specify the STAR Filing System (SFS) Repository to which the staff member can attach image/electronic documents, in the SFS-defined fields of the Catalog and Accessions databases. If a valid repository is not specified, staff will not be able to use the SFS Import function when creating and editing records.

For details, see Dollar Variables.

Server Log File Settings

TRACE

Leave the default setting so that log files (e.g., userid.serlog) will be available for use by Customer Support if problems are reported.

Idle Timeout

WIDLE

This setting defines a first-level timeout for inactive users—i.e., the amount of time that is to elapse before a user is automatically exited from the session if no request has been submitted to STAR from the user's desktop browser.

After the "idle" time period has expired, STAR releases the license slot for use by others but continues to remember the user's session if the person returns, so the user can resume where he or she left off.

Values are expressed in seconds (e.g., 1200 represents 20 minutes).

For the Public Catalog session login ID record: This setting is typically set to 600 or 1200 or 1800.
For Staff session login ID records: The setting delivered with the "skca" ID uses an 8-hour setting; see discussion below. A Staff session ID will not be "idled" out by STAR Web if there's an open record.

Kill Timeout

WKILL

This setting defines a second-level timeout, also expressed in seconds, after which STAR terminates the session and the user cannot resume where he or she left off when they are logged back in.

The termination timeout period is typically set to the same or a larger number than the idle timeout.

For Staff session login ID records: If you have a sufficient number of STAR licenses, we recommend that, for staff who will be working with the application throughout the day, you set the time to 8 hours, which represents the number of seconds used in the "skca" startup ID record.

If you do not want to use an "all-day" setting, consider one that is sufficiently high to accommodate those staff members who will be browsing a large number of retrieved records in a report to help ensure that the timeout does not get triggered while staff are still working locally.

Idle Timeout

IDLE

(optional, for users authorized to use classic STAR) This field can be filled in with some number of seconds (e.g., 300 for 5 minutes).

A minimum of 10 seconds is required if you implement this feature, to have inactive sessions terminated (with an EXIT IGNORE).

Management Notes

MNOTE

Use this field for leaving a footprint when making changes in the record. Subfields:

|_. added by (staff member). Authority. Users (.ARCHUSERS) (Direct input/valid names only)
|d. date (populated automatically with "today's" date but can be modified)
|n. comments

Record Created

STAMP

(Edit form only) This non-editable field represents data captured automatically with the standard STAR Audit Create rule.

Subfields (as stored): userID |D yyyy 0m 0d |T hh:mm:ss

Record Updated

UP

(Edit form only) This non-editable field represents data captured automatically with the standard STAR Audit Update rule—"last updated" data.

Subfields (as stored): userID |D yyyy 0m 0d |T hh:mm:ss