3212 results found

1. PO line description should represent current bibliographical data

   Alma provides insufficient data in PO lines for the task of pulling a list of subscriptions a library has of a specific publisher's titles:

   1. The PO line description contains only bibliographical data from the bib record as it was at the time the PO line was created. Subsequent changes in the publisher data are not updated in the related PO lines.

   2. Even in newly created PO lines, Alma introduces the content of MARC field 264 _1 instead of 264 31 if such a field exists, i.e. it copies the first, not the current publisher’s name into the PO line description.

   In negotiations with publishers, especially when licensing electronic content, it is essential to be able to provide a complete list of all subscriptions, through an agency or directly, of that publisher's titles.

   PO lines should be updated when the related bib record is amended; at the very least, when creating a PO line or manually updating it from the bib record, the current publisher should be imported.

   Martin Gränicher, Library am Guisanplatz
   martin.graenicher@gs-vbs.admin.ch

   Alma provides insufficient data in PO lines for the task of pulling a list of subscriptions a library has of a specific publisher's titles:

   1. The PO line description contains only bibliographical data from the bib record as it was at the time the PO line was created. Subsequent changes in the publisher data are not updated in the related PO lines.

   2. Even in newly created PO lines, Alma introduces the content of MARC field 264 _1 instead of 264 31 if such a field exists, i.e. it copies the first, not the current publisher’s name into the PO line description.

   … more

   128 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  ·  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

2. Alternative Call Number in Manage Patron Services-Requests

   In Manage Patron Services, tab Requests, we can’t display or add Alternative Call Number.
   For us is important the visibility of this field due to it’s our location system.
   We would like this field to be displayed.

   Thanks!

   129 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 - 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

