1015 results found

1. ability to track perpetual access to eJournals when you cancel them.

   submitted case #00086211 to create a new field in the Electronic Portfolio and Electronic Collection records for 'Perpetual Access Coverage Dates', and for this field to be retrievable in Alma Analytics.

   We use separate spreadsheets to track these cancelled titles. In Alma, we would update coverage end date, POL if applicable (for individually subscribed titles in our case), and also a public note indicating the discontinuation. Patrons contacted us and asked why they couldn’t access a title any more, so we figured a public note would be more helpful to patrons in this case. But the public note fields is not searchable. We’ll consider using the internal description field to track within Alma.

   We did not feel it appropriate to include this information in the licence record, as the perpetual access relates to multiple licence agreements depending on the history of the journal title.

   Ex Libris closed the case and reported that this enhancement request has been added to the Roadmap with no estimated timeline for the release.

   submitted case #00086211 to create a new field in the Electronic Portfolio and Electronic Collection records for 'Perpetual Access Coverage Dates', and for this field to be retrievable in Alma Analytics.

   We use separate spreadsheets to track these cancelled titles. In Alma, we would update coverage end date, POL if applicable (for individually subscribed titles in our case), and also a public note indicating the discontinuation. Patrons contacted us and asked why they couldn’t access a title any more, so we figured a public note would be more helpful to patrons in this case. But the public note fields is… more

   32 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  ·  Acquisitions - General  ·  Delete…  ·  Admin →
   Already Supported  ·  Dana Sharvit responded

   Please see perpetual access best practice at:
   https://knowledge.exlibrisgroup.com/@api/deki/files/41819/perpetual_access_best_practice.pdf

2. Configuring different sender e-mail addresses (SMPT-envelope-from) for one letter-type

   For now the SMTP-envelope-from definition for Alma Letters can be set only once per letter-type. This isn’t suitable. E.g., our libraries need more than one sender email address for different acquisition departments. Vendors should be able to reply directly to the departments E-Mail-address. Using one no-reply-address (as SMTP-envelope-from value) in combination with a “reply-to”-addresses written in the Mail Footer cannot be a permanent solution.

   Actual situation in Alma:
   When an E-Mail is send in the context of a job Alma takes the SMTP-envelope-from value from the „addressFrom”-definition in the concerning letter-configuration (general configuration -> letter emails).
   When an E-Mail is send manually by a staff member (e.g. conversation letter, also used for claims to vendors) Alma takes the SMTP-envelope-from value from the definition in the settings for “preferred E-Mail-Address” of the acting staff member.

   Suggestion:
   ALMA already allows the definition of up to 5 E-Mail-Addresses of different types for each department or library (primary, billing, shipping, claim response, patron communication). Unfortunately these types can be used only as output-values in the letter-content (=text), but not as actual SMTP-envelope-from addresses. This function could be extended as follows:
   When E-Mails are send from a job or manually by a staff member, the values “from” and “Reply-to” in the SMTP-envelope section should be taken from a specific E-Mail-Address in the contact-definitions of the department (e.g. preferred). If no E-Mail-Address is defined in the concerning department the E-Mail-Address of the library and (if none defined) at least the E-Mail-Address of the institution should be taken (or even the value from „General Configuration - Configuration menu - General Configuration - other settings - envelope-from”).
   This improvement would give the whole system more flexibility not only for Acquisition-departments.

   (This is in addition to Ners request ID 5184)

   For now the SMTP-envelope-from definition for Alma Letters can be set only once per letter-type. This isn’t suitable. E.g., our libraries need more than one sender email address for different acquisition departments. Vendors should be able to reply directly to the departments E-Mail-address. Using one no-reply-address (as SMTP-envelope-from value) in combination with a “reply-to”-addresses written in the Mail Footer cannot be a permanent solution.

   Actual situation in Alma:
   When an E-Mail is send in the context of a job Alma takes the SMTP-envelope-from value from the „addressFrom”-definition in the concerning letter-configuration (general configuration -> letter emails).
   When an E-Mail is… more

   264 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  ·  Other  ·  Delete…  ·  Admin →
   Completed  ·  Dana Moshkovits responded

   When sending patron notices from a library, the library's 'Circulation Communication' address will be used as the reply to address on the email. For more information see video at https://youtu.be/bFfopLgjEN4'

