1693 results found

1. The Provenance field in the physical item editor

   We would like the Provenance field in the physical item editor to be mandatory.
   It is possible to have a default for the list but that is not the same thing. We are afraid people will be not so attentive, and the default option will be the one they always choose. We want it to be mandatory and default to nothing. The user then has to choose something in order to save the item.

   4 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

2. Webhooks enhancement

   We're using webhooks as a proof of concept on our sandbox, for the time being. In particular, we use webhooks on loans.
   Official documentation :
   https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/090Integrations_with_External_Systems/030Resource_Management/300Webhooks

   We're bothered by the ecological/energy waste generated by this webhook. Unlike the notification webhooks, this webhook does not provide any filtering.
   If we activate it in production, we estimate that there will be almost 500,000 API calls per year, for which only 1% will result in an action according to our action rules.
   Can we have a possibility to filter the webhooks on loans, according to these criteria (and / or):
   -item library
   -item location
   -item temporary location
   -item policy.

   We're using webhooks as a proof of concept on our sandbox, for the time being. In particular, we use webhooks on loans.
   Official documentation :
   https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/090Integrations_with_External_Systems/030Resource_Management/300Webhooks

   We're bothered by the ecological/energy waste generated by this webhook. Unlike the notification webhooks, this webhook does not provide any filtering.
   If we activate it in production, we estimate that there will be almost 500,000 API calls per year, for which only 1% will result in an action according to our action rules.
   Can we have a possibility to filter the webhooks on loans, according to these criteria (and / or):
   -item library
   -item… 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  ·  Webhooks  ·  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

3. Add call number to General information box

   In the new UI, when searching for a title, the results do not display the call number in either the holdings summary on the left, or the general Information box on the right. yes, it's only a click away in the 'Holdings' option, but when you're doing a task involving a lit of, say, 200 items, that's 200 extra clicks.
   the General information box already shows Material Type, ISBN, Edition, Brief level 10, and a whole lot of other things, so why not the call number?

   5 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  ·  Acquisitions - 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

   Submit Rating

4. Alma : add search indexes for all MARC21 fields

   We would find it very helpful if the tag and the search index were displayed in the search. Sometimes the tags are not self-explanatory, there are multiple similar tags or there are different ways to name it. So, one must regularly check the list (https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/Metadata_Management/180Search_Indexes/050MARC_21_Search_Indexes) to see what the exact designation is.
   So if the field code (= search index) were provided as well, it would be very helpful. This way, one could search by tag or search index.

   Thanks for your help !

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

5. Allow POL and INV Line 'Save' with errors. NOT 'Save and Continue'--just 'Save'.

   We occasionally need to create a POL on the fly, and before I've set up the relevant fund--usually because a vendor needs a POL number right away, but information in hand can be incomplete for other reasons as well.

   'Save and Continue' should remain totally impossible without mandatory fields completed, but it's annoying to have to re-start work from scratch when I realize I'm missing a bit of info, e.g. price or fund. As it is, I usually just throw in a fake price and an existing fund as a placeholder, but those just blend in if I get de-railed midstream.

   If it were possible to leave blanks on initial 'Save', the info already entered would not have to be re-typed, and such orders, if not completed immediately, would be easy to i.d. through an Analytics query if the operator (not always me) got diverted .

   We occasionally need to create a POL on the fly, and before I've set up the relevant fund--usually because a vendor needs a POL number right away, but information in hand can be incomplete for other reasons as well.

   'Save and Continue' should remain totally impossible without mandatory fields completed, but it's annoying to have to re-start work from scratch when I realize I'm missing a bit of info, e.g. price or fund. As it is, I usually just throw in a fake price and an existing fund as a placeholder, but those just blend in if I get de-railed… more

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

6. Add Detail for Payment Method=Accounting Department in Vendor Record/Account

   Payment Method=Accounting Department is used to route invoices through our campus check feed/ERP export. However, at the campus financial system level, there are multiple options for how the vendor gets paid, including PaymentPlus, ACH (via Paymode-X), as well as paper check. It would be good to 1) record this information as a detail of Payment Method=Accounting Department, 2) be able to modify specifics via a table as needed for institution variations, as well as 3) have the fields available via Analytics. Ex. Campus has made a change in issuing checks, and we would like to communicate this change to our library vendors (getting Analytics output isolating those only those vendors paid by check first).

   Payment Method=Accounting Department is used to route invoices through our campus check feed/ERP export. However, at the campus financial system level, there are multiple options for how the vendor gets paid, including PaymentPlus, ACH (via Paymode-X), as well as paper check. It would be good to 1) record this information as a detail of Payment Method=Accounting Department, 2) be able to modify specifics via a table as needed for institution variations, as well as 3) have the fields available via Analytics. Ex. Campus has made a change in issuing checks, and we would like to communicate this change to our… more

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

