Skip to main content
ExLibris
  • Subscribe by RSS
  • ExLibris Dev

    General, User Interface

    User Interface

    Are there plans to redesign the Alma UI?

    A new Alma interface will be launched during 2017. A few screenshots of the the new design follow:
    Personalized Menu Bar via Quick Links; Persistent Search Bar:
    Find and manage users:
    A patron record:
    The acquisitions menu:

    General

    What types of messages and alerts are supported?

    For staff users, the system employs a roles based mechanism which allows the creation and management of specialized users that will perform different tasks.
    These tasks are part of Alma’s workflow engine which provides Alerts to these users to act according to the defined workflow. The following screenshot shows the ‘Tasks Widget’ which is displayed to users allowing them to enter directly to the relevant task they need to perform:

    Are edits and updates by staff users logged?

    Alma maintains a comprehensive audit trail of transactions made in the system, including the user ID, the exact operation and data that was accessed. The audit trail report is accessible and can be generated using Alma analytics reporting. Almost every operation made in Alma is logged and can be reported. The audit trail report also indicates the type of operation made in the system: view, edit, deleted etc. with an indication when the operation was made. Below you can see a screenshot of part of an audit trail report:

    What collaborative options are available in Alma?

    Some areas of collaboration:
    • Ability to add and edit records in the Community Zone.
    • Shared vendor records (with individual library accounts defining local parameters.)
    • Community reports in Analytics.
    • The potential to share data for benchmarking, (currently in development).
    • Community normalization rules in Resource Management.
    • Sharing of applications, integrations and expertise via the Ex Libris Developer Network.
    • Full two way communication in Resource Sharing (ILL) if both borrower and lender are using Alma.
    • Shared global authority files.

    Can staff view the public display (discovery tool) of a record directly from Alma?

    The imbedded Primo search box – available on the Alma dashboard supports this functionality:

    Limits

    What limits are there in size and number of values in data elements within records of various types?

    Alma manages various types of records in the catalog, based on MARC21 (e.g., bibliographic records) using the MARCxml format. There are no limitations in managing a record and its data elements, except where mandated by the MARC standard (for example, there is only a single LDR field in a record).
    Other types of records in Alma have both a fixed set of attributes and repeating, non-limited elements. For example, many records in Alma such as the user record, purchase order line, and others can have any number of notes fields or attachments.
    Where a record has a fixed set of attributes (e.g., a user record has fields for their first name, middle name and last name) these fields are added by Ex Libris, based on functional and business requirements. These fields have specific sizes, which are developed as described above, based on functional and business requirements, by Ex Libris.

    Is there a maximum character limit for notes?

    The User note in the patron record is limited to 2,000 characters.
    Other notes (all areas in Alma that use the notes infrastructure) are limited to 4,000 characters. There is no limit to the number of notes that can be added to a record.

    Time-out

    Are staff timed out after a specific period of time?

    The session timeout for Alma is 60 minutes. This means that if the staff user is not working in Alma for 60 minutes, his/her session will expire and he/she will be asked to login again. This cannot currently be configured by the institution. One minute before an Alma session times out, a warning message appears on the screen. You can cancel the timeout or log out. If you do not select either option, the session times out after one minute.

    Does Alma warn the user before a session time-out?

    One minute before an Alma session times out, a warning message appears on the screen. The staff user can cancel the time-out or choose to log out. If neither option is selected, the session times out after one minute.

    Identifiers

    Are all types of indentifiers unique within an institution?

    Alma leverages the industry-leading multi-tenancy solution based on Oracle VPD (Oracle Virtual Private Database). This means that any key in the database includes the unique institution ID, thus ensuring the separation between institutions at all levels, as well as our ability to ensure uniqueness across all institutions. Since access to the Alma database always includes the institution ID, uniqueness is delivered and maintained at all areas of the system with no limitation.

    Are identifiers validated for uniqueness at import or creation within records

    Alma automatically generates a unique ID for every bibliographic, holding and item record. This is a 15 string number, (the last three digits being the institution ID). An example of the unique ID for a bibliographic record:
    For holding records:

    Macros, shortcuts

    Can macros be used in Alma?

    Alma can be used with macros, using the HTML IDs of Alma page elements.
    Alma development uses Selenium as the web application automation tool for testing purposes. We use the HTML IDs (and xpath) for simulating users, and this can be used with macros as well.
    Note that there are some limitations when using macros—for example, the MD Editor is not macro-certified.

    Does Alma support the use of shortcut keys?

    Shortcut keys are available throughout Alma in a wide variety of areas:

    Does Alma support shortcuts and automation for repetitive tasks and processes?

    Streamlining currently labor-intensive processes was one of our primary goals in designing Alma. This goal has been achieved in a number of ways:
    • By providing readily available links to different areas of the system, making required data no more than one click away.
    • By providing task chains. Task chains are lists of actions that are:
      • Automatically carried out when different action are activated, such as when a record is saved or deleted
      • May be manually activated, for example for correcting a record while working on it at the Metadata Editor.
    Alma enables usage of hot keys, including functions where a large amount of error-prone, repetitive work is performed. This includes:
    • The circulation desk patron services area
    • The cataloging metadata editor area
    Task-oriented macros may be implemented using Alma’s Process Automation capabilities, which allow for tailoring a chain of tasks to be performed on a predefined set of data. This may include:
    • Bulk moving of item records
    • Normalization of bibliographic records
    • Cancelation of requests

    Is an auto-complete function available?

    Alma supports auto-complete in a number of areas of the system - for example:
    • Selecting patron in the Manage Patron Services
    • Selecting patron in the patron request forms
    • Applying funds to PO Lines
    • Selecting vendors for PO Line
    • Applying funds to Invoices

    Navigation

    Is it possible to navigate around a form and complete it without using a mouse?

    Alma forms can be navigated and completed using standard Windows navigation functionality. (e.g. Tab, Enter keys).

    How does the staff user navigate from one part of Alma to another?

    As a next-generation solution, Alma does not have different components or modules; rather, there are several entry points for performing particular functions within the system. The following screenshot shows the Alma menu, displaying links to all of the relevant tasks and functions for each staff member available from anywhere in the system.
    In addition, there are many links among relevant areas. For example, the metadata record will always be accessible for viewing and editing when working with an item without the need to exit one area of Alma to enter another. Note that only staff with the appropriate assigned role can access and make changes in the metadata editor. Changes to item status are made using the Physical Item Editor, accessible through an item’s listing in the Repository Search.

    Ease of use

    What options does Alma offer for streamlining labor intensive tasks?

    Streamlining currently labor-intensive processes was one of our primary goals in designing Alma. This goal has been achieved in a number of ways:
    • By providing readily available links to different areas of the system, making required data no more than one click away.
    • By providing task chains. Task chains are lists of actions that are:
      • Automatically carried out when different action are activated, such as when a record is saved or deleted
      • May be manually activated, for example for correcting a record while working on it at the Metadata Editor.
    Alma enables usage of hot keys, including functions where a large amount of error-prone, repetitive work is performed. This includes:
    • The circulation desk patron services area
    • The cataloging metadata editor area
    Task-oriented macros may be implemented using Alma’s Process Automation capabilities, which allow for tailoring a chain of tasks to be performed on a predefined set of data. This may include:
    • Bulk moving of item records
    • Normalization of bibliographic records
    • Cancellation of requests

    Does Alma allow for a multi-tasking environment?

    The Alma Task List provides the staff user with information about tasks that need their attention.
    The Task List is part of the persistent menu bar of Alma and therefore available from any page.
    The Task List has hypertext links for easy navigation to areas of the system where records require manual intervention. The Task List is sensitive to the user’s roles and privileges so that only acquisitions staff will see ordering and invoice-related tasks.

    Can a workflow be saved at any time without losing data?

    Throughout Alma there are places where records can be saved “mid-way” though a process to make sure changes are not lost.
    For example it is possible to ‘save’ an order before sending it to the vendor.
    Similarly, a metadata record can be saved as a draft before saving to the repository (catalog).
    Electronic resources can be edited in many stages until they are activated and “done”.
    Functions where manual intervention might be required (e.g. invoices, purchase orders, item records, etc.) can be saved in draft format.

    Customization, personalization

    Can the staff user personalize the Alma interface?

    Alma provides a state-of-the-art dashboard that the staff user can configure and customize according to his/her roles. Widgets that the user (based on his role) can select for display on the dashboard are created in Alma Analytics. The pre-defined reports are shown by default to the user (role-based). For example: if the user's role is Acquisitions Administrator, (s)he will be able to see expenditure trends during the last year. The user can arrange the reports and define which of them (s)he would like to see as part of the personalized dashboard. Below is an example of a circulation staff user’s personalized dashboard, displaying the user’s task list and relevant analytics. The user may add widgets as needed.

    What interface languages are supported?

    The Alma interface languages:
    German, French, Spanish, Italian, and Korean, Welsh and Chinese. Some examples follow:

    What branding options are available for Alma?

    Alma enables you to define a header logo, email logo, and/or login page logo for your institution. You can also change the default blue in the user interface to a different color. To configure Alma branding, you must have the General System Administrator role.
    These elements are configured on the Branding Management page:
    Alma also allows the institution to modify the CSS (and associated image files) that the system uses for the delivery tabs by uploading a customized CSS.
    You can view and configure skins from the Manage Skins page:

    How can Alma be customized?

    As a fully web based solution, Alma provides certain level of customizations for the user interface. The Alma web page colour scheme can be customized as well as the Alma dashboard with customization of widget view. Alma also supports the ability to customize the search results table columns by changing columns location. The size of the fonts can be controlled by using the browsers zoom in/out functionality.
    Throughout Alma list tables can be customized, enabling you to perform the following customizations:
    • Change the width of table columns.
    • Change the order of table columns.
    • Retain changes to the sort order of columns after moving to another page.
    • Hide and display columns
    Customizations are retained for each user and for each list after moving to another page,logging out, and so forth.

    Ease of management

    Is Alma easy to manage for small libraries but with flexible options for large libraries?

    Moving to the cloud lowers the required threshold for entry to basic management processes. In today’s systems, many mission-critical workflows require server access. The staffing requirements for basic management processes such as record loading or integrating data from other campus systems must be managed by a system administrator. Since Alma provides user-friendly and highly efficient interfaces for all tasks, the system expertise needed to manage the system is significantly reduced. Both Alma and Primo are hosted by Ex Libris and no local database expertise or maintenance is required.
    Configuration and profiling are done easily via a set of configuration rules per each process (e.g., acquisition, resource management). The system-managed workflows automate many currently manual processes, reduce error, and free staff to work on those tasks that require decision making.
    Alma’s basic design is based on two organizational levels, the Institution and the Library:
    1. The Institution is the basic level of data and workflow management in Alma; it also holds all of the institution, or local library, data. Some processes and configurations, however, may be managed at the Library level.
    2. The Library is one or more physical locations that are normally housed in a single building or in several buildings that are in close proximity to one another. It has locations and circulation desks that are familiar to the library patrons.
    An institution manages the following, accessible to all institution operators with the proper role:
    • User management
    • Vendors
    • Funds management
    • Licenses
    • Metadata management
    • Configurations
    In addition, an institution can make use of single
    • Integrated external systems such as ERP or SIS
    This is illustrated below:
    Alma is pre-configured with all batch jobs required for operation of the system. One needs only to decide to opt in or opt out of a scheduled job.This makes the configuration very easy to manage.
    The following screen capture shows the configuration areas, each of which includes configuration options that can be defined at the institution or library level.

    What is the expected level of local systems staffing required for managing Alma?

    Providing Alma as a cloud-based SaaS solution eliminates significant aspects of the work done typically by system administrators and DBA staff on systems installed on site. Local operations in Alma are primarily concerned with the administration of users and the configuration of local workflows. Both can be done centrally by the consortium.
    The table below summarizes all areas that are traditionally managed by local staff. Marked in green are areas that are performed by Ex Libris, and the purple areas are tasks that performed by the customer’s staff. Local tasks include setting firewall rules (to allow access to Alma cloud via a standard web port) or command lines that are no longer relevant with Alma since access is done via the application or through a dedicated API and web-services.
    As illustrated in the diagram, configuration and customization (in blue) are performed at the institution level, while Alma is delivered with settings that allow for faster time to production. Customers report and track service calls through the Ex Libris CRM system, with the benefit of 24x7 monitoring and the hub team.
    Alma provides a flexible environment that will allow the institution to maintain many tasks centrally, including integration development, customization, and purchasing. The library/consortia may also distribute all or part of such tasks, and work as a unified system across all members.
    Thanks to Alma’s flexibility, the library may choose to take several roles in Alma’s ongoing operation such as:
    • Help desk type support – functioning as Alma experts in resolving tier one issues that are primarily issues related to ‘know-how’’;
    • Troubleshooting for application issues – such as configuration issues;
    • Integration development using Alma’s API and web-services;
    • Provide expert services to the rest of the members in a consortial environment in areas such as advanced reporting and analytics, integrations and customizations;
    • Managing users and staff accounts; and
    • Provide customized training to its staff and/or consortia members.
    While Alma’s architecture and support model allows for the above roles system administration is flexible and can be done by local system librarians, Ex Libris, or in cooperation with Ex Libris.

    Alma should be easy for staff to learn and use

    Alma unifies the management of print, electronic and digital resources, supporting automatic, exception-based workflows for the complete lifecycle management of all of the resources managed in the library. Rather than integrating a range of existing, disparate services, Alma was designed to break down the traditional silos among formats and functions to create efficiencies that reduce the library’s cost of ownership and free library staff to perform the important activities that solidify the library’s role in the larger institution.
    Unlike legacy function-oriented library systems, Alma is task-oriented and focuses on streamlining workflows for library staff.Common tasks are fully automated, from metadata management to ordering and invoicing and more. As a result, staff deal only with the exceptions, which are surfaced as tasks, based upon staff role or roles within the library.
    Total views:
    7
    • Was this article helpful?
    //doorbell.io feedback widged