3. Change order of availability in "Get it" tab

   We would like the order of availability in the "Get it" tab to be different. Instead of "x copies, x available, x requests" we would prefer "x available, x requests, x copies". The users frequently misunderstand and think that "copies" are available on shelf.

   376 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  ·  Fulfillment - General  ·  Delete…  ·  Admin →
   Completed  ·  Dana Moshkovits responded

   As part of the June release it will be possible to: Resequence the existing labels, for example “x available, x requests, x copies”.
   Add a descriptive text before, after or between each one of the labels, for example “x available, resources, x requests, x copies”.
   Remove labels which are not needed, for example "x available, x copies”
   For more information please see https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2020/Alma_2020_Release_Notes

4. Improve OpenURL generation to remove blanks and duplicates

   Openurls generated could by Alma/Primo be shorted by:

   1. Not sending duplicate parameters.
   2. Not sending empty parameters.

   Background:

   We have noticed that OpenURLs produced by Alma/Primo (which are then sent on to our ILLiad server, which can require redirection to get the patron authenticated) can be VERY long. So long in fact, that they can produce errors for our ILLiad web server. The ILLiad server will end up reporting "Request header is too large", and the user is left with a HTTP Status 400 Bad request error.

   We believe the responsibility here is on the Alma/PRimo side as the urls generated could be shorted by:

   1. Not sending duplicate parameters.
   2. Not sending empty parameters.

   Note: For our (UW-Madison's) locally developed discovery interface, we generate our own OpenURL links for things like "Request a copy" from article searching and the catalog records, so we can ensure proper length limits.

   ExLibris generates OpenURL links in their UResolver (Find it) and Primo Search API

   Alma/Primo OpenURLs

   For example, following a "Find it at UW-Madison" link from Google Scholar and then doing "Request a copy" (sending the OpenURL on to our ILLiad server):

   Starting in Google Sholar, and ending up here:
   https://uwi-primoalma-prod.hosted.exlibrisgroup.com/primo-explore/openurl?sid=google&auinit=PM&aulast=Vitousek&atitle=Beyond%20global%20warming:%20ecology%20and%20global%20change&id=doi:10.2307%2F1941591&title=Ecology.&volume=75&issue=7&date=1994&spage=1861&issn=0012-9658&vid=WISC&institution=WISC&url_ctx_val=&url_ctx_fmt=null&isSerivcesPage=true

   Provides an OpenURL link (request a copy) of:

   https://madison.hosts.atlas-sys.com/illiad/OpenURL?Action=10&Form=30&rft.genre=article&rft.title=Ecology.&rft.stitle=Ecology.&rft.atitle=Beyond+global+warming%3A+ecology+and+global+change&rft.jtitle=Ecology.&rft.au=&rft.date=1994&rft.month=&rft.volume=75&rft.issue=7&rft.number=&rft.spage=1861&rft.epage=&rft.edition=&rft.issn=0012-9658&rft.eissn=1939-9170&rft.aulast=Vitousek&rft.aufirst=&rft.auinit=PM&rft.pub=Brooklyn+Botanical+Garden&rft.pubdate=1920-&rft.pubyear=&rft.publisher=Brooklyn+Botanical+Garden&rft.place=Brooklyn%2C+NY+%3A&rft.doi=10.2307%2F1941591&rfe_dat=35698209&rfr_id=google

   Where the following parameters are included, yet blank:

   au, month, number, epage, edition, aufirst, pubyear

   Primo Search API

   In order to display electronic availability for articles we have to query the OpenURL resolver in alma to get data back. The string we use to query the resolver is provided to us by the Primo Search API

   Primo API Docs - Ex Libris Developer Network

   This one is by far the biggest offender, as that API returns the "GetIt1" URL we need to use. An example URL returned to us looks like:

   https://na02.alma.exlibrisgroup.com/view/uresolver/01UWI_MAD/openurl?svc_dat=CTO&ctx_enc=info:ofi/enc:UTF-8&ctx_id=10_1&ctx_tim=2020-02-07T10%3A04%3A19IST&ctx_ver=Z39.88-2004&url_ctx_fmt=info:ofifmt:kev:mtx:ctx&url_ver=Z39.88-2004&rfr_id=info:sidprimo.exlibrisgroup.com-proquest&req_id=&rft_val_fmt=info:ofifmt:kev:mtx:journal&rft.genre=article&rft.atitle=Telltale%20warming%20likely%20to%20hit%20poorer%20countries%20first&rft.jtitle=Nature&rft.btitle=&rft.aulast=Schiermeier&rft.auinit=&rft.auinit1=&rft.auinitm=&rft.ausuffix=&rft.au=Schiermeier,%20Quirin&rft.aucorp=&rft.date=2018-04-26&rft.volume=556&rft.issue=7702&rft.part=&rft.quarter=&rft.ssn=&rft.spage=415&rft.epage=416&rft.pages=415-416&rft.artnum=&rft.issn=00280836&rft.eissn=14764687&rft.isbn=&rft.sici=&rft.coden=&rft_id=info:doi/10.1038d41586-018-04854-2&rft.object_id=&rft.eisbn=&rft.edition=&rft.pub=Nature%20Publishing%20Group&rft.place=London&rft.series=&rft.stitle=&rft.bici=&rft_id=info:bibcode&rft_id=info:hdl&rft_id=info:lccn&rft_id=info:oclcnum&rft_id=info:pmid&rft_id=info:eric((addataeric}}&rft_dat=%3Cproquest%3E2056433252%3Cproquest%3E%3Curl%3Ehttp:search.proquest.com/docview/2056433252/%3C/url%3E,language=eng,view=MD&svc_dat=viewit&req.skin=MADskin&rft_pqid=2056433252&rft_galeid=572639507&rft_cupid=&rft_eruid=&rft_nurid=&rft_ingid=

   Previously we ran this URL through a parser to validate it and then remove empty parameters. There are three issues with this data - 1) sometimes keys are duplicated, which goes against best practices 2) Data is not properly url encoded 3) There are a lot of empty parameters.

   Removing those parameters for this example request would drop the length of the URL from 1328 to 1052 characters

   Note: We no longer parse this data as it was dropping the duplicated parameters causing lookup issues, so it's passed through to our OpenURL resolver as we receive it from the API (aside from prepending a parameter to return XML instead of HTML)

   Openurls generated could by Alma/Primo be shorted by:

   1. Not sending duplicate parameters.
   2. Not sending empty parameters.

   Background:

   We have noticed that OpenURLs produced by Alma/Primo (which are then sent on to our ILLiad server, which can require redirection to get the patron authenticated) can be VERY long. So long in fact, that they can produce errors for our ILLiad web server. The ILLiad server will end up reporting "Request header is too large", and the user is left with a HTTP Status 400 Bad request error.

   We believe the responsibility here is on the Alma/PRimo side as the urls… more

   16 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  ·  Resource Management - Electronic  ·  Delete…  ·  Admin →
   Closed  ·  AdminLiza Voloshin (Product Owner, Alma Resource Management, Ex Libris) responded

   Hello all,

   This idea has been closed as part of a cleanup process for ideas older than a year with fewer than 20 votes. This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the CERV process. We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Alma.

   Alma Product Team.

