139 results found

1. Adjust the Analytics report generation time to include events occurring after 8 PM.

   Currently, the Analytics report is generated around 8 PM Taiwan time, which is earlier than the library's closing time. As a result, events that occur after 8 PM are not included in the statistics for the following day. This prevents the library from obtaining complete statistics for the previous day. If the report generation time could be delayed by at least 2 hours, it would be very helpful for Taiwan users.

   141 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Analytics  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Add and improve audit logging and system event tracking for changes to Alma configuration

   Many institutions have needs and requirements to be able to track when Alma configurations change, and who changed them.

   This is especially true because many Alma "administrator" roles combine complex librarian tasks with systems configuration abilities. For example, Catalog Administrator or General Systems Administrator is required to create new metadata import profiles - a task that catalogers need to do regularly. But, both roles also grant additional abilities to configure Alma behavior for resource management,
   integrations and the like.

   Use cases include:

   • Monitoring changes as part of standard internal audit review. For example, an institution may identify that even though electronic resources staff need Fulfillment Administrator in order to manage general electronic services, none of those electronic resources staff should be changing other areas of fulfillment configuration. Because Alma's roles do not separate those duties, the secondary requirement would then become to monitor changes in the fulfillment configuration areas outside Discovery Interface Display Logic to know which staff members are changing them and when. We would want a regular report that logged information like the name of the logged in user, the name of the table, the date/time the change occurred, what row(s) changed, and what the prior and new values were in those rows.

   • Troubleshooting unexpected Alma behavior. For example, suppose that custom linking for a set of CDI databases begins to behave unexpectedly. Configuration for those database links is handled in Configuration > Discovery. A staff member hears about the database issue, goes in and attempts to fix it,
     but can't. The issue then gets reported to a systems staff member. At that point, the systems staff member can only see the last updated by and timestamp. They need to be able to see who edited that table, and when, to help figure out what
     might have happened.

   Analytics currently has a subject area called "System Events" that does a poor job of capturing this information. For example, there is a system event type 6141 - Mapping table updated. However, the information captured there is internal tracking information and not actually relevant to mapping table updates, according to Ex Libris support.

   Improving how this data is kept and tracked would go a long way towards reducing risk of Alma not functioning as expected, and making it easier for institutions to manage audit requirements and troubleshooting needs for Alma users.

   Many institutions have needs and requirements to be able to track when Alma configurations change, and who changed them.

   This is especially true because many Alma "administrator" roles combine complex librarian tasks with systems configuration abilities. For example, Catalog Administrator or General Systems Administrator is required to create new metadata import profiles - a task that catalogers need to do regularly. But, both roles also grant additional abilities to configure Alma behavior for resource management,
   integrations and the like.

   Use cases include:

   • Monitoring changes as part of standard internal audit review. For example, an institution may identify that even though… more

   108 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   6 comments  ·  Analytics  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Need a Physical items folder in the Course Reserves Subject area

   Items details are missing from the Course reserves subject area in Alma Analytics. So can't get Barcode and other item details for course reserves.

   84 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   6 comments  ·  Analytics  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Add Collection related subject area/dimensions/parameters in Analytics

   Please elaborate Collection in Analytics. We suggest three ideas for that;

   Idea 1)
   Collection can be a separate dimension, with the existing/new parameters below;
   - Collection ID (existing)
   - Collection Name (existing)
   - Collection External System
   - Collection External ID
   - Collection MMS ID (of the collection's BIB itself)
   - ★★★ The PIDs of the collection's direct sub-collections (in different rows, not combined with semicolons; should be repeatable so that the created report can show the hierarchical structure of whole collections)
   - Collection level (the depth)
   - Collection Path (from the collection's top level collection to itself)
   - Collection Description
   etc.

   Idea 2)
   If the aforementioned parameters are not capable to show the hierarchy of the collections, nine dimensions for each level of collection can be created as followings;

   1. Nine Demensions for each Collection level;
      Dimension 1 : Collection level 1 (top)
      Dimension 2 : Collection level 2
      Dimension 3 : Collection level 3
      ....
      Dimension 9 : Collection level 9

   2. Then, each dimension can have the following parameters;
      Collection BIB MMS ID
      Collection PID
      Collection Name
      Collection Description
      Direct super(upper)-collection PID
      Direct sub-collection PID
      Create date
      Modification date
      Creator
      etc.

   Idea 3)
   Collection can be a new Subject Area.

   Please elaborate Collection in Analytics. We suggest three ideas for that;

   Idea 1)
   Collection can be a separate dimension, with the existing/new parameters below;
   - Collection ID (existing)
   - Collection Name (existing)
   - Collection External System
   - Collection External ID
   - Collection MMS ID (of the collection's BIB itself)
   - ★★★ The PIDs of the collection's direct sub-collections (in different rows, not combined with semicolons; should be repeatable so that the created report can show the hierarchical structure of whole collections)
   - Collection level (the depth)
   - Collection Path (from the collection's top level collection to itself)
   - Collection Description… more

   77 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  Analytics  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Get auto-renewals dates back into Analytics

   Since the recently released August version, Analytics does not longer show the auto-renewal date due to a mentioned performance improvement on the nightly job. Please consider rolling back this change as it actually makes it impossible to get how many auto-renewals were made on a certain day in the past, since the only date we currently have is the Last Renewal Date which is updated every time the job runs. We virtually lost our auto-renewals log integrity.

   I know we still have this Last Renewal Date, the amount of auto-renewals and the Loan Date, and we could easily calculate the auto-renewals specific dates doing some basic maths but this approach is not reliable because a loan could be manually renewed and its due date could be manually changed.

   Consider rolling this back, because we ended up with no option but to disable auto-renewals in order to keep this renewals record for future queries, and these manual renewals will be processed individually on Analytics so it makes no sense to the desired improvement.

   Since the recently released August version, Analytics does not longer show the auto-renewal date due to a mentioned performance improvement on the nightly job. Please consider rolling back this change as it actually makes it impossible to get how many auto-renewals were made on a certain day in the past, since the only date we currently have is the Last Renewal Date which is updated every time the job runs. We virtually lost our auto-renewals log integrity.

   I know we still have this Last Renewal Date, the amount of auto-renewals and the Loan Date, and we could easily calculate the… more

   69 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Analytics  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Establish system to ensure complete coverage of LC classifications

   Alma Analytics includes LC Classification code data, but frequently valid classification codes come up as "Unknown." Ex Libris currently has no reliable way of keeping up with changes in LC classification. They rely upon the "Library of Congress Classification Outline", which is not complete. They will add classifications upon customer request, though this process takes months or years and puts significant burden upon institutions. Ex Libris should develop a system to reliably update its LC classification coverage. This could take the form of e.g. establishing its own access to Classification Web, subscribing to LC updates, and/or setting up some alternative system with LC for updating their coverage. The outcome would be that Analytics users would be confident that very few valid classifications would come up as "Unknown" in Alma Analytics, and those that did would be added within a reasonable time frame without the need to file support tickets.

   Alma Analytics includes LC Classification code data, but frequently valid classification codes come up as "Unknown." Ex Libris currently has no reliable way of keeping up with changes in LC classification. They rely upon the "Library of Congress Classification Outline", which is not complete. They will add classifications upon customer request, though this process takes months or years and puts significant burden upon institutions. Ex Libris should develop a system to reliably update its LC classification coverage. This could take the form of e.g. establishing its own access to Classification Web, subscribing to LC updates, and/or setting up some alternative… more

   •  

   64 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Analytics  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Report on empty viewit screens and better link resolver usage reports

   I would like to be able to report on empty viewit screens.

   Currently the link resolver usage area is not so useful, missing the openurl itself, and limiting the data that is being reported to very few request metadata elements.

   Im missing, in addition to the openurl, the date/vol/issue details as well as request article title and book titles.

   My goal is to be able to use these reports in order to analyze problem points - currently I'm missing crucial data that will help me analyze problems.

   63 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   5 comments  ·  Analytics  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Expose 'Export to Worldcat' management tag to Analytics

   We would like to be able to access the 'Export to Worldcat' management tag in analytics, in the same way we can access the 'Suppress from Discovery' management tag. This would allow us to gather records for which the Export tag has been set incorrectly, and use a job to Republish them to OCLC.

   62 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   7 comments  ·  Analytics  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. Display prompts in analytics widgets

   We have created a widget to display IDs of citations, and would like to be able to display the associated prompts to allow users to select their own criteria.

   The current behaviour is by design:

   https://knowledge.exlibrisgroup.com/Alma/Knowledge_Articles/Analytics_widgets_with_a_prompt

   but it would be very helpful if this could be changed.

   61 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Analytics  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. Identify stats for individual self check machines in Analytics

    It doesn't appear to currently be possible to report stats in Analytics for individual self check machines unless you assign a separate Circulation Desk for each self check within a branch.

    We have multiple self check machines in each branch and we'd like to be able to report on the number of loans each self check processes so we can see which ones are in demand and which ones aren't. We'd like to see a way to attach multiple self checks to the same Circulation Desk and be able to report out the stats for each of those self checks in Analytics

    It doesn't appear to currently be possible to report stats in Analytics for individual self check machines unless you assign a separate Circulation Desk for each self check within a branch.

    We have multiple self check machines in each branch and we'd like to be able to report on the number of loans each self check processes so we can see which ones are in demand and which ones aren't. We'd like to see a way to attach multiple self checks to the same Circulation Desk and be able to report out the stats for each of those self checks… more

    54 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Analytics  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Notes Tabs not in Analytics

    We would like to be able to retrieve all the details in the Notes Tabs for Borrowing and Lending requests via Analytics. Currently, only the Request Note is retrievable.

    •  

    54 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Analytics  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Add 880 field to the Bibliographic Details dimension table in Analytics

    In MARC bibliographic records, the 880 field is used for non-Roman script equivalents of other fields in the bib record. CJK (Chinese, Japanese & Korean) libraries, for example, may use the 880 to record the non-Roman script equivalent of the Romanized characters in a 245. We would like the 880 field to be searchable in Analytics so we can create new book lists in the CJK scripts. New book lists are very popular with our users and we would like to be able to present these lists in the CJK scripts.

    54 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    5 comments  ·  Analytics  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. Analytics - Last Return Date

    It would be extremely useful to be able to report on the Last Return Date; this should be added to the Physical Items subject area alongside the Last Loan Date parameter

    52 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Analytics  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Add publication date and subject fields to 'Portfolio Details for Consortia Members' analytics table

    The bibliographic publication date and subject fields would be very useful additions to the 'Portfolio Details for Consortia Members' analytics table. Please include these fields.

    49 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Analytics  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. Map item level fields, Pattern Type and Linking Number in Analytics.

    Area of concern: Analytics Fields for Reporting on Serials 863/866 Generation.

    Please reference Ex Libris presentation ‘Automation Tasks for Summary Holdings’:

    https://knowledge.exlibrisgroup.com/@api/deki/files/63890/Serials_-_Automation_tasks_for_summary_holdings.pptx?revision=2

    In order for 863/866 Summary Holdings generation to work properly, each item record must contain certain information in the ‘Pattern Type’ and ‘Linking Number’ fields. Currently, these fields are not mapped in analytics, so there is no way to report on which records lack this info. Without this reporting capability, we are stuck individually checking many thousands of records to be sure they have the required information.

    What should be changed: As Serials Processors, we would like to have item level fields, ‘Pattern Type’ and ‘Linking Number’ mapped in Analytics so that they are easily reportable. This would benefit our workflow by allowing us to easily locate item records that do not have this information filled in. If we can find and correct those items efficiently, then we can optimize our records for Automated Summary Holdings generation.
     

    Area of concern: Analytics Fields for Reporting on Serials 863/866 Generation.

    Please reference Ex Libris presentation ‘Automation Tasks for Summary Holdings’:

    https://knowledge.exlibrisgroup.com/@api/deki/files/63890/Serials_-_Automation_tasks_for_summary_holdings.pptx?revision=2

    In order for 863/866 Summary Holdings generation to work properly, each item record must contain certain information in the ‘Pattern Type’ and ‘Linking Number’ fields. Currently, these fields are not mapped in analytics, so there is no way to report on which records lack this info. Without this reporting capability, we are stuck individually checking many thousands of records to be sure they have the required information.

    What should be changed: As Serials Processors, we would like to… more

    49 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Analytics  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Add the source field to Analytics

    It would be useful to be able to report on the Source field from Resource Sharing requests in the Borrowing Request subject area of Analytics. Then we could analyse the channels that users' Resource Sharing requests are coming in from.

    44 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    3 comments  ·  Analytics  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. Analytics: Transit end time NOT registered

    Hello,
    Please see our public ticket 00903860.
    If you make a query containing the field "Physical item historical events->Event end date->event end date and time" with the conditional "event type description=physical item went into transit" on this field is NOT registered the end of transit process, but the start of the following process (if any). Please correct this behaviour.

    42 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Analytics  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Add Alternative Title to Alma Analytics

    Adding the Alternative Title for an electronic collection would allow us fully use Alma Analytics and not need to maintain separate reports that are created outside of Alma. As a consortium, this would also allow more information sharing with our members and more efficient troubleshooting and maintenance.

    42 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Analytics  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. Add User Note Creation Date and Creator as query-able fields in Anayltics

    Please make it so that we can create analysis in analytics that display the creation date and creators of user notes. Both fields would be very useful filters for us.

    39 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Analytics  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. Subscription interval field in Analytics

    Adding the Subscription interval field in PO Line to the Funds Expenditure subject area in Analytics. This would allow reporting based on the frequency of a serial.

    39 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Analytics  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close