7. Add Scan in message with "Cancel" option for items currently on loan

   A common mistake when working with "Scan in" is to accidentally scan in the same item twice. When working with home deliveries, this means the first scan in will loan the item out to the patron, while the second scan in will return it again. This alone might be a problem, but it gets even worse when there are requests for the item. The item will either be placed on hold shelf for or even loaned out to the next patron if it was requested for home delivery. In both cases, both the new and the old patron might receive messages telling them about the status change, which means we don't only have to fix the situation in Alma but also communicate the mistake and explain the messages to the patrons.

   There are blocks to prevent items that are lent out to one patron from being lent out directly to another without return first, but since the Scan in workflow does a return first and only then tries to loan the item out, it will not help in this scenario.

   Instead I suggest adding another "Scan in message" with the "Cancel" option to make it possible to abort the scan in. The simplest implementation would be to just warn for any lent out item, letting the operator decide if they should proceed, but that might be problematic for some who use scan in extensively to (intentionally) return books. If so, more complex logic might be required, like triggering only if the item is also requested.

   With this change, there is a second chance of catching the mistake before it makes a mess of the request queue.

   A common mistake when working with "Scan in" is to accidentally scan in the same item twice. When working with home deliveries, this means the first scan in will loan the item out to the patron, while the second scan in will return it again. This alone might be a problem, but it gets even worse when there are requests for the item. The item will either be placed on hold shelf for or even loaned out to the next patron if it was requested for home delivery. In both cases, both the new and the old patron might receive… more

   3 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  ·  Edit…  ·  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

8. MDE Search Resources mask should be empty

   When opening the Search Resources mask in MDE, the previous search is still in the data mask. For us there is no benefit for this behavior and we would like to have an empty mask and not to clear the mask every time before starting a new search.
   (If other libraries need this opportunity, we would suggest to make the default settings for this mask customizable)

   72 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

9. Arrow keys now 'stick' in fields in MDE

   When navigating through records in MDE, if you've previously typed anything in a field, you now cannot move out of that field using the arrow keys. It's not entirely consistent and sometimes does let you move out the field, while other times it 'sticks' randomly in fields you haven't edited at all, but in general it is extraordinarily inconvenient.

   I see using the arrow keys to move within a field was previously suggested as a feature, but even within that suggestion, the idea included the stipulation that if the cursor was already at the start/end of a line hitting up/down should then move to the previous/next field.

   When navigating through records in MDE, if you've previously typed anything in a field, you now cannot move out of that field using the arrow keys. It's not entirely consistent and sometimes does let you move out the field, while other times it 'sticks' randomly in fields you haven't edited at all, but in general it is extraordinarily inconvenient.

   I see using the arrow keys to move within a field was previously suggested as a feature, but even within that suggestion, the idea included the stipulation that if the cursor was already at the start/end of a line hitting up/down… 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  ·  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

10. Dear colleagues, regarding Alma interface, it would be highly useful that the option EDIT ITEM had a 1-step shortcut.

    Dear colleagues, regarding Alma interface, it would be highly useful that the option EDIT ITEM had a 1-step shortcut. It is pretty annoying to continuously click 3 times to open de item in order to work on it. Thank you for your attention.

    •  

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

11. Support Storage Location ID in SRU and Barcode API Queries

    Hi,

    Currently, Alma's BIB SRU interface does not support querying by Storage Location ID. This limits our ability to perform targeted searches for items based on their physical storage location, which is a critical need for institutions managing remote or offsite collections.

    We propose the following enhancements to improve Alma's interoperability and search capabilities:

    1. Extend the BIB SRU “q” parameter to support querying by Storage Location ID.

    2. Introduce an ITEM-level SRU endpoint, similar to the existing BIB SRU, that would support more granular item-level searches including by Storage Location ID.

    3. Alternatively or additionally, add Storage Location ID as a searchable field in the existing Alma API that supports querying by barcode.

    Example Usage:

    Libraries with multiple storage locations, including remote or automated facilities, need an efficient and standardized way to locate and manage items based on their storage location. Having Storage Location ID available in SRU and APIs would allow seamless integration with external inventory systems and automation workflows.

    Impact:

    • Streamlines item management in large and complex storage environments.

    • Enables better automation of inventory and retrieval tasks.

    • Facilitates integration with third-party systems through standards-compliant interfaces.

    We appreciate your consideration and look forward to seeing this functionality included in a future Alma release.

    Thank you,
    Shaul Greenstein
    NLI-Library

    Hi,

    Currently, Alma's BIB SRU interface does not support querying by Storage Location ID. This limits our ability to perform targeted searches for items based on their physical storage location, which is a critical need for institutions managing remote or offsite collections.

    We propose the following enhancements to improve Alma's interoperability and search capabilities:

    1. Extend the BIB SRU “q” parameter to support querying by Storage Location ID.

    2. Introduce an ITEM-level SRU endpoint, similar to the existing BIB SRU, that would support more granular item-level searches including by Storage Location ID.

    3. Alternatively or additionally, add Storage Location ID as a searchable… more

    1 vote

    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