5. Enhancement request for New MDE > Editing Actions > Expand from Template

   Request for customizing the sorting and enable/disable the template options in the Choose Template dropdown list
   The current sorting is starting from public ones followed by private ones, in alphanumeric order respectively.
   We hope for being able to toggle enable/disable and customize the ordering of the template options

   For achieving the above feature, refer to New MDE > New > Templates display configuration
   A similar toggle button for each template, similar to the Display in Menu toggle button here, is desired.
   And allowing manually sorting the order of the templates would be appreciated as well.

   0 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  ·  Resource Management - Physical  ·  Delete…  ·  Admin →
   Closed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

   Hello All,

   This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 20 votes.

   This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.

   We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Alma.

   Alma Product Team

6. monitor requests on loan

   In the Alma Monitor Requests & In Processes module, add the ability to filter requests for items that are currently On Loan.

   6 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  ·  Fulfillment - Requests  ·  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

   Submit Rating

7. Alma RS: Borrowing - Receive Slip Letter cannot be reprinted after 'Receive action' completed

   Issue:
   For borrowing physical item requests, if staff forget to select 'Automatically print slip' when receiving an item or need to change a request's temporary item barcode, the 'Receive Slip Letter' cannot be reprinted.

   Currently there are no APIs that can create the printout on demand so a Cloud App cannot be created.

   Requested Outcome:
   Can an option be added to the Alma RS Borrowing Request Actions menu to allow staff to reprint the 'Receive Slip Letter' for received items?

   8 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  ·  Resource Sharing  ·  Delete…  ·  Admin →
   Already Supported  ·  AdminMoshe Shechter (Alma Senior Product Manager, Ex Libris) responded

   After receiving an item in the Receive Items interface, it is possible to reprint the slip using the Print Slip action, see https://www.screencast.com/t/B93NQoKt8

