This article is specific to "on-site" installations where clients manage their own server. This article does not apply to "hosted" clients on PdMagic servers.
Crash Magic SYS data is all record types maintained by the system. This includes:
oUser groups
oUsers - Includes the .config and .shared users that hold the configuration resources
oPSRattrs - Also referred to as "resources" and "templates") These make up a client configuration.
oProjects
oStudies
oReports
There are several methods available to manage SYS data:
oManually, using the administration form on the program.
oImport, using the administration form on the program.
oImport, using the Login form's "Import configurations ..." option.
Crash Magic utilizes a “configuration” to interpret the crash data used by your agency. A configuration is simply a collection of resources, each referred to as a “PSRattr”. Parts of every configuration are protected and editable only by PdMagic. Other parts of your configuration are available to be edited by you, the Crash Magic user. When using Crash Magic’s hosted server, PdMagic maintains the protected part of your configuration for you. When Crash Magic is installed on-site, it is important that our clients are able to update the protected parts of the configuration as provided by PdMagic.
For some agencies, with a completely custom configuration, there is only the “.Master” configuration and the client configuration. However, in most cases there are several levels in play. You can view these levels by logging into the administration form in the program. There you will see a “tree” of user groups containing configurations. It will contain “.Master”; a state level configuration; often some intermediate, like county or state configurations; sometimes a PdMagic reports configuration; and then your agency configuration.
|
A typical configuration “tree” containing:
o.Master group – contains configuration resources common to all agencies and all users. This group of resources is updated with every version of the program and is not editable by any group administrators. Even PdMagic only updates this through the new version installation process. In fact, any changes to this configuration will be automatically overwritten with the next version. It’s essentially part of the program. This is considered a “protected” group. o“_” groups. Groups that start with an underscore contain shared resources. Most agencies in a state will share the same database fields, lookups and overall configuration. They will all reference (inherit) the resources in these groups. An example group name might be “_OR@CDS” where the “OR” indicates the state and the “CDS” indicates the database or crash data system used by the agency. This type of group name might also be called “_MD@Base”. In this case, the “MD” is the state and “Base” indicates that this is the base configuration for all MD clients. Further down the list might be report resources created specifically for a client. For example “_OR@CDS_Schematics” are collision diagram schematics created specifically for the state of Oregon and only useful to clients with Oregon data. A group like this might also be called “_MD@PdReports”, again the first part names the state for which the reports work, and the second part “PdReports” describes the group’s contents. Most “_” groups are managed by PdMagic and are protected. oAgency group. There will only be one agency group in any configuration. This group will almost always follow the naming convention of <StateAbbreviation>@<AgencyName>. (e.g. OR@Eugene; MD@DOT; CO@Boulder; etc.) This group contains content only useful to that agency. This group is also the only group that clients have access to edit. Clients may edit content in the .shared user or any of the named users. They can not edit the .config or the .tools user content. Those are provided by PdMagic and are protected. |
When hosted on the PdMagic server, we update the protected portions of the configuration. Clients may use configuration inheritance to add / edit configuration resources in the .shared or individual user accounts. This makes it possible to customize and override all of the protected resources provided by PdMagic. However, when hosted on an agency server it can be necessary to update the protected resources as PdMagic makes changes to them. These resources should be imported exactly as provided by PdMagic and not edited.
Imports of configuration resources (PSRattrs) are also known as SYS table imports. There are two types of configuration imports that an on-site administrator might need to perform. Both are the result of PdMagic making changes to your official configuration.
•Entire user group (shared resource). These are the “_” prefixed groups. These user groups are maintained as a unit containing a .config / .shared / .tools user. It is not appropriate to update just one or two resources within the group. Rather it is imperative to import the entire user group including all the user records in that group.
•.config within the agency group. Most of the resources in the agency group (<ST>@<Agency>) are not protected, but rather are owned by the group (.shared) or the individual user accounts. Only the .config user is protected.
These resources may be changed by logging in as the MasterAdmin. However, this is a precarious account to log into and makes possible changes that could completely disable the Crash Magic system. PdMagic is not responsible for repairing systems damaged by a client who logs in as a MasterAdmin. Instead a utility is available on the login form that can be used to update on-site shared user groups using an "Import configurations user".