12. When you close an invoice, the price can automatically be updated in PO-Line to the same on the invoice

    Is there a possibility that when you change the price in the invoice and close the invoice with the correct price, that it can automatically change and insert the correct price into PO-Line/Items?

    • 

    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…)
    0 comments  ·  Acquisition - Invoices  ·  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. barcode added to "pick from shelf" list

    more of a question.
    Can the barcode be added to the 'pick from shelf' list'? It would be helpful when printing the item page from the list and it would also be beneficial if the item barcode was visible instead of have to hit the requests number for the barcode.
    Thank you
    joann

    •  

    23 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

    Submit Rating

14. Implement Automatic Upload of Electronic Holdings for Perlego eBooks

    Implement auto holdings (autoholding, automatic upload of e-holdings) for Perlego eBooks.

    This will allow for automatic update of the collection based on most recent institutional holdings file received from Perlego.

    As is already available for ProQuest, Springer, Elsevier, Wiley, and other publishers.

    22 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 - Electronic  ·  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. Open / Closed Stacks Request Possibilities Priority

    Currently, when a library owns a title in several copies, and that some of these copies are dispatched between physical locations attached to both closed and open stacks fulfillment unit, all copies behave like open stacks.

    In other terms: if we have two items, one in open-stacks and one in closed-stacks, title-level requesting is blocked as long as the open-stacks item is available. Hence, open stacks configuration takes precedence over the closed one.

    We would like that whenever an available item is stored in a closed stacks location alongside other open stacks available items, users still can request the item from Discovery, request being placed on the closed stack item.
    For more technical information: SF Case 06737777.

    Thank you very much in advance, best regards,
    Renaud Arlettaz for SLSP

    Currently, when a library owns a title in several copies, and that some of these copies are dispatched between physical locations attached to both closed and open stacks fulfillment unit, all copies behave like open stacks.

    In other terms: if we have two items, one in open-stacks and one in closed-stacks, title-level requesting is blocked as long as the open-stacks item is available. Hence, open stacks configuration takes precedence over the closed one.

    We would like that whenever an available item is stored in a closed stacks location alongside other open stacks available items, users still can request the item… more

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

16. Alma APIs Multilingual Code-tables

    We’d like to request an enhancement to the Alma API that would allow PUT and POST requests to include translation updates. Currently, only GET requests support the lang parameter for retrieving localized data, while updates ignore these descriptions. Enabling translation updates via API would streamline content management across languages, making it easier to keep localized information current and consistent.

    Updating code tables for around 80 patron-facing letters in three different languages via the web UI is extremely time-consuming and inefficient. Allowing translation updates through the API would greatly improve this process, making Alma more effective for multilingual institutions.

    We’d also like to highlight an inconsistency: the addressFrom field, which represents an email address, is language-dependent in the current setup. Since email addresses are universal and not language-specific, it would make more sense for this field to remain constant across all languages.

    Allowing language-neutral fields like addressFrom to remain consistent would simplify multilingual management and avoid unnecessary duplication across language settings.

    We’d like to request an enhancement to the Alma API that would allow PUT and POST requests to include translation updates. Currently, only GET requests support the lang parameter for retrieving localized data, while updates ignore these descriptions. Enabling translation updates via API would streamline content management across languages, making it easier to keep localized information current and consistent.

    Updating code tables for around 80 patron-facing letters in three different languages via the web UI is extremely time-consuming and inefficient. Allowing translation updates through the API would greatly improve this process, making Alma more effective for multilingual institutions.

    We’d also… more

    20 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  ·  APIs and Integrations  ·  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