8. Incoherent date in the “Date” column when the transaction type is “Expenditure”

   According to the developer, the expenditure date comes from the invoice date and always comes from it (see documentation at https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/020Acquisitions/030Invoicing/020Creating_Invoices).

   As you can see there, the calculation of the exchange rate is also done according to this date: "By default, Alma calculates the value of the transaction based on the exchange rate on the date specified in Invoice Date."

   Now we know where the date comes from when the type of transaction is “Expenditure”. However, in other types of transactions (transfer, allocation, encumbrance, etc.) the date that appears corresponds to the moment in which the transaction occurs. For this reason, it seems impractical that in the type of transaction “Expenditure” the invoice date is used and not the date on which the transaction is triggered, that is, the “create on” date.

   We request to incorporate a new column in the table of visualization of transactions that is “create on”.

   We provide explanatory screenshot of how it could be implemented.

   According to the developer, the expenditure date comes from the invoice date and always comes from it (see documentation at https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/020Acquisitions/030Invoicing/020Creating_Invoices).

   As you can see there, the calculation of the exchange rate is also done according to this date: "By default, Alma calculates the value of the transaction based on the exchange rate on the date specified in Invoice Date."

   Now we know where the date comes from when the type of transaction is “Expenditure”. However, in other types of transactions (transfer, allocation, encumbrance, etc.) the date that appears corresponds to the moment in which the transaction occurs. For… more

   •  

   •  

   29 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  ·  Acquisition - Funds  ·  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

   Submit Rating

9. Allow users to enter an address for home delivery

   Users should be able to enter an alternate address when requesting home delivery as most students put in a parent address when they enroll and then never update the info again. If students do want to update their address, they need to go into the campus system and wait another day for it to be loaded to Alma. At our institution, faculty and staff never have personal addresses loaded into Alma. In addition, that address entered at time of request should be pushed to the personal delivery notification letter.

   10 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…)
   Completed  ·  1 comment  ·  Fulfillment - Requests  ·  Delete…  ·  Admin →

10. Allow for Almost Arbitrary Conditions in General Electronic Services

    Currently for a general electronic service we can only create conditions based on metadata already contained in the given BIB record. Please provide a way to let the link resolver check any condition which is computable within a reasonable short amount of time!

    Example Use Case:
    Our library network offers a web service taking any given ISBN, ISSN or Union Catalog ID and returning 'true' if there is a BIB record for the corresponding resource in the union catalog and at least one of the network's libraries has an item of this resource available for ILL. Otherwise the web service returns 'false'. If we were able to let the Alma link resolver check a given ISBN, ISSN or Union Catalog ID against that web service we could offer an ILL service if and only if there is a pretty good chance that there is an item available via ILL.

    Instead the only general electronic service we can offer currently is a context-insensitive "check whether ILL might be an option" link which resolves to our library network's SFX service menu(!) where an ILL service shows up if and only if there is a pretty good chance that there is an item available via ILL. (Yes, SFX is able to perform such "magic" thanks to so called "plugin thresholds". Their implementation in SFX as an arbitrary local script that evaluates the desired condition does not fit into a cloud environment, of course, but letting a web service evaluate the desired condition and return 'true' or 'false' does.)

    Please note that this enhancement request has also been submitted to the CERV portal: https://enhancements.exlibrisusers.org/ideas/AENH-I-36524

    Currently for a general electronic service we can only create conditions based on metadata already contained in the given BIB record. Please provide a way to let the link resolver check any condition which is computable within a reasonable short amount of time!

    Example Use Case:
    Our library network offers a web service taking any given ISBN, ISSN or Union Catalog ID and returning 'true' if there is a BIB record for the corresponding resource in the union catalog and at least one of the network's libraries has an item of this resource available for ILL. Otherwise the web service… more

    71 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  ·  Link Resolver  ·  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

    Submit Rating

