1698 results found

1. Job “Withdraw Physical items” and holding of related records

   With the “Withdraw Physical items” job, Alma does not provide the option of preventing the deletion of holding and bibliographic records when there are Holding of related record. We would like an additional option “Delete holdings; delete bibliographic records that have no other holdings and that have no Holding of related records”.

   39 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   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. Allow the keyword function to search up permanent call numbers directly

   If I enter a call number into the keyword search box, it will often show no results despite showing results when the search category is switched to "permanent call number." Inputting an OCLC into the keyword search consistently yields accurate results, so why can't it do so with call numbers?

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

3. Make Existing Record Primary When Merging via Search Resources

   When merging records through Alma’s Search Resources, make the existing Alma record the Primary and the incoming external record the Secondary.

   Currently, when bringing in external records, Import and Integration Profiles treat the existing Alma record as Primary, but Search Resources makes the external record Primary. This inconsistency forces libraries to maintain two opposing sets of merge rules, depending on how the record enters Alma.

   Making the Alma record Primary in Search Resources would align the behavior with other workflows. This could be configurable or at least opt-in so libraries can adjust their merge rule settings in the External Search Resources configuration to coincide with the change.

   Benefits:
   Simplifies workflows by allowing a single set of merge rules.
   Reduces user confusion, since rule descriptions will match consistently across scenarios.
   Provides consistency in the Metadata Editor, where the record on the left will always be the Primary.

   When merging records through Alma’s Search Resources, make the existing Alma record the Primary and the incoming external record the Secondary.

   Currently, when bringing in external records, Import and Integration Profiles treat the existing Alma record as Primary, but Search Resources makes the external record Primary. This inconsistency forces libraries to maintain two opposing sets of merge rules, depending on how the record enters Alma.

   Making the Alma record Primary in Search Resources would align the behavior with other workflows. This could be configurable or at least opt-in so libraries can adjust their merge rule settings in the External Search… 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  ·  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

   Submit Rating

4. Display personal metadata editor history of opened/edited records

   Currently in Alma's All Titles search you can see a list of records you have previous looked at, but it would be helpful in the metadata editor if you had a list of records that you have opened recently. Even a list of 5-10 would helpful.

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

5. FUND / Ledger facet missing from PO Line user interface

   All PO Lines has multiple facets but FUND or Ledger is not one of them.

   Funds, both allocated & summary, are fundamental to purchasing and we'd like to be able to filter the PO Line display by these variables.

   Please add a facet in the All PO Lines user interface for FUND.

   52 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   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. Enable creation of individual patron blocks for loans of specific material types

   If an institution needs to prohibit an individual user from borrowing a particular type of resource temporarily, e.g. placing a temporary ban on laptop loans for that person, then there is no way to block them from borrowing items of that specific material type without preventing them from borrowing everything else as well. As a result, we are unable to apply blocks in exceptional circumstances, such as with our laptop loans service, because the block would be disproportionate and prevent the user borrowing any physical items at all. The only workaround would be to have a ‘Blocked’ user group configured not to be able to borrow that specific material type, to which users being blocked could be assigned temporarily. However, that is not a workable solution for us because each of our User Groups has different entitlements to length of loan period, maximum number of items, and so on. We would like the ‘Blocks’ tab in a patron record to enable individual material types to be selected when creating a block for that user, determining the scope of that block.

   If an institution needs to prohibit an individual user from borrowing a particular type of resource temporarily, e.g. placing a temporary ban on laptop loans for that person, then there is no way to block them from borrowing items of that specific material type without preventing them from borrowing everything else as well. As a result, we are unable to apply blocks in exceptional circumstances, such as with our laptop loans service, because the block would be disproportionate and prevent the user borrowing any physical items at all. The only workaround would be to have a ‘Blocked’ user group configured… more

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

   Submit Rating