17. Customize secondary search menu under Borrowing/Lending requests

    When searching under Borrowing & Lending requests, the order of the search field options defaults to alphabetical.

    It would be nice to have the ability to customize the order of the search options, so the most used fields can be placed closer to the top of the list to avoid extra scrolling.

    For example, searching by Title is common, but the option is near the bottom of the menu. Staff need to scroll down to it every time they want to search requests by Title.

    It would be nice to at least be able to identify a favorite search field, so the menu could default to that every time.

    When searching under Borrowing & Lending requests, the order of the search field options defaults to alphabetical.

    It would be nice to have the ability to customize the order of the search options, so the most used fields can be placed closer to the top of the list to avoid extra scrolling.

    For example, searching by Title is common, but the option is near the bottom of the menu. Staff need to scroll down to it every time they want to search requests by Title.

    It would be nice to at least be able to identify a favorite search field,… more

    •  

    7 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 →
    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. Add email address to Contact People table in Vendor Details>Contact People

    We are configuring Vendors as new Alma customers, and we wish it was easier to immediately see the Vendor Contact People email addresses (and easily copy and paste them or even hyperlink) without having to click into the record to track down the email address.
    Please see screenshot attached showing where this information would be helpful.
    If there is a way to make the email address visible that we have not discovered as Alma newbies, I'd also love to learn this!
    Thank you,

    Abigail Wickes (she/her/hers)
    Electronic Resources Management Librarian
    Email: abigail.wickes@duke.edu

    • 

    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…)
    0 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

19. Allow sort configuration in Primo (VE and NDE) brief results view and Collections View

    Currently as far as is known, search results and collections items can only be sorted by year. Multiple records with the same year creation date cannot be further sorted.
    See https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/Primo/Technical_Guide/010The_PNX_Record/080The_Sort_Section

    "[The Sort section] is not applicable to Primo VE environments. Only the Display, Facets, and Search sections are configurable in Primo VE"

    ---

    I would like to be able to sort a set of records by specific date (day, month, year) in any list of multiple records (collection with items view, basic brief records view, etc.).

    This could be based on whatever date structure is necessary (yyyymmdd, etc.) and could use any possible MARC field, though MARC 033 $a seems like the best choice for basing a function on a structured exact date.

    Alternatively, allow users to configure custom sort indexes based on fields of their choice.

    Currently as far as is known, search results and collections items can only be sorted by year. Multiple records with the same year creation date cannot be further sorted.
    See https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/Primo/Technical_Guide/010The_PNX_Record/080The_Sort_Section

    "[The Sort section] is not applicable to Primo VE environments. Only the Display, Facets, and Search sections are configurable in Primo VE"

    ---

    I would like to be able to sort a set of records by specific date (day, month, year) in any list of multiple records (collection with items view, basic brief records view, etc.).

    This could be based on whatever date structure is necessary (yyyymmdd, etc.) and could… more

    1 vote

    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  ·  Other  ·  Edit…  ·  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

20. Implement Checks on the Authority Heading Type for Institutions Using ID-based Authority Control

    Currently, when authority linking in Alma is based on ID rather than text, Alma does not check whether the authority heading type in the bibliographic record matches the heading type in the authority record. For example, Alma will link a 600 tag in the bib record for personal names with an authority record whose heading is in tag 110 for corporate names if their ID matches, even though Alma would not offer that option if F3 were pressed.

    We would like Alma to (1) avoid linking in such cases and (2) flag these instances in the authority control task list.

    We ran into this issue in the context of a migration from a non-MARC21 system, from where we still receive authority records that are mapped to MARC21. Initially, a certain sort of authority record was converted into personal name authority records (X00), which was changed later into corporate name authority records (X10). Consequently, we had to clean up instances where the authority heading type in the bib records does not match the heading type of the authority record.

    We had hoped to use the authority control task list to identify those instances where linking would fail due to a mismatch of authority types. However, according to Ex Libris, case 07775618, checking the authority heading type is only available for institutions using text-based authority linking.

    Ex Libris wrote: "The product manager thoroughly reviewed this case as a part of the issue handling and advised the designed behavior. The linking of direct ID authority is not dependent on specific heading types but is instead based on matching the 035 value of the authority with the $0 subfield of the bibliographic field. This means that direct ID authority linking does not involve additional checks for heading types. For example, it will correctly link a 650 field in the bibliography with a 110 field in the authority, as only the match in subfield $0 is considered. Similarly, any changes to the field tag in the linked authority record would not affect the field tag in the linked bibliographic record."

    We believe that adding checks on the authority heading type will benefit also other libraries that use ID-based authority linking.

    Currently, when authority linking in Alma is based on ID rather than text, Alma does not check whether the authority heading type in the bibliographic record matches the heading type in the authority record. For example, Alma will link a 600 tag in the bib record for personal names with an authority record whose heading is in tag 110 for corporate names if their ID matches, even though Alma would not offer that option if F3 were pressed.

    We would like Alma to (1) avoid linking in such cases and (2) flag these instances in the authority control task list.

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