Using the Events area, the Design Analytics user may create reports/dashboards that provide more details about events generated through Alma. Each time a cataloger creates, deletes, or updates an MMS record, for example, a new event is generated in Alma. By using the Events Subject Area, you can create an activity report and present how many new MMS records were created by each user.
The following events are not included in the Events subject area:
|3008||File start stage|
|3009||File end stage|
|3016||Record merged with existing record|
|3059||Error during harvesting|
|4146||Resource was not found in partner's catalog|
|6129||External System Rejected User|
|8000||Publishing to primo|
|8012||Information of linking PA number of linking|
|9033||Attachment upload status|
|9153||Succeeded to update users|
The following lists the fields available in Events:
Events – Field Descriptions
The Event Keys table is a fact table that stores all events generated in Alma. It contains all keys and values associated with events.
|Event ID||Stores the unique ID of the event|
|Creator||Stores the creator of the event|
|Event Duration||Stores the duration of the event in seconds|
|Session ID||Stores the session ID to which the event was registered|
|Key Name||Stores the key name – a category of event, such as Account Type and Action.|
|Key Value||Stores the key value – a member of the key name such as Public and Staff.|
|Num of Events||Stores the calculated fields that count all the unique events (by distinct event ID). Each event can have several entries in the table with different keys and values.|
The Event Metadata table is a dimension table that stores additional details about the event. The primary key is EVENT_TYPE.
|Event Type||Stores the event code.|
|Description||Stores the description of the event|
|Is Enabled||Indicates if this event is recorded|
|Message Description||Stores the message description with fillers for the parameters|
|PURGE_POLICY||The number of months to save the event. Empty or 0 means that the event is never purged|
The Category table is a dimension table that stores the category code and description of the event. The primary key is EVENT_TYPE.
|Category Code||Stores the category code||Possible Values:
|Category Description||Stores the category description|
The Module table is a dimension table that stores the module code and description of the event. The primary key is EVENT_TYPE.
|Module Code||Stores the module code that the event associated with such as acquisition, inventory, migration, and repository|
|Module Description||Stores the module description|
The Submodule table is a dimension table that stores the submodule code and description of the event. The primary key is EVENT_TYPE.
|Sub Module Code||Stores the submodule code that the event associated with such as currency, PDA cleanup, and purchase orders|
|Sub Module Description||Stores the submodule description|
The Severity table is a dimension table that stores the severity code and description of the event. The primary key is EVENT_TYPE.
|Severity Code||Stores the severity code of the generated event such as error, fatal, information, and warning|
|Severity Description||Stores the severity description|
The Event Date table is a dimension table that stores details about the date of the event such a month, year, and quarter. Key fields may be used when calculations are required. Descriptions fields may be used for formatting the display of the report.
Using this dimension, users may drill down from year to month to the specific event. The number of events are accumulated to the relevant level in the hierarchy.
|Date Key||Stores the date in the format 2/29/2012|
|Month Key||Stores the month of the date in number format such as 2 for February||This field is useful when you want to sort by month|
|Month Desc||Stores the month of the date in month description format such as February|
|Year Key||Stores the year of the date in string format such as 2012|
|Year Desc||Stores the year of the date in string format such as 2012.|
|Full Month Desc||Stores the month and the year of the date in a display format such as Feb 12|
|Full Month Key||Stores the month in a number format such as 9 for September and the year|
|Full Quarter Desc||Stores the quarter of the date in a display format such as Q1 and the year|
|Full Quarter Key||Stores the quarter of the date in a display format such as 1 and the year|
|Quarter Desc||Stores the quarter of the date in a display format such as Q1|
|Quarter Key||Stores the quarter of the date in a display format such as 1|
|Date Filter||Used to filter report results by date.|
|Event Date||Stores the Hierarchy column that allows the user to drill down from the year to the month to the specific event date. Using this column provides the user with the option to view the accumulative measures in each level of the hierarchy.|
The Security Events table is a dimension table that stores details of security events generated by Alma. This table stores events associated with CATEGORY=SECURITY and MODULE=USER_MANAGEMENT. Using this dimension, a user may create the FERPA (Family Educational Rights and Privacy Act) reports that indicates which users in Alma may view details of other users.
|Accessing User ID||Stores the user ID of the user that accessed other user information|
|User ID||Stores the user ID of the user whose details have been seen|
|User Accessing Operations||Indicates when the Viewed operation was used to access the information|
|User Subentity List Name||Describes the entity that has been seen such as address, email, and so forth.|
The shared Institution dimension allows the Network Zone to view reports according to institution. It is available in every subject area. It contains the following fields:
|Institution Code||The code of the institution.|
|Institution Name||The name of the institution.|
|Institution Timezone||The timezone of the institution|
|Data Available As Of||When the data became available to analytics|
|Data Update As Of||When the data was taken from Alma|
If an analytics report is run from the Network Zone in a collaborative network implementing a Network Zone, all member institutions are included in the report for Institution Code and Institution Name.
If an analytics report is run from an institution that is not part of a collaborative network implementing a Network Zone, only the single institution from which the report is run is included in the report for Institution Code and Institution Name.
Reports involving data across a collaborative network implementing a Network Zone may take longer to run than reports within one institution.
Shared Dimensions with Other Subject Areas