11. Make it possible to add Vendor Interface fields and customize field value options for existing fields

    In Alma, Vendor Interfaces in Vendor records are the place designed to hold e-resources administrative information, such as contact information, administrative details, and usage statistics details. However, the fields available to libraries were developed several years ago, are not customizable, and do not reflect the complexity of modern e-resources management. Different types of institutions have different needs and want to record different types of information, so adding a few new fields for all libraries isn't an ideal solution.

    Instead, this request is for libraries to have the ability to add and manage Vendor Interface fields. Libraries should be able to create new fields to reflect their own local needs, and these new fields should all be viewable in analytics. For example, we'd like to store accessibility information and COUNTER version information for each vendor interface, but there is no fields dedicated to this type of information (other libraries might wish to store other types of information). Also, for both new and existing fields, libraries should be able to manage their own controlled field values lists. For example, for the field "Implemented Authorization Method," the select list of controlled values is currently not customizable does not include modern authentication methods such as Shibboleth, SSO, or OpenAthens. We would like to be able to add the field values we need for these and other fields.

    This will make it possible to e-resources librarians to flexibly respond to new developments in the field and track the information they need in Alma (instead of relying on external shadow systems and spreadsheets). This functionality is already in place in Alma for licenses (see https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/020Acquisitions/040Configuring_Acquisitions/170Managing_License_Terms). Like License terms, we should be able to add new terms, choose the term type (including free text, yes/no, or controlled vocabulary, and then we can create the controlled vocabulary) and choose the Vendor Interface record section in which the term will appear. I will attach a mockup of what the Add Vendor Interface Term form should look like (based on the Add License Term form).

    In Alma, Vendor Interfaces in Vendor records are the place designed to hold e-resources administrative information, such as contact information, administrative details, and usage statistics details. However, the fields available to libraries were developed several years ago, are not customizable, and do not reflect the complexity of modern e-resources management. Different types of institutions have different needs and want to record different types of information, so adding a few new fields for all libraries isn't an ideal solution.

    Instead, this request is for libraries to have the ability to add and manage Vendor Interface fields. Libraries should be able to… more

    •  

    204 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  ·  Acquisition - Vendors  ·  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

    Submit Rating
    AdminTamar Fuches (Alma product manager, Ex Libris) responded

    Hi Elizabeth, Katie, and everyone,

    Thanks so much for sharing this idea!

    From what I understand, it includes two main parts:

    1. Allowing institutions to edit the list of values in various fields, with a specific example being the “Implemented Authorization Method” field.
    2. Adding more fields and making them reportable in Analytics, along with a request for a flexible mechanism to support this.

    Regarding the second point — adding a flexible mechanism is quite a complex change and could impact the timeline.

    If you can point out around three specific fields that are most important to add first, it might be easier.

    Looking forward to hearing your thoughts!

    Thanks again,

    Tamar

12. User Requests Should Pop or Be more Visible for Cataloguers

    When cataloguers are processing new books or fixing bibliographic records or item records, there is no notification that a user has requested the item we are working on. We won't know to give the item to Fullfillment so that they can put the item aside for the user.

    I know there is a little number that indicates there is a request, but for new books ordered in there is already 1 request from Acquisitions. This does not pop-up and it is just a little number that you can barely see in the results screen. It should be much more obvious when a user has put an item on hold.

    When cataloguers are processing new books or fixing bibliographic records or item records, there is no notification that a user has requested the item we are working on. We won't know to give the item to Fullfillment so that they can put the item aside for the user.

    I know there is a little number that indicates there is a request, but for new books ordered in there is already 1 request from Acquisitions. This does not pop-up and it is just a little number that you can barely see in the results screen. It should be much… more

    2 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  ·  Fulfillment - Requests  ·  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

    Submit Rating

