Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    NERS

     


    1. NERS 2022 - High Level Solutions
      1. NERS 7934 : Borrowing request with status Ready to be sent - should appear in task list
      2. NERS 7705 - Make it possible to customize the cancellation reasons
      3. NERS 7948 : Adding “Does not contain” and “Not equal” search option in Alma staff search
      4. NERS 7876 : Improve letter editing functionality
      5. NERS 7880: Dynamic collections that are automatically updated using logical sets
    2.  
    3. NERS 2021 - High Level Solutions
      1. NERS 7177: Add option to configure Process Types for Unavailable Physical Items, without creation of requests
      2. NERS 7343: Ability to Move/Re-Order Requests
      3. NERS 7456: Restricting the number of fields that show when manually creating new users via Register New User
      4. NERS 6664: Disable Item description confirmation message
      5. NERS 6969: Provide the ability to batch-edit electronic collections
      6. NERS 7419: View electronic collection portfolios from the POL view.
    4. NERS 2020 - High Level Solutions
      1. NERS 6795: Improve Repository Search functionality with free text options for MARC tags and subfields in Advanced Search
      2. NERS 6962: Resource sharing: updates to due dates of borrowing request loans to be reflected in resource sharing and fulfillment
      3. NERS 7049 Acquisitions: Hyperlink invoice number in POL to invoice
      4. NERS # 6676 Enable customer-defined order of locations in the Get It menu
      5. NERS # 6941 Enable customer-Improve Display Logic Rules
    5. Supported Functionality in NERS Enhancement Request List - 2020
      1. NERS # 7016 Provide patrons notification of reasons for failure to renew a loan
      2. NERS # 6555 Mark item as missing when cancelling a request
      3. NERS # 6941 Improve display logic rules
      4. NERS # 7028 Add functionality to loan status Claimed Return
      5. NERS #6780 - Requested titles show as available in Primo

    NERS 2022 - High Level Solutions

    As part of the NERS 2022 Enhancement procedure, a number of requests were voted to be included in Alma. Following are the NERS requirements and their high-level solution as agreed with the NERS representatives.

     

    NERS 7934 : Borrowing request with status Ready to be sent - should appear in task list

    Total Votes: 4791

    Request:

    We would like borrowing requests with status Ready to be sent to appear in task list under Borrowing request heading.

    Today, you need to open Borrowing requests and check facets to see if there are requests that are ready to be sent.

    High Level Solution:

    The Tasks Widget will have 'Ready to be Sent - Assigned to me ' and 'Ready to be Sent - Unassigned' widgets that link into the borrowing requests task list faceted for the relevant status

    NERS 7705 - Make it possible to customize the cancellation reasons

    Total Votes: 4987

    Request:

    When we choose to cancel a patron's hold or resource sharing borrowing request we have to select a cancellation reason from a drop-down list. The reason is then included in the letter to the patron. The available texts are currently not customizable by the library, which is a big problem. The texts should be customizable through a code table, just as the PO Line Cancellation Reasons. The available cancellation reasons, and especially the translations, are irrelevant and incomprehensible to our users.

    High Level Solution:

    Some of the cancellation codes are hardcoded to be used by Alma processes.  They are therefore currently customizable only by EXL staff. The solution must make sure library customization does not damage these Alma processes. 

    A proposed solution would therefore be - 

    1. EXL will add additional 10 'reason x' - reasons to the current list, for library use. The codes will be disabled by default, so libraries will be able to activate new codes (and texts) that are needed.
    2. EXL will enable the Alma institutions to customize the text of all codes
    3. EXL will enable customers to disable some of the existing reasons

    Disabling system used codes will not prevent the existing Alma processes that may use these codes from using them.

     

    NERS 7948 : Adding “Does not contain” and “Not equal” search option in Alma staff search

    Total Votes: 4900

    Request:

    Add “Not contains” or “Not equals” to Alma titles and inventory search indexes where “contains” or “equals” currently exist. (Original request: Adding "Does not contain" and "not" search option in Alma)

    High Level Solution:

    • "Not contains" search operators will be added to indexes where the index supported a "contains" search.
    •  "Not equals" search operators will be added to indexes where the index supported an "Equals" search.

    Note that when searching with a lower-level index* using "not contains" or "not equals", the search will retrieve results if at least one entity matches the query.

    For example, when searching for physical titles where holdings' location "not equals" stacks - if a title has two holdings, one fulfilling the condition (location=reference) and another not meeting it (location=stacks) - this title will be found by the search, since it has one holdings that matches the search criteria.

    * lower level index is an index that belongs to an entity contained in the searched entity, e.g. searching for physical holdings by item data, searching for electronic titles by portfolio data, etc.

     

    NERS 7876 : Improve letter editing functionality

    Total Votes: 5075

    Request:

    Editing of letters in Alma is a complex and difficult process, requiring substantial prior knowledge in order to do this effectively. Improvements have been made during recent years (e.g. the ability to view impact of changes) but the editing functionality is still in need of improvement, including the following points. We consider the priority order of these to be:


    1. The built-in error checker is not helpful because it doesn't provide enough information about a supposed error to assist with identifying it, but it does prevent the template being saved, even when the user is confident they have not introduced any errors with their recent changes.

    2. Use of XSL functions requires prior knowledge of those expressions. It would be much better if the letter template included an XSL glossary function from which a general system administrator could choose the appropriate XSL expression.

    3. It would be useful to have a 'Save draft' function to make it possible to save templates being worked on that are not yet finished, enabling users to stop their work as needed and pick it up again later without having to start afresh.

    4. Introducing an integral accessibility checker would enable us to be certain that we are meeting Web Content Accessibility Guidelines at source, rather than having to run checks on the emails themselves after sending.

     

    High Level Solution:

    1. The XML, XSL and the output HTML are all displayed on the same page while Changing the XSL will be immediately verified by presenting a preview allowing:

    a. Verify that the change is valid
    b. Validate the effect of the change on the output HTML
    c. Enable chanigng the language of the letter
    d. Enable sending the letter to an email address

    2. Improve XSL and XML editor appearance and readability (highlighted colors, indented text etc.)

    3. Template Draft version allowing to opt in and out and continue work on the draft in multiple sessions.

    3. Accessibility check button to verify HTML is accessible. 

    clipboard_e756c813d83337e0f77023f13778c478f.png

    NERS 7880: Dynamic collections that are automatically updated using logical sets

    Total Votes: 4748

    Request:
    A collection (unrelated to an electronic collection) is a set of bibliographic records used to organize and showcase a group of related library resources (i.e., 1920's jazz recordings). Customers can create collections using itemized sets (a static group of selected records) or logical sets (the results of a saved query created dynamically each time the query is run). However, once you create a collection using a logical set, it becomes static, effectively negating its purported advantage and making it behave no different than an itemized set. In order to create collections that don't require ongoing curation and manual updates, we would like to be able to use logical sets in a way that would allow collections to update automatically every time new works are added to the repository that match the set's predefined criteria. 

    High Level Solution:

    Each collection level could be categorized as either logical or itemized. Once defined as logical, the collection resource editor will include an attribute of a logical set of titles, which would be the only source populating the collection. Titles will not be able to be associated with that collection in any other way. An itemized collection, on the other hand, will continue working as of today.
    A periodic system job, eg nightly, will run all logical collection queries and add / remove titles which were added / removed from each corresponding logical set.
    Naturally, this will impact the collection discovery in Primo.

     

    NERS 2021 - High Level Solutions

    As part of the NERS 2021 Enhancement procedure, a number of requests were voted to be included in Alma. Following are the NERS requirements and their high-level solution as agreed with the NERS representatives.

    NERS 7177: Add option to configure Process Types for Unavailable Physical Items, without creation of requests


    Total Votes: 3957

    Request:
    Alma Process Types and the associated Base status of 'Item not in place' or 'Item in place' are hardcoded, as are the automated workflows within Alma and the flow-through to Primo for the availability status to be set to 'Not Available' or 'Available'. This is extremely limiting, as there are scenarios when a Library might want their physical resources to still be discoverable in Primo ie not suppressed, but also be marked as Unavailable. Being able to control availability by configured Process Types will allow us to communicate to users that we hold resources already, so that they don't waste time submitting purchase requests or thinking that we have a poor collection, while also avoiding user confusion with resources set to 'Available', when they actually aren't. Use cases for the need for this option are closures due to mould outbreaks and closures for physical distancing requirements related to COVID-19. Outcome: A configuration option is added to Alma whereby a site can add, edit, and subsequently delete new Process Types, as a static status added to an item, with no associated automated workflows triggered or requests created within Alma. A discovery label can be added to each Process Type by code table, for the Get It display. The configured Process Types are available in the Change Physical Items job, allowing for sets of items to have this type added and also then removed easily in bulk by job. The assignment of the Process Type to a physical item in Alma would immediately flow-through to Primo to mark these resources to be 'Unavailable' by the availability status, and display the associated label in the Get It by Real Time Availability. These Process Types would also be ETL'd to Analytics, along with the existing hardcoded Process Types, in the Physical Items subject area, for tracking and ease of management. Note: The current configuration option of Work Orders are not suitable to fulfill this submission, as they create a request for each resource, which then cannot be removed in Alma by bulk job, and incorrectly inflate Analytics data for requests. In the use cases provided, we do not need Alma's help in managing our resources beyond making clear to users in Primo that the resources are not available currently. See Idea Exchange submission at 98 votes as at 5.1.2021: https://ideas.exlibrisgroup.com/foru...s-for-physical 

    High Level Solution:

    •   Streamlined process for the institution to add, edit, and delete Work Order Types for Physical Items, individually or in bulk

    o    Work order types will no longer require any automated workflows, scanning in items or handling requests, and can be handled:

    • In bulk: It would be possible to add / remove the work order process type using a job
    • In the item editor
    • Workflow flexibility: Libraries will be able to choose to also use the work order department workflows for some / all of their work order types

    o    The configuration of work order types will be streamlined and automated. The admin will see

    • Work order types – ability add, edit and delete
    • Department will be created automatically - admin can add or edit departments if needed
    •  In the Physical Item Editor

    o    See, add, change or remove work order types

    o    When a work order type is added the item is marked as "Not in place" ( ="Unavailable" for publishing / GetIt).

    • The Change Physical Item Information Job will allow adding / removing work order type from a set of items in bulk
    • The repository search will support searching for physical items in a specific work order types
    • In Exclude Process Types from Publishing configuration, work order types will be supported in addition to the existing stand-alone process types (e.g. Loan, Lost, Transit), allowing libraries to exclude only items in a specific work order type from discovery
    • Based on "Exclude Process Types from Publishing", mark the items as suppresses in both the search result and item editor

    Already supported:

    Note:  Available Physical Items should be subject to regular loan processes 

     

    NERS 7343: Ability to Move/Re-Order Requests


    Total Votes: 3725

    Request:
    We would like the ability to move/re-order requests within an item's queue. 

    High Level Solution:
    It will be possible to sequence the entire requests queue.

    Currently, it is only possible to activate one instead of the system selected one. By adding an explicit 'sequence' field to the request, it will be possible to set an override for the ordering of the request that will take precedence over the priority field.

    NERS 7456: Restricting the number of fields that show when manually creating new users via Register New User

    Total Votes: 3143

    Request:
    Library staff regularly create a variety of new users in Alma. When we create these records via Register New User, there are a total of 34 text boxes to navigate. At most, only 16 are needed--not even half. This doesn't include the check box for 'Find user in other institution', the required checkboxes for the email, postal address, and phone # and the Yes/No radio button selection to designate 'Patron has institutional record', all of which we still need. Would it be possible to limit the number of available fields, by allowing the institution to customize the form in Alma to only relevant fields. For example, relevant fields for our institution would be: (under User Information) First Name, Last Name, Primary Identifier, User Group, Expiration Date, Purge Date; (under User Management Information) Password, Verify Password; (under Email Addresses) Email Address; (under Addresses) Address line 1, Address line 2, City, State/Province, Postal Code, Country; (under Phone Numbers) Phone number. 

     

    High Level Solution:

    It will be possible to use a mapping table to turn on/off fields in the user registration form (quick user edit form).

    One configuration form will be used for all forms and all user types (public/staff) with a super set of all of the fields of all forms.

    Ideally, it should enable removing fields altogether. Alternatively, it would grey out the undesired fields.

    NERS 6664: Disable Item description confirmation message

    Total Votes: 3125

    Request:
    Anytime you save an item that has a description, you get a pop-up message that reads "The description may need to be updated as well..." This occurs even if you have just updated the description manually. It is unhelpful, and is a bane for staff who work with serial items or multi-part works. It increases the time it takes to save an item and adds unnecessary keystrokes. The only time it does not occur is if you have clicked the Generate button in advance of Saving, but this button isn't generally used by our staff because there are too many bugs with the item description templates, and in other cases the Generate button is not appropriate, such as when you are cataloging a 9-disc volume set and the descriptions read "Disc 9," etc. This pop-up should be disabled, or there should be an institution-level configuration option to turn it off. Here's a video showing some of the latency. The pop-up adds several seconds to the transaction, which is a lot for staff trying to process hundreds of item records: https://www.screencast.com/t/UllQPrqi3DNy 

    High Level Solution:
     

    The messages when updating the description field will be adjusted as follows:

    •  Soft message will be displayed as an info feedback message
      Note: User today can hide Info message by default
    •   Few of the messages will remain mandatory as part of specific workflows
    •  Unneeded messages will be removed
    NERS 6969: Provide the ability to batch-edit electronic collections

    Total Votes: 3043

    Request:
    Allow library staff the option to batch update multiple electronic collections at once. Use cases provided by requester below: 1) We subscribe to several collections on the same platform. The platform vendor announces site maintenance which will make the platform inaccessible for several hours. We want to be able batch-apply to all the collections on that platform the same Authentication Note stating that the platform is unavailable. Then, when the maintenance is over, we want to be able batch-remove the same note. 2) We subscribe to several collections on the same platform. The platform vendor announces that the URL syntax is changing from http to https. We want to run a job to batch change the Electronic Collection Level URLs. This would be something like "delete or replace portfolio's prefix" in the "Change Electronic Portfolio Information" job. 3) We subscribe to several collections on the same platform. The platform vendor announces that these collections' names have changed; "Database A" is now "Platform Name: Database A." We would like to be able to update these names in a batch so the new names display to users. Perhaps if there were a "collection editor" spreadsheet with columns for collection ID and all the other collection fields, we could enter the new names in the Public Name (override) column, upload the spreadsheet, the spreadsheet would match on Collection ID, and all our collections would have their new values in Public Name (override) applied. 4) We want to make sure that the collections we need to proxy all have the same proxy sever settings. For these collections, we want to run a job to batch enable proxying (at the collection and the service level) and batch set the proxy server (at the collection and service level) to our default proxy server. 

    High Level Solution:

    A new job by the name of 'Update electronic collections' will be introduced, job will support:

    • Setting the same value to a set of electronic collections:
      • Update of all relevant attributes (to be defined as part of the FSD)
    • Clear electronic collection attributes values

    Job will report relevant changes

    NERS 7419: View electronic collection portfolios from the POL view.

    Total Votes: 2862

    Request:
    We are able to search for an electronic collection and find a link to the order, however when we are viewing the order, we cannot click into the electronic collection to see the portfolios. We have to copy and paste the title, leave the order, and search electronic collections to view the portfolios. 

    High Level Solution:

    In order to improve the navigation between an order of an electronic collection and its portfolios a new "view portfolios" link will be made available within the collection's summary section to reduce the number of clicks:"

    NERS 2020 - High Level Solutions

    As part of the NERS 2020 Enhancement procedure, a number of requests were voted to be included in Alma. Following are the NERS requirements and their high-level solution as agreed with the NERS representatives.

     

    NERS 6795: Improve Repository Search functionality with free text options for MARC tags and subfields in Advanced Search

    PowerPoint Presentation: Enhanced Ability to Filter a Set Using an Indication Rule (NERS 6795).pptx

     

     

    Total Votes: 4506

    Requirement: The Alma search function focuses on out-of-the-box mapping of grouped fields. It is a powerful search environment, but it does not allow for the autonomy of any library staff to quickly and easily run a customized search by specific MARC tags and subfields on demand as the need arises. For example, the Title grouping contains more than 3 dozen MARC tags and over a hundred subfields. The current in-system solution is restricted to staff with a cataloger role and is not quick or easy with several steps including a steep learning curve for writing complex indication rules. It also results in only static itemized sets.

    This submission requests the addition of free text fields in Alma's Advanced Search, where any MARC tags and subfields for both bibliographic and holdings can be typed in, such as an All Titles set just on data in 245 a, 130 a and 730 a, or just in 260 b and 264 b, or just data in 776 z, or specific entries like LDR 06 equal to a and LDR 07 equal to m and 008 equal to 21 of d, or any combination together. This functionality should be incorporated into existing Alma Repository Advanced Search options for all search types, including, but not limited to, All
    Titles, Physical Titles, and Electronic Titles. It should have comprehensive conditions including “contains”, "not contains", “equals”, “not equals”, "is empty", "is not empty", and "starts with", as well as Boolean operator selection (AND & OR) between multiples lines of query, and the ability to select specific grouping of multiple lines with visual indication of this. The resulting records should be able to be saved as any Alma search set can currently, in a logical set, and also itemized immediately or later.

    See mockup image provided and also Alma Idea Exchange entry with 264 votes as at 27.1.2020 and Planned status from 1.9.2017: Ability to search via free text MARC tag and subfields

    High Level Solution:

    1. User will perform a simple or advanced search
    2. User will be able to choose a ‘Filter’ action that will open a panel. The user can choose a predefined Filter or an option to create a new Filter. Functionality available as of Alma July 2021 release (Enhanced Ability to Filter a Set Using an Indication Rule)

    clipboard_e5298d30be6add5421e905c3c0da62ede.png

    1. Filters are based on Indication rules which are conditions based on MARC fields and subfields. The creation of a new Filter/Indication Rule will be simplified, and form based. The indication rule will be created in the background without the need for knowledge of any drool language

    clipboard_ed05f6ba92cccf58db773a156785aecf8.png

    1. When the user chooses ‘Run a filter’ an itemized set will be created “behind the scenes” applying the filter indication rules on the search results, The filtered results will be accessible via the Recent Entity panel.

     clipboard_ec93d62ca15f30a39595cd6e225891ea1.png

    1. The indication rule is assigned as a filter to the saved set. The user will be able to update the assignment from the Set edit screen and will also be able to see all filter results created as itemized sets. Functionality available as of Alma July 2021 release (Enhanced Ability to Filter a Set Using an Indication Rule)
      clipboard_ecebffa9fbaf8e0e0dcbad5811f086146.png

    The deployment is divided into two phases:

    NERS 6962: Resource sharing: updates to due dates of borrowing request loans to be reflected in resource sharing and fulfillment

    PowerPoint Presentation:  Resource sharing - updates to due dates of borrowing request loans to be reflected in resource sharing and fulfillment (NERS 6962).pptx

     

     

    Functionality available as of Alma March release

    Total Votes: 3433

    Requirement: If updating the due date of a borrowing request on loan, it should be reflected in both the patron account and the borrowing request, irrespective of where it was updated. Using the renew option in the borrowing request will update the due date in both borrowing and the patron side, but it should also be possible to update the due date in the patron side and for this to be reflected in the borrowing request, rather than having to do this twice

    High Level Solution: Patrons will be able to renew a Resource Sharing loan in advance of getting a lender’s approval. The loan due date will be updated as per the library’s loan terms of use before getting the lender’s approval. The loan can later be updated if the lender eventually responds with a different renew due date
     

    NERS 7049 Acquisitions: Hyperlink invoice number in POL to invoice

    PowerPoint Presentation: Acquisitions - Hyperlink invoice number in POL to invoice (NERS 7049).pptx

     

     

    Functionality available as of Alma February release

    Total Votes: 2890

    Requirement: There's frequently a need to access invoice information while working on PO Lines. Staff need to be able to view payment date, check number and other PO Lines associated with the invoice. Under the Invoice Lines tab the invoice number is listed to the left. On the right there is a View button which only accesses brief invoice information associated with that PO Line and no others.

    High Level Solution: The Invoice number for each invoice line will be hyperlinked from the PO Line “Invoice Lines” tab and will navigate the user to the relevant invoice screen in “view mode”

    clipboard_e3f77609c282e7ca5bcd7f5b5718a5c0d.png

     

    NERS # 6676 Enable customer-defined order of locations in the Get It menu

    PowerPoint Presentation: Enable customer-defined order of locations in the Get It menu (NERS 6676).pptx

     

     

    Functionality available as of Alma December Release

    Total Votes: 2583

    Requirement: Currently, the locations in the Alma resolver (Get It menu) are not sorted in a consistent, meaningful manner. There is a "use IP best locations ordering" option, but this option is insufficient for many institutions. For instance, in many cases, users are off site or not in a library building, and many institutions do not reserve IP addresses for specific buildings. There is also an alphabetical option but often the size or significance of locations doesn’t fit well into an alphabetical listing (for example a small branch starting with A or B might sort ahead of a large Central Library). Ideally, we would like the ability to explicitly define the preferred order in which locations are sorted. For multi-campus institutions, customers should be able to define the location order for each campus including accommodation for different sort orders between Alma available for groups/Primo views.

    High Level Solution:The institution will be able to define list of libraries, in a prioritized order, and list of locations within a library. There may be groups of equal locations/libraries that are prioritized higher than another list of locations/libraries. The prioritization within the group will be random.
    • When publishing availability, if the published record has multiple availability location lines, they will be published in the order that has been defined by the institution.
    • When displaying list of locations in the GetIt tab, if the record has multiple holdings they will be listed in the order that has been defined by the institution.
    Example: For "Main" Campus Primo view, Central Library resources will be sorted to be on the top of the list. For "Wellington" campus, Wellington Medical Library resources will be sorted to be on the top of the list.

    Where the institutional priorities have not been defined or are not relevant alphabetical sorting should be used.

    PrimoVE only – Institutions will be able to define the prioritized order for each "Primo view", the system will take into account the "Primo view" in which the user is logged into and will present the order of the locations accordingly.
    NERS # 6941 Enable customer-Improve Display Logic Rules

    Functionality available as of Alma November Release

    Total Votes: 2659
    Requirement:
    1. Add the ability to display a single collection when multiple collection options are available from the same vendor via a single rule in Alma. Currently this requires making multiple rules in Alma. In SFX this was possible using the asterisk '*' suffix (e.g., Do not show EBSCOHOST* getFullTxt If available EBSCOHOST* getFullTxt Condition: same_threshold).\
    2. Ability to give preference to collections that have a linked PO Line (to favor subscription access) or just being able to mark preferred collections.
    3. Ability to prioritize collections by designating collections that should appear at the top of the list and collections that should be placed last on the list (this also was possible in SFX).
    High Level Solution:
    Requirement #1 and Requirement #3 are supported as described here
    The solution will include the ability to give preference to collections/portfolios that have a linked PO Line (to favor subscription access)
     
    1. New option by the name of 'Prefer Ordered Resources' will be added to the Online Service configuration page
    2. Once enabled
      1. Services for for portfolios that have a POLine either at the level of the collection or at the level of the portfolio itself will be given preference in the sort order.
      2. This preference will override both the default alphabetic sort order as well as the list of services listed in the Top services section. 

     

    Supported Functionality in NERS Enhancement Request List - 2020

     

    As part of the NERS 2020 Enhancement procedure we identified a number of NERS requests that are already supported in Alma. Following are the request details, and the supported functionality for each of these requests.

    NERS # 7016 Provide patrons notification of reasons for failure to renew a loan

     We would like it to be possible to notify users when they have an item on loan that cannot be renewed, and to explain the reason to them so as to avoid confusion to patrons. Reasons may include: - because it is requested, - the patron has reached their expiry period - or the item has reached its maximum renewal period. Currently when an item is about to go overdue a notification is sent to warn a user that an item must be renewed or returned even if there is a request on the item. However, when a renewal is attempted, whether by the patron, automatically, or by staff, it fails, e.g. because of the request, with no notification of the failure which is confusing to the end user.

    Ex Libris:

    In December 2019 an enhancement relating to courtesy notices was introduced.
    Courtesy notices now include the last renew status and date in the XML (so that customers can add it to the XSL). If the renew status is added to the XSL, then the output of the notice will include information as to why the last automatic renew failed.

    You can configure the courtesy notice XSL to include the renew status in the notice.

    Alma > Configuration > General > Letters > Letters Configuration:

    clipboard_e22096daff2a1040409602c571bf80d2a.png

    Edit the Courtesy Notice Line:

    clipboard_e7e5f559a63cfa47d875fb4315b6790cc.png

     

    Note the New (from the December 2019 release) Renew Status line:

    clipboard_e03589e62ae6c23fad1f45d675191c6e3.png

    At the top of the table, click on the Template tab:

    Add the renew status lines as in the example below:

    clipboard_e72909d075287881d56260b974808c621.png

    The Courtesy notice will now have an additional column “Renew Status”. If there is more than one reason for the ‘non-renewal’ the reasons will be listed separated by a semi-colon (;).

    clipboard_eb4fcd755546e40e6dbdfc7a9f65847e2.png

     

    NERS # 6555 Mark item as missing when cancelling a request

     When we cancel a request and choose "item is missing" as the reason, we would like the option to update the item as missing as part of that process, rather than having to go back to the item record and mark it missing as a separate step"

    Ex Libris:

    In addition to the 'Cancel' option, the ‘Pick From Shelf’ (Fulfillment > Resource Requests > Pick from Shelf) screen offers the option to 'Mark as missing':
    clipboard_e43a2a55afafcde537ac80d35851a39bc.png

    Clicking on this option will result in the following:

    • The request will be canceled, and will no longer appear in the Pick From Shelf list
    • The item will be marked as missing (note the following message, before confirming the ‘Mark as missing’ status):

    clipboard_e5d5f69f0725e79a755ff8e759fe85348.png

    clipboard_eb225d593d885f64ca69f55ea50d45d60.png

    clipboard_e77b8a0273857e48b987af381cec016ae.png

    • A ‘Request Cancel’ letter will be sent to the patron with the information that the request has been cancelled as the ‘Resource material cannot be located’.

    clipboard_e3ec8ef7410aa80d0e169b377980c91e4.png

      More information can be found on the Knowledge Center here.

    NERS # 6941 Improve display logic rules

    This request included the following:

    1. Add the ability to display a single collection when multiple collection options are available from the same vendor via a single rule in Alma. Currently this requires making multiple rules in Alma. In SFX this was possible using the asterisk '*' suffix (e.g., Do not show EBSCOHOST* getFullTxt If available EBSCOHOST* getFullTxt Condition: same_threshold).
    2. Ability to prioritize collections by designating collections that should appear at the top of the list and collections that should be placed last on the list (this also was possible in SFX).
    3. Ability to give preference to collections that have a linked PO Line (to favor subscription access) or just being able to mark preferred collections. By this we mean sort order – put collections/portfolios that have a PO Line at the top of the sort.
    Ex Libris:
    • With regard to #1:

    Add the ability to display a single collection when multiple collection options are available from the same vendor via a single rule in Alma.

    Alma has the ability to display a single collection when multiple collection of the same vendor exists using a single rule, see for example:

      clipboard_e00f84239aaa570e56b051af082412e1c.png 
    For all the options supported by display logic rules please see here on the CKC.

    • With regard to #2:

    Alma supports the ability to prioritize collections by designating collections that should appear at the top of the list and collections that should be placed last on the list using the 'Online Sort Ordering'.

     clipboard_e6ca823d4769588561f452b3175fa86e8.png

    For complete information please see Online sort Order.

    • With regard to #3:

    The ability to mark preferred collections exists.

    The request now is to be able to give preference to collections that have a linked PO Line (to favor subscription access).


    NERS # 7028 Add functionality to loan status Claimed Return

    Amended text after correspondence with Ex Libris:


    Currently it is not possible for an item to have a claimed return status and simultaneously be in a work order status. Like many institutions and per recommendation from the Ex Libris workflow analyst, we use work orders to track item searches (traces). These searches have multiple steps and can be tracked using their statuses. However, if you put something into a work order that you had marked as claimed return, it loses its claimed return status. This prevents the behaviors of claimed returns from applying to the item automatically.

    We would like a special work order type “Claimed Return – Work Order” that allows the claimed return status to be retained while the item goes through the steps of the work order. This means retaining the behaviors associated with claimed return: that it stays on the patron’s account; that it has a process status and loan status of claimed return, in addition to the work order status; and that fines or lost fees don’t accrue while it is in claimed return status. Ideally, there’d be a step at the end of the special work order that could be either “found” or not, which would either check the item back in and release any fines, or remove the claimed return status from the loan on the patron’s record such that it would continue to accrue fines.

    Ex Libris:

    Our response relates to the original and the amended text of the NERS request.

    In Alma there is a customer parameter Configuration > Fulfilment > General > Other Settings 'overdue_at_claim_return_loan':

    clipboard_eaf7c50885bea62f6590bf44129271088.png

    Set to true if you want fines to stop accruing for items that were claimed to be returned. Read more about this here

    During the process of searching for the item, the existing fine can be set as 'dispute' so that the patron will not be blocked due to this fine.

    Every loan on a patron’s record has an optional 'notes' action. There can be multiple notes per loan. Using Alma's Analytics, you can generate a report which will present all items with a status 'Claim return' together with their notes. This can help monitor and track the number of times there was a search for the item. 

    During the process of searching for the item, the existing fine can be set as 'dispute' so that the patron will not be blocked due to this fine.

    Once the item is found/not found, the claimed return status can be removed and fines will apply (or not if the item is found).

    To summarize, Alma allows:
    - Pausing fines from being accumulated during the 'searching phase'
    - Adding a note on the loan which reflects the status of the item’s 'claim return'
    - Creating an Analytics report to manage the search for items with a 'Claim return' status
    - Disputing fines so as to not block patron activity while there is a search for the item.
     

    NERS #6780 - Requested titles show as available in Primo

    "Items that have been requested for pickup display as "available" in the Primo brief record. This causes issues if another patron attempts to borrow the item before it's retrieved from the shelves. Need option to display item as 'unavailable' or 'requested' in Primo."

    Ex Libris:

    In Alma there is an option to configure requested items to show as “Requested” in Primo, with an unavailable status. This setting needs to be enabled by Ex Libris support. For more details see here.


    • Article last edited: 09-Nov-2020
    • Was this article helpful?