7. create a new item status for items "lost on shelves"

   Currently items can be marked as Missing (if not found in the Library), or Lost (if long overdue on user's account). Missing books are regularly checked on, but some of them cannot be tracked within a reasonable time for users, and the search becomes more of an in-house task than fulfilment of an immediate customer need.
   However, it is not possible to distinguish between items marked missing relatively recently and still actively searched for (e.g. because we could not find them immediately when requested by users), and those which were not found after several checks, for a long time, even if we think they should be in the library and we do not want to delete their record.
   For that reason the missing books' list is ever growing, and working with it is frustrating because more often than not colleagues are checking for hundreds of items which are not urgent to find (e.g. users do not need them any more), and which are maybe not important to check on regularly as we could mark them available again as and when they re-surface.
   I would like to see a separate item status for these books to make our work easier, to eliminate the need to put these items in some sort of Work Order as a workaround because those WOs expire and have their own sets of problems, and to improve our customer service by being able to focus on the missing books currently required by our users.
   The new item status could mean an automatic supress from Discovery, would allow us to list these items if we have the need for that, but most importantly, would allow us to treat currently missing (and actively/urgently searched for) items separate from those long-term missing ones

   Currently items can be marked as Missing (if not found in the Library), or Lost (if long overdue on user's account). Missing books are regularly checked on, but some of them cannot be tracked within a reasonable time for users, and the search becomes more of an in-house task than fulfilment of an immediate customer need.
   However, it is not possible to distinguish between items marked missing relatively recently and still actively searched for (e.g. because we could not find them immediately when requested by users), and those which were not found after several checks, for a long time, even… more

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

8. Enable us to display items in an "Unavailable" location type as Unavailable in Primo

   We need the ability to show items that are assigned to a location with Type = UNAVAILBLE to show as unavailable in Primo

   The primary use cases that prompt this idea are:
   1. A library is closed for renovation and the items are inaccessible to staff and patrons, but the items must still be discoverable so that patrons can be directed to Resource Sharing in Primo.
   2. Portions of a collection are temporarily inaccessible to staff and patrons, and the items are assigned to a temp location, but must still be discoverable so that patrons can be redirected to Resource Sharing in Primo.
   In both of these use cases, setting the Location(s) to type = UNAVAILABLE accomplishes both suppressing a link for local requesting, and allowing a Request for Resource sharing link to appear, without any other configuration changes

   Right now, items that are in a type=UNAVAILABLE location show in Primo with a prominent "Available" indicator in several places, and use the label for c.uresolver.getit2.item_list.status.ITEM_IN_PLACE in ViewIt, even though the items are not actually available. There is no way to use existing functionality to suppress this "Available" label or the "In library" (ITEM_IN_PLACE) label without an unreasonable amount of work (see info on the impracticability of using work orders below)

   What is needed:
   1. The calculated availability for items in a type=UNAVAILABLE location needs to be Unavailable/Not Available, when Alma might otherwise consider the items to be "in place" (not on loan, not in a process, etc)
   2. The ViewIt information for items in a type=UNAVAILABLE location needs to use a new label, and not the "c.uresolver.getit2.item_list.status.ITEM_IN_PLACE" label

   Why the suggestion on the closed Idea 46262368 "make location type 'unavailable' functional: items in these locations should be shown as unavailable in Alma and Primo" (see URL below) of using work orders to accomplish this is unworkable:
   1. Work orders cannot be removed in bulk. If there are 300000 items that needs to be set to UNAVAILABLE, removing 300000 work orders manually when they are available again is an enormous burden on staff, and is practicably impossible.
   2. Patrons find the Primo display of items in work orders to be confusing
   3. Items in work orders are requestable unless further changes are made to the items or to configurations. Using a type=UNAVAILABLE location accomplishes the un-requestability without needing to do any other configuration or data changes,

   SUMMARY:
   Give us the ability to show items in a type=UNAVALABLE location as unavailable in Primo
   - enabling clear and understandable display of an item's availability to our patrons
   - without onerous additional work

   Note: this is basically a repost of https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/46262368-make-location-type-unavailable-functional-items
   That idea was closed despite support for the idea, and despite the unworkability of the "just put them in a work order" response from Ex Libris

   We need the ability to show items that are assigned to a location with Type = UNAVAILBLE to show as unavailable in Primo

   The primary use cases that prompt this idea are:
   1. A library is closed for renovation and the items are inaccessible to staff and patrons, but the items must still be discoverable so that patrons can be directed to Resource Sharing in Primo.
   2. Portions of a collection are temporarily inaccessible to staff and patrons, and the items are assigned to a temp location, but must still be discoverable so that patrons can be redirected to Resource… more

   •  

   267 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…)
   8 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
   AdminTamar Fuches (Alma product manager, Ex Libris) responded

   Dear colleagues,

   Thank you for raising this idea.

   This was part of the CERV cycle in 2025, but did not make it to the final list.

   During the analysis, 3 possible approaches were discussed, each has a different estimation and effort:

   Option 1: New dedicated process type

   • It will be possible to mark specific items as "unavailable", similarly to the way it is possible to mark them as "missing"
   • Items marked as "unavailable" will be considered as "not in place"
   • The new "unavailable" option will appear as a possible process type in all the places where there is a list of process types, including configuration options such as Fulfillment Unit Rules

   Option 2: Mark a location as "unavailable"

   • It will be possible to mark a location as "unavailable"
   • All items in this location will be considered as "not in place"
   • The difference from option 1 is that when an item is in an "unavailable" location, it can still be in a process such as loan, work order or any other process type. These are 2 separate attributes
   • The existing options for location based configuration can be used

   Option 3: A new "unavailable" field in item level

   • It will be possible to mark specific items as "unavailable", similar to the availability status of portfolios
   • Items marked as "unavailable" will be considered as "not in place"
   • Similar to option 2, "unavailable" item can still be in a process such as loan, work order or any other process type. These are 2 separate attributes
   • As this is a new attribute, relevant configuration options will need to be enhanced to take this attribute into consideration. Further analysis will be needed here

   Although option 3 might give more flexibility, it is super complicated and would require huge effort. Therefore, the selected option is option 2: Mark a location as "unavailable".

   The description of this idea exchange sounds like this option, however in the comments I saw some references to option 3. Therefore I wanted to share with you the analysis and discussion - you can see it in: https://public.3.basecamp.com/p/ERLrkhNUHtTYerEiaQAsG2uT

   Please note that as this did not make it to the final list of the CERV selected items, there is no timeline for implementing this.

   Thanks,

   Tamar Fuches

   Alma product team

   Dear colleagues,

   Thank you for raising this idea.

   This was part of the CERV cycle in 2025, but did not make it to the final list.

   During the analysis, 3 possible approaches were discussed, each has a different estimation and effort:

   Option 1: New dedicated process type

   • It will be possible to mark specific items as "unavailable", similarly to the way it is possible to mark them as "missing"
   • Items marked as "unavailable" will be considered as "not in place"
   • The new "unavailable" option will appear as a possible process type in all the places where there is a list of process types, including configuration options such as Fulfillment Unit Rules

   Option 2: Mark a location as "unavailable"

   • It will be possible to mark a location as "unavailable"
   • All items in this location will be considered as "not in place"
   • The difference from option 1 is that when an item… more

9. Limit number of resource sharing partners in a borrowing request's rota

   We sometimes see instances where a problematic resource sharing requests are sent to dozens of partners before they're cancelled or go unfilled. It would be very helpful if we could somehow limit the number of partners that appear in a request's rota. Since we would always want to include a lender of last resort like ILLiad or WorlsShare ILL as the final partner, it would probably be best to allow us to limit the number of partners from a specific rota template that can be added to a rota.

   73 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

10. Drop line breaks while compiling XML for import profile

    Many of our vendors upload MARC files to an FTP server and the files are processed by our import profiles. When there are line breaks in the files (usually in a note field that is copied into the MARC from another source), the file is treated as invalid MARC. This error is identified after all the files for that profile have been combined, so the import job kicks out valid MARC files in addition to the ones containing errors. Since these are being uploaded by the vendor, we often don't notice that there is a problem until a staff member is looking to receive and pay for the materials.

    I would like to suggest that Alma do some normalization to drop paragraph and line breaks from files (or replace them with spaces) prior to compiling the file into XML.

    Many of our vendors upload MARC files to an FTP server and the files are processed by our import profiles. When there are line breaks in the files (usually in a note field that is copied into the MARC from another source), the file is treated as invalid MARC. This error is identified after all the files for that profile have been combined, so the import job kicks out valid MARC files in addition to the ones containing errors. Since these are being uploaded by the vendor, we often don't notice that there is a problem until a staff member… more

    •  

    •  

    •  

    19 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. Buffer periods for Last Interest Date for Borrowing Requests

    ISSUE: Quite a few of our borrowing requests are getting cancelled automatically by Alma, because people are setting a Last interest date of the same day or the next day. Unrealistic expectations are being created by the Last Interest Date. Yet, staff find it useful to know the Last Interest Date for borrowing requests where the patron indicates a date some time into the future.

    LOCATION: ILL request form, patron facing (e.g. in Primo VE).

    SOLUTION: Allow buffer periods to be implemented on the Last Interest Date. For example, a library may choose to create a 10 day buffer for loans, so that loan requests can't have a Last Interest Date of less than 10 days from the borrowing request date. A shorter buffer period may be selected for copy requests. Flexibility in setting the buffer period should be provided to the Library. (This is exactly how this works in Relais ILL.)

    ISSUE: Quite a few of our borrowing requests are getting cancelled automatically by Alma, because people are setting a Last interest date of the same day or the next day. Unrealistic expectations are being created by the Last Interest Date. Yet, staff find it useful to know the Last Interest Date for borrowing requests where the patron indicates a date some time into the future.

    LOCATION: ILL request form, patron facing (e.g. in Primo VE).

    SOLUTION: Allow buffer periods to be implemented on the Last Interest Date. For example, a library may choose to create a 10 day buffer for… more

    9 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

12. Marine Corps University Press ebooks and journals

    Add Marine Corps University Press open access ebooks and the following journal titles to the Community Zone:

    Journal of Advanced Military Studies: JAMS
    Marine Corps History
    International Perspectives on Military Education: IPME
    China: Military Studies Review
    MCU Insights
    Expeditions with MCUP

    The starting URL is https://www.usmcu.edu/MCUPress/

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

13. Improve Library Only Note field in reading lists

    We would like to propose the addition of the Library-only note field in Alma to the panel on the right side of the reading list page. We would like to propose a modification to the Library Type note in Alma to improve workflow efficiency. We would like this note to appear in the Reading List Information panel or the panel where the 'view in Leganto' link can be found, rather than in the Notes tab. This should be editable directly from the panel to allow Library staff to add comments or further information related to a list (e.g. summary of communication with tutors, details on item availability, etc.). It would be like the "receiving note" field in POLs, but for reading lists.

    This change would streamline processes by making key information more visible and accessible, which would facilitate handovers and tracking of known issues.

    We would like to propose the addition of the Library-only note field in Alma to the panel on the right side of the reading list page. We would like to propose a modification to the Library Type note in Alma to improve workflow efficiency. We would like this note to appear in the Reading List Information panel or the panel where the 'view in Leganto' link can be found, rather than in the Notes tab. This should be editable directly from the panel to allow Library staff to add comments or further information related to a list (e.g. summary of… more

    55 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 →
    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. Consistent use of first ISBN in MARC field 020 for electronic resources in Alma

    Right now which ISBN is displayed/taken for export relating to e-resources is rather inconsistent in Alma:

    .) In the results list of an All Titles search the first ISBN of MARC field 020 is displayed and subsequently used for Excel export.
    .) In the results list of an Electronic Portfolio search the second ISBN of MARC field 020 is displayed (if there is one) and subsequently used for Excel export.
    .) In the portfolio list of an electronic collection the second ISBN of MARC field 020 is displayed (if there is one).
    .) On the portfolio tab of the Electronic Service Editor the print ISBN of MARC field 776 08 is displayed.
    .) When creating an extended export of an electronic collection the ISBNs are primarily taken from 776 08 MARC field and secondarily from MARC field 020. Three ISBNs are exported at most. Depending on how many ISBNs the record contains it could be 3 print ISBNs of MARC field 776 08, 2 print ISBNs of MARC field 776 08 and the last ISBN of MARC field 020, 1 print ISBN of MARC field 776 08 and the 2 last ISBNs of MARC field 020, 3 ISBNs of MARC field 020 ...

    Referring to the knowledge article on display priority (https://knowledge.exlibrisgroup.com/Alma/Knowledge_Articles/ISBN_(ISSN)_Display_Priority) we would like to note that priority of print ISBN over eISBN seems wrong. Instead we suggest to consistently take the first ISBN of MARC field 020 for display and export of e-resources.

    Right now which ISBN is displayed/taken for export relating to e-resources is rather inconsistent in Alma:

    .) In the results list of an All Titles search the first ISBN of MARC field 020 is displayed and subsequently used for Excel export.
    .) In the results list of an Electronic Portfolio search the second ISBN of MARC field 020 is displayed (if there is one) and subsequently used for Excel export.
    .) In the portfolio list of an electronic collection the second ISBN of MARC field 020 is displayed (if there is one).
    .) On the portfolio tab of the Electronic… more

    157 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. Enable local extensions on MARC 79X and 89X

    OCLC Bibliographic Formats and Standards sets out tags 79X (790-799) and 89X (896-899) as valid for local uses. These ranges should be available for network zone members to use as well. Adopting these ranges will allow catalogers to directly adapt records from WorldCat into a network and add local extensions without having to remap from the OCLC-supported field to a field in Alma, such as a 9XX.

    Catalogers primarily use these fields to enter details such as authors with local affiliations (e.g., current faculty members), dissertation advisors or members of dissertation committees, and the college within the institution supervising the dissertation. These are locally-relevant data that are not always relevant in the universal, shared record. Allowing their inclusion enables a network member to highlight what makes the record and information valuable to the institution.

    Moreover, the use of a local extension for this data helps protect the data from removal by other network members, and the data are protected if the network record is overlaid by a WorldCat record that doesn't retain that data.

    OCLC Bibliographic Formats and Standards sets out tags 79X (790-799) and 89X (896-899) as valid for local uses. These ranges should be available for network zone members to use as well. Adopting these ranges will allow catalogers to directly adapt records from WorldCat into a network and add local extensions without having to remap from the OCLC-supported field to a field in Alma, such as a 9XX.

    Catalogers primarily use these fields to enter details such as authors with local affiliations (e.g., current faculty members), dissertation advisors or members of dissertation committees, and the college within the institution supervising the… 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  ·  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

    Submit Rating