3. Suppress bib record when no active portfolios/services

   If a record has zero active services, it should be automatically suppressed in Primo. When we choose to use the CDI records for a collection instead of the CZ records, there is a button to "change to CDI-only full text activation." This suppresses the service, but it does not suppress the bib records. We have to manually run a job on each collection to also suppress the bib records. Most of the time this is fine (even though it's an extra step), but if some of the CZ bib records overlap with other collections, we don't necessarily want to suppress them all. We only want to suppress the ones with no services.

   There is a SuppressBibWithSuppressedHol setting which means that if all physical holdings in a bib record are suppressed, the bib record itself suppressed. I'd love to see something similar for e-resources, i.e. SuppressBibwithSuppressedServices.

   If a record has zero active services, it should be automatically suppressed in Primo. When we choose to use the CDI records for a collection instead of the CZ records, there is a button to "change to CDI-only full text activation." This suppresses the service, but it does not suppress the bib records. We have to manually run a job on each collection to also suppress the bib records. Most of the time this is fine (even though it's an extra step), but if some of the CZ bib records overlap with other collections, we don't necessarily want to suppress… more

   129 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  ·  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

4. Notify when a title (esp. electronic portfolio) chosen in a Leganto reading list is deleted in Alma

   Especially when dealing with electronic titles, for example when importing them, Alma may delete some portfolios.
   However, researchers may have previously selected these portfolios for their Leganto reading list. But nobody would notice that, until the students find a broken link in Leganto.

   To avoid that right now we perform a manual check, relying on an Analysis looking for Electronic Titles selected for reading lists before running the import, and comparing that with the list of deleted portfolio we have when the import is finished. It's however time consuming.

   It would be much better to get a notification when the deleted title was previously included in a leganto reading list, so that the librarian can replace the related entry with an alternative copy.

   The issue is esp. relevant to electronic titles, however it may also occur with physical titles that are withdrawn, an implementation of such a warning for both electronic and physical titles would be the best solution.

   Especially when dealing with electronic titles, for example when importing them, Alma may delete some portfolios.
   However, researchers may have previously selected these portfolios for their Leganto reading list. But nobody would notice that, until the students find a broken link in Leganto.

   To avoid that right now we perform a manual check, relying on an Analysis looking for Electronic Titles selected for reading lists before running the import, and comparing that with the list of deleted portfolio we have when the import is finished. It's however time consuming.

   It would be much better to get a notification when the… more

   128 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  ·  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

5. Overdue notifications to be sent also on days after closed days

   We noticed that if closed days are configured, and a closed day is between the due date of a loan and the planned day on which the first reminder should be sent, the job does not generate a notification on that day but waits until the next one.
   This leads to misunderstanding on the patrons side, because the grace period is not always identical and can vary depending on possible closed days.
   We described the issue in case nr. 05301818 (old SF nr.: 00953477) and were told that this is the expected behaviour. The Product manager decided that when there's a closed day between the job run and the due date, due to the request for not sending emails on closed days, it will check another extra day.
   We would like IZs to be allowed to choose whether they want this extra day or not, by adding e.g. some parameter in the overdues configuration.

   We noticed that if closed days are configured, and a closed day is between the due date of a loan and the planned day on which the first reminder should be sent, the job does not generate a notification on that day but waits until the next one.
   This leads to misunderstanding on the patrons side, because the grace period is not always identical and can vary depending on possible closed days.
   We described the issue in case nr. 05301818 (old SF nr.: 00953477) and were told that this is the expected behaviour. The Product manager decided that when there's… more

   128 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 - Loans  ·  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. Expired Hold Shelf to Alma mobile

   It would be practical to get the Expired Hold Shelf lists to Alma mobile so we didn't have to print them on paper.

   128 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

7. Adding the publisher location to the "Keywords" index in Alma

   Currently, the publisher location is not indexed in the general "Keywords" index in Alma. If someone wants to search for a certain publisher location, one must use the specific index because a "Keywords" search won't bring any results.
   This is particularly unpractical when searching for series or periodicals, as they often have similar names but different publishers or publisher locations, or later editions of a certain work which can be identified by the different publisher resp. publisher location.
   What confuses staff users is also that if one wants to search for a book, using the title and/or the author as search terms leads to useful results but the simple addition of the publisher location brings no results at all.
   For these reasons, we suggest adding subfields 260 $a, 264 $a, 533 $b, 752 $a-g to the general "Keywords" indexing.

   Currently, the publisher location is not indexed in the general "Keywords" index in Alma. If someone wants to search for a certain publisher location, one must use the specific index because a "Keywords" search won't bring any results.
   This is particularly unpractical when searching for series or periodicals, as they often have similar names but different publishers or publisher locations, or later editions of a certain work which can be identified by the different publisher resp. publisher location.
   What confuses staff users is also that if one wants to search for a book, using the title and/or the author as… more

   128 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  ·  Resource Management - General  ·  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. Adding new labels to a letter in Alma

   In Alma/Administration/General Configuration/Configuration Menu/General Configuration/Letter emails
   I want to add new labels with translation field.

   For example the OrderListLetter.xsl has the following codes:

   department; billingaddress; date; issnisbn; sincerely; addressFrom; Cc; Bcc; note; letterName; orderdate; subject; polinenumber; price; quantity; shippingaddress; shippingmethod; title; vendoraccount; placeorderintroduction

   In Alma/Administration/General Configuration/Configuration Menu/General Configuration/Customize Letters

   We want to add a new header cells, for example:
   <th>@@publication_place@@</th>

   Is there possible to add new codes in “Alma/Administration/General Configuration/Configuration Menu/General Configuration/Letter emails”?

   127 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  ·  Fulfillment - General  ·  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. Allow renaming of normalization, indication, and merge rules

   Please allow renaming of normalization, indication, and merge rules. Right now you can only duplicate the rule and change the name of the copied rule.

   126 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

10. Incorporation of All Indigenous Syllabics from the Canadian Aboriginal Syllabics Unicode Block

    I have a case open with Ex Libris (# 00517082) regarding this. Not all Indigenous syllabics render in Alma, and thus, do not render in Primo either. As an important aspect of Canadian Libraries' commitments to Truth and Reconciliation, and as it is UN's International Year of Indigenous Languages, it would be excellent if Ex Libris could prioritize resolving this issue so that we can allow Indigenous users full discoverability of resources in their own languages.

    125 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  ·  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

11. Add a view option for Attachments.

    Currently if you want to view an attachment (e.g. licence attachment, POL-attachment, etc) you have to download it to your computer. This is very annoying if you just want to have a quick glance at it as your are constantly cleaning out your downloads folder.
    It would be really great if there were a view option which either showed the document in a pop-up or opened it in another tab of your browser.

    126 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  ·  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

12. Hold shelf request slip letter - new regex code table to create pickup number based on internal identifier for Resource sharing requests?

    In 2018, a new letter for hold shelf items was introduced thanks to this idea exchange (https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/32042020-new-letter-for-hold-shelf-slips) It has been very helpful in managing physical item requests, since the letter is customizable.

    We see that improving this letter to also include pickup numbers for resource sharing requests/physical non-returnable. Since these requests do not get a Request ID which then becomes the Additional ID - but rather an Internal ID – the letter could be improved to include a portion of the Internal ID as the pickup number.

    For instance, a RS request has the internal ID 4177325980002286. Following the same logic as how Additional ID is generated, the pickup number would become 417-732-598 and can be included in Hold Shelf letters to the end user as well.

    This would work for both regular material types, and physical non-returnable, since both are assigned an internal identifier on the borrowing library side.

    In 2018, a new letter for hold shelf items was introduced thanks to this idea exchange (https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/32042020-new-letter-for-hold-shelf-slips) It has been very helpful in managing physical item requests, since the letter is customizable.

    We see that improving this letter to also include pickup numbers for resource sharing requests/physical non-returnable. Since these requests do not get a Request ID which then becomes the Additional ID - but rather an Internal ID – the letter could be improved to include a portion of the Internal ID as the pickup number.

    For instance, a RS request has the internal ID 4177325980002286. Following… more

    125 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  ·  Resource Sharing  ·  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. Related holdings displayed only after "direct" holdings in the brief results

    Currently, only 5 holdings are displayed in the "Physical" tab in the brief results list in Alma. In many cases holdings and "related" holdings are mixed and displayed without any particular ranking. Especially when many of them are present, it takes many clicks before one can exclude the related holdings and obtain a list of all holdings linked directly to a record.
    The "Physical" tab in Alma could be changed like this: all holdings linked directly to the record are displayed first (regardless of the library), and only then come the holdings of related records.

    125 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

14. Provide email address information in search results of patron search

    When searching for patrons through Fulfilment>Manage Patron Services, it would be useful if the search results included the patron's email address so that library staff had a unique identifier to check against when there a multiple patrons with the same name.

    122 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 - General  ·  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. Enhanced “In Transit” flow/functionality

    We encounter a lack of important functionality to efficiently follow-up on In transit requests (physical item requests to another pick-up location). We would like the functionality to be extended with the following additional features:
    1. A patron facing letter when the requested item is placed “in transit” by the owning library, so that the patron is better informed of the status of his request.
     We want to create a situation that once a requested item is being transported, there is in fact no way back and a fee needs to paid.
    2. To make it impossible for patrons to cancel their request in Primo once the requested item is already in transit or on the hold shelf in the pick-up location.
     We need a granular setup config to define the end user cancellation option in Primo based upon the status of the request.
    3. A letter to the owning library when a patron is cancelling his request in Primo, so that the owning library might avoid sending items that have already been cancelled.
     Context: multiple different libraries within 1 institution, and some of these libraries handle dozens of request per day based upon the request slip. This means:
    o It’s too time consuming to check the expired hold shelf for all items which are possibly cancelled…
    o A cc or bcc added to the cancellation letter is not an option, because this is an institutional letter and cancellation request letters will come in from multiple libraries… The ‘alert’ / letter needs to be owning library specific!

    We encounter a lack of important functionality to efficiently follow-up on In transit requests (physical item requests to another pick-up location). We would like the functionality to be extended with the following additional features:
    1. A patron facing letter when the requested item is placed “in transit” by the owning library, so that the patron is better informed of the status of his request.
     We want to create a situation that once a requested item is being transported, there is in fact no way back and a fee needs to paid.
    2. To make it impossible for patrons to… more

    122 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

16. Job or tool for extraction of related bibliographic records

    We would like the ability to get a hold of or extract the related bibliographic records in bulk based on a set of (other) bib-records.

    Alma already now automatically displays related records in "other details". We understand that the links are built based on bibliographic data in the MARC linking fields: 773, 774, 777, 786, 800, 810, 811, and 830 (subfield w,x,z).

    An example of a related record is a title within a monographic series. In this case, the bib record for the single monograph has a 830 $w with the MMS-ID/system number of the superordinate bib record.

    We would like exactly this function but not only for one title but for a set of bib records.

    Use cases are:

    • Moving a part of our library to a different location or even library. We make the selection for the move based on items with a certain call number or location, but have trouble getting a hold of holdings which might belong to related bib-records but don’t have a permanent call number or a specific location.

    • When migrating from Aleph to Alma, a lot of sub- and superordinate bib records were not anchored in our Institution Zone, because they didn’t have inventory. However, they’re related to bib-records on superordinate (series) or subordinate (journal articles) level, which do have inventory. Now we need to find those related records in order to anchor them into our IZ.

    We imagine, the easiest way would be to create a job, which exports all related bib-records based on a set of bib-records. Also an analytics-column, which displays all related MMS-IDs would work. The export should include the type of link (MARC field 773, 800, etc.) and all the other subfields of those MARC fields, so that we can sort the export list accordingly.

    Since cataloguing hierarchical bib records is widely practiced all over the world and especially so in the German speaking regions, and since they’re part of the RDA cataloguing regulations, we are convinced, that this could be useful for many libraries.

    We would like the ability to get a hold of or extract the related bibliographic records in bulk based on a set of (other) bib-records.

    Alma already now automatically displays related records in "other details". We understand that the links are built based on bibliographic data in the MARC linking fields: 773, 774, 777, 786, 800, 810, 811, and 830 (subfield w,x,z).

    An example of a related record is a title within a monographic series. In this case, the bib record for the single monograph has a 830 $w with the MMS-ID/system number of the superordinate bib record.

    We would… more

    122 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 →
    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. Bulk waiving by date

    Currently we are unable to do bulk waives within set dates, for example - 01/04/2020 - 02/09/2020. We need to run bulk waives on fines accrued during lockdown periods.

    120 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…)
    4 comments  ·  Fulfillment - Fines &Fees  ·  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. Option to change default management tag publishing for bibs

    When creating or importing new bib records from an external source (especially OCLC), the bib's default management tag in the MDE is set to "Publish Bib" for publishing under "Export to WorldCat". However, "Publishing Holdings Only" is useful for the purposes of publishing our library's Local Holdings Records (LHRs), and other libraries may not want to publish bibs or holdings by default at all. The option to choose between one of these three publishing defaults would benefit libraries who would otherwise need to either regularly update batches of records or manually edit each one as they're created.

    119 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  ·  Resource Management - General  ·  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. More humanity in the letters: add the name of librarians who take care of the requests

    Automatic processes in Alma make library staff save time and efforts, but also significantly reduce human interactions with patrons (very few emails are personally sent by librarians to patrons). Lots of Alma letters sent to patrons are nameless and only signed by generic service names like "Acquisitions Department", "Circulation Desk", "Library ABC" etc. (see @@department@@ in the Labels). Some staff members suffer from this dehumanization in the processes.

    We want to give a name and a face to a request when patrons get notified and would like to enrich some Alma letters with the name of the librarian who took care of the requests and add a line like for example "You have been served by: Jane Smith". Behind the librarian's name in the letter, the customer could create a link to the librarian's webpage, LibGuides profile pages, the University directory, etc. with the XSL template.

    For at least the last staff member who worked on the requests (item hold at the circ desk, digital material sent, item received/activated...), please add the following staff User information:
    - First name
    - Middle name
    - Last name
    - Preferred middle name
    - Preferred first name
    - Preferred last name
    - Primary identifier
    - Job category
    - Job description
    - Website URL
    in the XML of the following Alma letters:
    - Document Delivery Notification Letter
    - Ful Cancel Request Letter
    - Ful Digitization Notification Item Letter
    - Ful Personal Delivery Letter
    - Interested In Letter
    - On Hold Shelf Letter
    - Purchase Request Status Letter

    Automatic processes in Alma make library staff save time and efforts, but also significantly reduce human interactions with patrons (very few emails are personally sent by librarians to patrons). Lots of Alma letters sent to patrons are nameless and only signed by generic service names like "Acquisitions Department", "Circulation Desk", "Library ABC" etc. (see @@department@@ in the Labels). Some staff members suffer from this dehumanization in the processes.

    We want to give a name and a face to a request when patrons get notified and would like to enrich some Alma letters with the name of the librarian who took… more

    118 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

20. Resource Sharing - Status of Renewed Lending Request not clear

    After Renewing a Lending request the status automatically updates to "Received by Partner" - it would be more helpful if the status updated to 'Renewal Accepted".

    117 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  ·  Resource Sharing  ·  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