13. Provide a notice/warning on Scan In when a home delivery is blocked

    When an item requested for home delivery is scanned in and the patron is blocked, e.g. due to excessive fines, Alma silently places the item on the Hold Shelf. There is no notice to the staff user that the item was requested for home delivery and that a fulfillment process was just interrupted.

    We use home delivery exclusively for remote students that often will not be able to come in and pick up their items, so placing the item on the hold shelf will not help them.

    And when/if the block is lifted (e.g. the user pays the fines) the item will remain on the hold shelf with no indication in Alma that it can now be delivered as requested.

    We regard this as an exception that will require manual intervention from our staff to be able to fulfill the request, but since Alma doesn't alert the staff user it is far to easy to miss.

    When an item requested for home delivery is scanned in and the patron is blocked, e.g. due to excessive fines, Alma silently places the item on the Hold Shelf. There is no notice to the staff user that the item was requested for home delivery and that a fulfillment process was just interrupted.

    We use home delivery exclusively for remote students that often will not be able to come in and pick up their items, so placing the item on the hold shelf will not help them.

    And when/if the block is lifted (e.g. the user pays the… more

    14 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  ·  Fulfillment - General  ·  Delete…  ·  Admin →
    Closed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

    Hello All,

    This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 20 votes.

    This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.

    We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Alma.

    Alma Product Team

14. Linked Data Enrichment Moves $e Relator Subfields to Incorrect Positions When Saving Authorities with F3

    When saving a name authority record in Alma using the F3 function, the Linked Data Enrichment process is causing the $e relator subfield to move to an incorrect position within the field. Instead of maintaining the expected order (e.g., $a, $e, $1), the $e subfield is often placed at the end or in another unexpected location after $0/$1 subfields are added. This disrupts the intended structure of the authority field and creates extra manual work for cataloguers.

    Attempts to correct the placement by copying and pasting the $e subfield do not work as expected—Alma consistently pastes it at the end of the field, regardless of cursor position. This issue only occurs after Linked Data Enrichment and does not affect other fields or occur before enrichment.

    Ex Libris support has indicated that this is currently by design, as part of the Preferred Term Correction (PTC) process.

    Impact:
    • Authority records are not formatted as cataloguers expect, leading to confusion and extra manual editing.
    • The copy-paste function does not work reliably for $e subfields after enrichment.
    • The current behaviour reduces efficiency and increases the risk of errors in authority data.

    Request:
    Please review and enhance the Linked Data Enrichment and F3 saving process so that $e relator subfields retain their correct position (immediately after $a) when new $0/$1 subfields are added. Additionally, ensure that copy-pasting subfields works as expected in all scenarios. This change would improve cataloguing accuracy and workflow efficiency.

    When saving a name authority record in Alma using the F3 function, the Linked Data Enrichment process is causing the $e relator subfield to move to an incorrect position within the field. Instead of maintaining the expected order (e.g., $a, $e, $1), the $e subfield is often placed at the end or in another unexpected location after $0/$1 subfields are added. This disrupts the intended structure of the authority field and creates extra manual work for cataloguers.

    Attempts to correct the placement by copying and pasting the $e subfield do not work as expected—Alma consistently pastes it at the end… more

    47 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  ·  Metadata Management  ·  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

    Submit Rating

15. Increased efficiency thanks to new “Send externally” field in CZ update

    The additional “Send externally” field in the CZ update increases efficiency and communication within the library and with external partners and is structured in the same way as the “Report to Ex Libris” field. This allows messages to be sent directly from ALMA, eliminating the need to copy information. This reduces errors, saves time, and minimizes manual effort. Faster processing of requests and better coordination between departments and partners increase service quality and satisfaction and make the library forward-thinking.

    This option includes the following fields:

    1. Sender (automatically filled in by ExLibris based on the login)
    2. Field for entering the email address(es) to which the message should be sent
    3. Drop-down menu with various options, such as: No access – request title, etc.
    4. Free text field “Description”
    5. Additional information: automatically filled in as for “Send to Ex Libris”

    The additional “Send externally” field in the CZ update increases efficiency and communication within the library and with external partners and is structured in the same way as the “Report to Ex Libris” field. This allows messages to be sent directly from ALMA, eliminating the need to copy information. This reduces errors, saves time, and minimizes manual effort. Faster processing of requests and better coordination between departments and partners increase service quality and satisfaction and make the library forward-thinking.

    This option includes the following fields:

    1. Sender (automatically filled in by ExLibris based on the login)
    2. Field for entering the… more
    15 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  ·  Other  ·  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

    Submit Rating

16. Clearly show a patron's home campus when placing requests

    Occasionally we will need to place a 'Patron physical item request' on a title/item on behalf of a patron when all existing copies are unavailable. We'd like to clearly be able to see what a user's home campus is from the 'Create Request' screen after entering the Requesters name. Alternatively, if we were to click on the 'Select from a list' to choose the requester, we are taken to a 'Find and Manager Users' popup. It would be useful to be able to see the patron's campus within a column in this display.

    Currently, we must first go into a patron's record to check what their default campus is, so that the book can be sent to that campus for pickup when it is available.

    Occasionally we will need to place a 'Patron physical item request' on a title/item on behalf of a patron when all existing copies are unavailable. We'd like to clearly be able to see what a user's home campus is from the 'Create Request' screen after entering the Requesters name. Alternatively, if we were to click on the 'Select from a list' to choose the requester, we are taken to a 'Find and Manager Users' popup. It would be useful to be able to see the patron's campus within a column in this display.

    Currently, we must… more

    2 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  ·  Fulfillment - Requests  ·  Delete…  ·  Admin →
    Closed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

    Hello All,

    This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 20 votes.

    This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.

    We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Alma.

    Alma Product Team

17. Add Cancellation Reason code and Notes to the Interested In Letter XML

    This essentially replicates an earlier request that was closed in 2021 without resolution:

    https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/44262498-request-to-add-cancellation-reason-and-cancellatio

    We would like to have Cancellation Reason code and Cancellation Note available in the XML that is supplied to the Interested In letter template. The Cancellation Reason code is a distinct field In Analytics, so I would hope that this would be easy to add to the XML. The cancellation note might be trickier -- it is stored as a PO Line Note in Analytics. If the cancellation note is just one of several PO Line notes in Alma, we would be happy to have all the PO Line Notes go to the Interested In letter XML, though it would be better if the Cancellation Note was sent as a separate element in the XML.

    This essentially replicates an earlier request that was closed in 2021 without resolution:

    https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/44262498-request-to-add-cancellation-reason-and-cancellatio

    We would like to have Cancellation Reason code and Cancellation Note available in the XML that is supplied to the Interested In letter template. The Cancellation Reason code is a distinct field In Analytics, so I would hope that this would be easy to add to the XML. The cancellation note might be trickier -- it is stored as a PO Line Note in Analytics. If the cancellation note is just one of several PO Line notes in Alma, we would be happy to… more

    •  

    •  

    8 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  ·  Acquisition - PO & POLine  ·  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

    Submit Rating

18. Allow customers to select multiple retention reasons for Item records.

    Allow customers to select multiple retention reasons for Item records.

    As an institution that is very enthusiastic about using the new Retention Information data fields for item records in Alma, we would like to request an enhancement that enables a user to assign multiple values to the Retention Reason field. For example, a single item could easily have all of the following statuses applied:

    1. Institutional last copy

    2. Faculty publication

    3. Rare

    4. Committed to some Shared Print program

    5. Digitized material

    Each of these retention reasons may correspond to different library staff workflow. For example, these retention reasons could support the following staff workflows, respectively:

    1. Blocking withdrawal/weeding at the institutional (IZ) or consortial (NZ) level by collection development staff

    2. Generate a report that can be used to populate a display shelf highlighting local research at our campus

    3. Identification of materials that should be prioritized for preservation treatment

    4. Block withdrawal/weeding and select for inclusion in data integration/sharing with partners

    5. Identification of materials that are good candidates for off-site high density storage

    Absent the ability to assign multiple values in a dropdown, which will provide a kind of authority control for approved statuses, we would be dependent on cramming all of this information into the free text Retention Note field. Obviously, this would be more error prone as it would require 100% consistency to achieve the same level of data reporting as the dropdown menu options would have. Additionally, parsing a free text field to find specific substrings in an Alma Analytics report is a much more sophisticated and therefore difficult task to accomplish. This would therefore have the effect of limiting the number of staff who are capable of effectively querying for all retention reasons.

    Allow customers to select multiple retention reasons for Item records.

    As an institution that is very enthusiastic about using the new Retention Information data fields for item records in Alma, we would like to request an enhancement that enables a user to assign multiple values to the Retention Reason field. For example, a single item could easily have all of the following statuses applied:

    1. Institutional last copy

    2. Faculty publication

    3. Rare

    4. Committed to some Shared Print program

    5. Digitized material

    Each of these retention reasons may correspond to different library staff workflow. For example, these retention reasons could support the following staff… more

    70 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  ·  Resource Management - Physical  ·  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

    Submit Rating

19. Create a Separate Search Index for Specific OCLC Number

    Currently, the OCLC Number for a record is indexed in the search index "Other System Number." This is not ideal, since the Other System Number indexes other numbers related to vendor record, CONSER, related item, etc.
    We request that Ex Libris provide a separate search index for OCLC number based on the presence of the '(OCoLC)' prefix in the 035 $a and/or $z, or (without prefix) in the 019 $a if there is a number in the 035 with an (OCoLC) prefix. Currently these specific (OCoLC) numbers are mixed in with other numbers occurring in the 019, 035, 773, 774, 775 777, 786, 800, 810, 811, 830 $w tags and subfields. Disambiguating these specific (OCoLC) numbers from the "other system numbers" would allow us to use them as unique identifiers. We see the potential for: Improved search Improved matching upon record import Cleaner Excel exports from Alma (we currently have to clean this field every time we export) Creation of a new Analytics field for OCLC number in Alma Analytics Establishment of a model for non-OCLC systems to create other unique search indexes 

    Currently, the OCLC Number for a record is indexed in the search index "Other System Number." This is not ideal, since the Other System Number indexes other numbers related to vendor record, CONSER, related item, etc.
    We request that Ex Libris provide a separate search index for OCLC number based on the presence of the '(OCoLC)' prefix in the 035 $a and/or $z, or (without prefix) in the 019 $a if there is a number in the 035 with an (OCoLC) prefix. Currently these specific (OCoLC) numbers are mixed in with other numbers occurring in the 019, 035, 773, 774,… more

    30 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  ·  Metadata Management  ·  Delete…  ·  Admin →
    Closed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

    This idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.

20. Change the pick up location when an item is "On Hold Shelf"

    When an item is "On hold shelf" (in a library A), by clicking on "Edit", we can change (only in Alma fortunately) the pick up location (to the library B for example).

    It's a good option, useful when a user has made a mistake and would like to change the pick up location.
    In Alma, currently, when you use this option (so edit > change the pick up location", there is no notification to the library A (livrary A have to send the book to library B).
    So, in the patron folder, the pick-up location is B (as the user's request) but in reality the book is still in the library A.

    Library A can't know that user has requested an other pick-up location.

    In fact, this option is useless as offered.

    If a user resquest to change the pick-up location when the item is "On hold sheld", the item should appears in the "Expired Hold Shelf Item" > "Send to the library".

    Thanks

    When an item is "On hold shelf" (in a library A), by clicking on "Edit", we can change (only in Alma fortunately) the pick up location (to the library B for example).

    It's a good option, useful when a user has made a mistake and would like to change the pick up location.
    In Alma, currently, when you use this option (so edit > change the pick up location", there is no notification to the library A (livrary A have to send the book to library B).
    So, in the patron folder, the pick-up location is B (as the user's … more

    17 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  ·  Fulfillment - Requests  ·  Delete…  ·  Admin →
    Closed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

    Hello All,

    This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 20 votes.

    This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.

    We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Alma.

    Alma Product Team