16. NZ and IZ environment: deletion of electronic collection in IZ should also delete records from NZ

    NZ and IZ environment: deletion of electronic collection in IZ should also delete records from NZ

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

17. royal society of chemistry gold 2026

    Please advise on the ETA on when the Royal Society of Chemistry Gold 2026 package will be loaded into the Community Zone for activation. The vendor rep I am in communication with has mentioned that they are currently in progress to send EXL their 2026 files. It would be great to know when to expect it to be available for activation. Thank you!

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

18. Add 245 subfield n to the letter XML node for title

    Many letters display the name of the title using the node notificationdata / physitem_display / title. This field contains a subset of subfields from the MARC field 245 to display the title of the work.

    We receive complains from our users regarding missing book title number in mostly textbooks. The missing number is available in the MARC field 245 subfield n and is an important part of the title. For example:
    245 10 |a Prisma Physik |n 1
    245 10 |a Deutsch |n Drei
    245 00 |a Prisma |n 1
    245 10 |a <<Die>> Sprachstarken |n 2 |b Deutsch für die Primarschule
    Currently, it is not possible to display the title including the subfield n.

    We would like to add the 245 subfield n right after the subfield a in the XML node notificationdata/physitem_display/title in letters. If the XML structure is different in each letter and you would have to adapt each letter, then please prioritize the On Hold Shelf Letter.

    Many letters display the name of the title using the node notificationdata / physitem_display / title. This field contains a subset of subfields from the MARC field 245 to display the title of the work.

    We receive complains from our users regarding missing book title number in mostly textbooks. The missing number is available in the MARC field 245 subfield n and is an important part of the title. For example:
    245 10 |a Prisma Physik |n 1
    245 10 |a Deutsch |n Drei
    245 00 |a Prisma |n 1
    245 10 |a <<Die>> Sprachstarken |n 2 |b… 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…)
    0 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

    Submit Rating

19. Sending On Hold Shelf Letter

    When scanning a barcode in Fullfilment - Checkout/Checkin – Returns items
    • Printing the Ful Resource Request Slip Letter
    • Change of document status in “Hold shelf”

    But no print On Hold Shelf Letter

    The operator can place the request on the reservation shelf but the reader is not notified

    Can the action “Returns items trigger the printing of the letter “On Hold Shelf Letter” ?

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

20. Any change to a role, or addition of a role, or replacement of a role, should be called out in release notes in a separate (or additional) s

    Any change to a role, or addition of a role, or replacement of a role, should be called out in release notes in a separate (or additional) section of the release notes.

    The reason for this need: Larger institutions have large numbers of Alma using staff to manage, oftentimes including student workers. It is important for Alma system administrators to have prompt awareness of changes to roles in order to make any necessary changes to staff accounts, profiles, etc. in order to maintain the security and integrity of patron data, cataloging data, norm rules, and the like.

    Having changes of these nature given prominence in release notes, rather than buried within sections of a long set of release notes, will assist system administrators with maintaining appropriate access to Alma.

    Any change to a role, or addition of a role, or replacement of a role, should be called out in release notes in a separate (or additional) section of the release notes.

    The reason for this need: Larger institutions have large numbers of Alma using staff to manage, oftentimes including student workers. It is important for Alma system administrators to have prompt awareness of changes to roles in order to make any necessary changes to staff accounts, profiles, etc. in order to maintain the security and integrity of patron data, cataloging data, norm rules, and the like.

    Having changes of… more

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