1730 results found

1. Save certain subfields from being overwritten via F3 and PTC

   When linking names, subjects etc. from authority files in various BIB fields, some cataloguing conventions require giving additional information in certain cases.

   One example for such a requirement, stemming from the German speaking countries, is to add the time and place of an auction when linking to the genre/form term “auction catalogs” in BIB field 655 (see attached screenshot). This additional information is, of course, specific for each BIB record and must not be overwritten or deleted, if at a later point in time either PTC processes said BIB record or a colleague invokes the F3 functionality.

   Since different subfields might be used for various types of additional information, based on the field number and the cataloguing tradition and/or authority file linked to, it would be sensible to allow to define specific subfields to be exempt based on the field number, but also the authority file in use ($2).

   When linking names, subjects etc. from authority files in various BIB fields, some cataloguing conventions require giving additional information in certain cases.

   One example for such a requirement, stemming from the German speaking countries, is to add the time and place of an auction when linking to the genre/form term “auction catalogs” in BIB field 655 (see attached screenshot). This additional information is, of course, specific for each BIB record and must not be overwritten or deleted, if at a later point in time either PTC processes said BIB record or a colleague invokes the F3 functionality.

   Since different subfields… more

   •  

   259 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…)
   9 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
   AdminErez Shabo (Senior Product Owner, Ex Libris) responded

   Hello everyone, for those who raised comments about the correction of 830 $v, could you please provide a detailed, step-by-step explanation of the scenario in which this subfield gets overwritten?

2. Contributed collections - a Report to Contributor instead of Report to Ex Libris

   There are many collections now that are contributed by the community. Sometimes there are errors within them and as it is now, there is no way to report that and get the linking problem (for an example) fixed and the issues can be so many that a deactivation is necessary, but then the collection becomes dead and just clutter KB. My suggestion is that when a institution contributes a collection, a mandatory field is added to the workflow of contributing. This field contains an email address. That email address is then incorporated into a button so you can report to Contributor instead of the button that is there now Report to ExLibris.

   This idea has been put forward before: Email CZ Contributor ... but it's a growing problem.

   There are many collections now that are contributed by the community. Sometimes there are errors within them and as it is now, there is no way to report that and get the linking problem (for an example) fixed and the issues can be so many that a deactivation is necessary, but then the collection becomes dead and just clutter KB. My suggestion is that when a institution contributes a collection, a mandatory field is added to the workflow of contributing. This field contains an email address. That email address is then incorporated into a button so you can report to… 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 - 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

3. Wikidata URIs

   We request that Wikidata be maintained within Alma as an authority vocabulary source. This functionality should include the ability to search against Wikidata as part of the Metadata Editor F3 linked data enrichment function. Cataloguers should be able to enrich bibliographic records by manually selecting the authority to apply the corresponding Wikidata URI to a name heading. This is useful for non-Library of Congress cataloguers and for those with Special Collections and archiving cataloguing responsibilities to use a more agile and international authority source in our cataloguing.

   68 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  ·  Linked Data  ·  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. Allow customers to select multiple retention reasons for Item records.

   Allow customers to select multiple retention reasons for Item records.

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

   1. Institutional last copy

   2. Faculty publication

   3. Rare

   4. Committed to some Shared Print program

   5. Digitized material

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

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

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

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

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

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

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

   Allow customers to select multiple retention reasons for Item records.

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

   1. Institutional last copy

   2. Faculty publication

   3. Rare

   4. Committed to some Shared Print program

   5. Digitized material

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

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

5. Reading Lists in the Task List Customise Alma task list (tasks requiring your attention) to match all our reading list statuses

   As Acquisitions & Reading Lists Manager I would like to customise the Alma task list (tasks requiring your attention) to help the reading list team manage the reading list workflow as using facets is a time-consuming long way round to find the list categories each time.

   Alma task list (tasks requiring your attention), section Reading lists, we would like to customise this list of tasks or add all reading list statuses each Library may have.

   We have reading lists with status other than Unassigned - processing, complete, reading for processing.

   We have 'updated' and 'core done' to help us manage the workflow.

   Currently the options available for Reading Lists in the Task List are:

   Reading List - Unassigned

   Reading List - Unassigned - complete

   Reading List - Unassigned - processing

   Reading List - Unassigned - reading for processing

   Reading List - Assigned to Me - reading for processing

   Reading List - Assigned to Me - List with new note

   Reading List - Unassigned - List with new note

   As Acquisitions & Reading Lists Manager I would like to customise the Alma task list (tasks requiring your attention) to help the reading list team manage the reading list workflow as using facets is a time-consuming long way round to find the list categories each time.

   Alma task list (tasks requiring your attention), section Reading lists, we would like to customise this list of tasks or add all reading list statuses each Library may have.

   We have reading lists with status other than Unassigned - processing, complete, reading for processing.

   We have 'updated' and 'core done' to help us manage… more

   42 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

6. Add Resource Sharing Partner Setting for ILLiad Cleared Status

   When a library creates a resource sharing partner for ILLiad and checks the Create User in ILLiad box, Alma does not pass a Cleared value in the CreateUser ILLiad API call. This means all ILLiad user records created by Alma need to be manually cleared. Please add a new setting to the ILLiad resource sharing partner type that allows libraries to select a Cleared value of either "No" or "New".

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

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

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

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

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

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

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

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

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

   48 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

8. Add function to monitor broken display logic rules

   When the name of a collection/interface/service used in a rule changes the rule quietly breaks. The only way in Alma to find out it's broken is to open the specific rule in edit mode, where it says "not listed" next to the changed collection/interface/service. There is no indication in the list of rules and you are not notified when a rule breaks. We have a long list of rules in use so it's difficult to keep track of the broken rules. It would be useful to be notified when a rule breaks or to have a way of monitoring broken display logic rules better.

   When the name of a collection/interface/service used in a rule changes the rule quietly breaks. The only way in Alma to find out it's broken is to open the specific rule in edit mode, where it says "not listed" next to the changed collection/interface/service. There is no indication in the list of rules and you are not notified when a rule breaks. We have a long list of rules in use so it's difficult to keep track of the broken rules. It would be useful to be notified when a rule breaks or to have a way of monitoring broken… more

   56 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

9. Expand SIP2 message support to include patron birth date

   Currently, Alma’s implementation of the SIP2 protocol uses only a limited subset of the available data fields. This restricts the potential of SIP2 integrations with self-check machines and other automated systems.

   For example, patron age or birth date information is not transmitted via SIP2 messages. As a result, self-check units cannot automatically block the checkout of restricted materials (e.g., DVDs or other items not permitted for users under 16).

   We propose that Alma extend its SIP2 message support to include additional patron details such as birth date and/or age

   This enhancement would enable safer and more autonomous self-service environments, particularly in low-staffed libraries, while ensuring compliance with age-based borrowing restrictions and institutional policies.

   Currently, Alma’s implementation of the SIP2 protocol uses only a limited subset of the available data fields. This restricts the potential of SIP2 integrations with self-check machines and other automated systems.

   For example, patron age or birth date information is not transmitted via SIP2 messages. As a result, self-check units cannot automatically block the checkout of restricted materials (e.g., DVDs or other items not permitted for users under 16).

   We propose that Alma extend its SIP2 message support to include additional patron details such as birth date and/or age

   This enhancement would enable safer and more autonomous self-service environments, particularly… more

   59 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

10. Increase the number of available facets for all POL searching

    All aspects of the POL should be available as facets, assuming they appear sufficiently frequently in a set of results. Most notably, all 5 reporting code fields should be available as facets.
    Additionally, other sources of POL lists, such as the Alma Vendor Record should offer all of the same faceting functionality, including the ability to customize which facets are visible.

    45 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

11. Improve cookies on Alma and other Clarivate sites

    Alma-specific:
    * Re-configure the OneTrust settings so that performance cookies default to off
    * Targeting cookies should not be present at all (my Alma usage is useless to advertisers and if it's not then that's really concerning!) but if you must have them then these should also default to off.
    * Leganto and other systems that are configured in Alma should respect any opt-out settings the user has already specified on the Alma site (and vice versa)

    Clarivate-wide:
    * Someone should have a thorough review of OneTrust configurations across the whole conglomerate to make all optional cookies default to off, remove unnecessary cookies (ie social media cookies and especially targeting cookies), and make more Clarivate sites respect user preferences as expressed on other Clarivate sites.

    Background - current situation:
    Clarivate has a vast range of library/research related websites. They all use OneTrust to manage cookies, but are almost all configured separately (so even after you've set your preferences on one site, other sites don't apply the same preferences) and differently (so some sites default to optional cookies off while others default to on).

    The best site is ProQuest Support. This has a lot of cookies (Functional, Targeting, Social Media, and Performance) but they all default to off, so you can open it up and quickly confirm that. Moreover if you then go to ProQuest Central, it appears to remember and respect those same preferences.

    Primo (both VE and NDE) doesn't have a cookie banner at all. I hope this means that it doesn't use cookies? (Though if Primo can manage without cookies I wonder why the other sites can't.)

    Other sites default to having cookies on: IdeaExchange only has Performance cookies, while Knowledge Centre, Developer Network, Alma, Leganto, and Web of Science all have both Performance Cookies and Targeting Cookies.

    This means that if, for example, you've cleared your browser cache for some reason, then when you open Alma, Leganto, Knowledge Centre, Developer Network, ProQuest Support, and IdeaExchange, every single one of these sites separately wants you to manage your cookies. Also if you start on ProQuest Support where cookies default to 'off' you may assume the same is true on the other sites, and try to save time by clicking 'confirm my choices' without clicking every individual tab first, not realising that this is actually setting them to 'on'.

    Alma-specific:
    * Re-configure the OneTrust settings so that performance cookies default to off
    * Targeting cookies should not be present at all (my Alma usage is useless to advertisers and if it's not then that's really concerning!) but if you must have them then these should also default to off.
    * Leganto and other systems that are configured in Alma should respect any opt-out settings the user has already specified on the Alma site (and vice versa)

    Clarivate-wide:
    * Someone should have a thorough review of OneTrust configurations across the whole conglomerate to make all optional cookies default to off,… more

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

    Submit Rating

12. Predicted Items - Add columns in Metadata overview

    When opening predicted items in the Metadata Editor, the "Predicted Items" pop-up window appears. It would be very useful if the following columns could be added to the overview presented in this window.

    Currently, the following columns are shown:
    - Description
    - Status
    - Expected arrival date

    Please add:
    - First level of enumeration (= Enumeration A in the physical item editor)
    - Second level of enumeration (= Enumeration B)
    - First level of chonology (= Chronology I)
    - Second level of chronology (= Chronology J)

    This addition would make it easier to verify whether all relevant fields are correctly filled by the pattern used in MARC 853.

    Thank you

    When opening predicted items in the Metadata Editor, the "Predicted Items" pop-up window appears. It would be very useful if the following columns could be added to the overview presented in this window.

    Currently, the following columns are shown:
    - Description
    - Status
    - Expected arrival date

    Please add:
    - First level of enumeration (= Enumeration A in the physical item editor)
    - Second level of enumeration (= Enumeration B)
    - First level of chonology (= Chronology I)
    - Second level of chronology (= Chronology J)

    This addition would make it easier to verify whether all relevant fields are correctly… more

    •  

    50 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Resource Management - 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
    AdminLiza Voloshin (Product Owner, Alma Resource Management, Ex Libris) responded

    Hi all,

    Please note that this idea was mistakenly closed. It has now been reopened, and we apologize for any inconvenience caused.

13. Browse Shelf Listing Call Numbers - 852 $$j

    Under the current design, browsing shelf listing by 852 $$j is not a supported feature in Alma.

    Example:
    852 18 $$b SBG $$c 91 $$8 222 B $$h 22/Z 1244 $$= l $$9 00 $$j 22/Hbl E 600 $$9 09 $$x DE-22

    For the holdings' field 852 subfields $$h 22/Z 1244 and $$j 22/Hbl E 600, the holdings call number “22/Z 1244 22/Hbl E 600” will appear only when the browse term is “22/Z 1244 22/Hbl E 600” or “22/Z 1244,” but not when the browse term is “22/Hbl E 600”.

    We need a 'Browse Shelf Listing' that lists ALL existing call numbers completely and in the correct sequence, regardless of whether they are call numbers from the holding level or from the item level and regardless of whether they can be found in the holdings' field 852 $$h or in 852 $$j.

    This function is essential to prevent call numbers from being assigned or recorded twice. The selection 'All' within the 'Browse Shelf Listing' should fulfill exactly this requirement. However, the 'All' selection actually does not list all existing call numbers. This browsing logic does not meet all our needs.

    Under the current design, browsing shelf listing by 852 $$j is not a supported feature in Alma.

    Example:
    852 18 $$b SBG $$c 91 $$8 222 B $$h 22/Z 1244 $$= l $$9 00 $$j 22/Hbl E 600 $$9 09 $$x DE-22

    For the holdings' field 852 subfields $$h 22/Z 1244 and $$j 22/Hbl E 600, the holdings call number “22/Z 1244 22/Hbl E 600” will appear only when the browse term is “22/Z 1244 22/Hbl E 600” or “22/Z 1244,” but not when the browse term is “22/Hbl E 600”.

    We need a 'Browse Shelf Listing' that lists ALL… more

    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…)
    1 comment  ·  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

14. acquisition vendor analytics expansion: all URLs

    We would like to see more complete vendor information in Analytics in general, however this specific request is for inclusion of all URL types, along with both their description and note fields.

    The use case is that we are hindered from fully using all the fields within Alma when we cannot run reports on that information in order to back it up. The backup is necessary due to the lack of an "are you sure" popup for the Delete action. Also, administrative and statistics login information needs to be available to all acquisitions and e-resources staff, however it needs to be backed up in case of accidental changes. And since vendors don't have a history tab, again, the alternative would be to run a regular report for backup purposes.

    We would like to see more complete vendor information in Analytics in general, however this specific request is for inclusion of all URL types, along with both their description and note fields.

    The use case is that we are hindered from fully using all the fields within Alma when we cannot run reports on that information in order to back it up. The backup is necessary due to the lack of an "are you sure" popup for the Delete action. Also, administrative and statistics login information needs to be available to all acquisitions and e-resources staff, however it needs to… more

    18 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  ·  Analytics  ·  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. Add General Electronic Services information to Analytics

    In General Electronic Services, we have four different services for article requests, four different services for book requests, and five different services for book chapter requests, all developed over the years to address provider idiosyncrasies. Each group of services provides the same link to the user, e.g. the article request links all display "Get this PDF".

    Our Interlibrary Services unit has the product delivery statistics, but I would really find it helpful to know how many clicks each of our General Electronic Services gets. It would help with service and link maintenance and I expect with troubleshooting, since it would allow for the simultaneous viewing of a lot of information.

    Please add the General Electronic Services to Analytics, with all fields:
    Active
    Service Code
    Service Name
    Service Description
    Public Name
    Public Note
    DD/ILL Service
    Display Location
    URL Template
    Enable without login
    Disable Service
    All Service Availability Rules

    Thank you for considering!

    In General Electronic Services, we have four different services for article requests, four different services for book requests, and five different services for book chapter requests, all developed over the years to address provider idiosyncrasies. Each group of services provides the same link to the user, e.g. the article request links all display "Get this PDF".

    Our Interlibrary Services unit has the product delivery statistics, but I would really find it helpful to know how many clicks each of our General Electronic Services gets. It would help with service and link maintenance and I expect with troubleshooting, since it would… more

    67 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  ·  Analytics  ·  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. Community-Managed electronic collections: Add several portfolios to one title

    In Community-Managed electronic collections, it is not possible to contribute a second portfolio to the same title that is pointing to a different URL. Use case: Both URLs are valid, both contain copies (in part) of the journal. It would be nice, if the contribution only gets blocked, if the URL of the newly contributed portfolio is identical to the existing one.

    34 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

17. Add reminders to Analytics

    The function reminders is only partly useful at the moment. Improve it by adding reminders to Analytics. Creating and scheduling reports on reminders by type, status, text and so on would be very helpful for us.

    32 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Analytics  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Allow for an authority file to be addressed by different codes in $2 of various BIB fields

    In Alma the authority file, a subject or term stems from, is defined by the content of $2 in various 6XX fields. This code controls the F3 functionality, as well as the linking process and the various jobs like PTC. Each and every authority file is addressed by one specific code.

    In the German speaking countries we use an integrated authority file (GND), which amongst names and subjects, also includes genre/form terms. For historical reasons the genre/form terms in BIB field 655 are marked with the official LoC /MARC Genre/Form Code and Term Source Codes “gnd-content” and “gnd-carrier” in $2, while the terms are, as the code suggests, actually a subset of our integrated authority file “gnd”. The same goes for notated music terms in BIB field 348. These too are a subset of our integrated authority file and are marked by the official LoC /MARC code “gnd-music” in $2.

    Alma currently does not allow to link the above mentioned terms to said authority file, because the content of $2 does not exactly match the code for the authority file, which is “gnd”. This problem could be solved by allowing for different codes in $2 to address one and the same authority file.

    In Alma the authority file, a subject or term stems from, is defined by the content of $2 in various 6XX fields. This code controls the F3 functionality, as well as the linking process and the various jobs like PTC. Each and every authority file is addressed by one specific code.

    In the German speaking countries we use an integrated authority file (GND), which amongst names and subjects, also includes genre/form terms. For historical reasons the genre/form terms in BIB field 655 are marked with the official LoC /MARC Genre/Form Code and Term Source Codes “gnd-content” and “gnd-carrier” in $2,… more

    145 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

19. Prevent items to be loaned immediately when they are returned at a SIP2 Self check machine and have a Rapido personal delivery request

    When a loaned item is returned at a SIP2 Self check machine and has a Rapido personal delivery request, the item is automatically loaned to the patron (and sorted to a request bin). Requested items then are scanned in at a circulation desk for further processing. In case of a personal delivery request, the item is immediately returned and marked for reshelving. Librarians do not see that there was a request (and a short loan).

    Previously we handled personal delivery requests via a GetIt request. The effect was the same, but we were able to prevent this behaviour by de-selecting «Supports personal delivery» in the associated circulation desk. Thie way the item wasn’t returned immediately, but transferred to a circulation desk where personal delivery requests are supported. A scan in loan the item to the patron.

    What we need is a similar configuration that prevents returns in case of a Rapido personal delivery request.

    PS: Setting 'Prevent Requested Items Check In' to 'Yes' in the Self Check integration profile (and give users a message like 'Item is requested and must be checked in at the circulation desk' is not an option. This would change the behaviour of most of the other requested items (e.g. pickup locally) which are behaving fine. And it would be no solution for libraries without served circulation desks or – as in our case – with 7/24 Self check machines outside the library.

    When a loaned item is returned at a SIP2 Self check machine and has a Rapido personal delivery request, the item is automatically loaned to the patron (and sorted to a request bin). Requested items then are scanned in at a circulation desk for further processing. In case of a personal delivery request, the item is immediately returned and marked for reshelving. Librarians do not see that there was a request (and a short loan).

    Previously we handled personal delivery requests via a GetIt request. The effect was the same, but we were able to prevent this behaviour by de-selecting… more

    46 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Fulfillment - Requests  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Pop-up window with information about blocks and reader's fees when create a request

    It would be helpful if, when filling out the user request form in Alma, a pop-up window with information about the users's blocks and financial obligations appeared when their card number was entered.
    A pop-up window exactly like the one that opens when you open a patron's account using the “Manage Patron Services” option.

    This solution would allow the users to be immediately informed of their obligations and avoid being sent from one station to another.

    For example: In our library, fines can only be paid at the station on the ground floor. If the employee at that desk orders items for the patron to be picked up on the third floor and does not notice that the reader has a fine, the reader will go to the third floor. There, the loan will be blocked and they will have to return to the ground floor and then back to the third floor to pick up the items they ordered.

    It would be helpful if, when filling out the user request form in Alma, a pop-up window with information about the users's blocks and financial obligations appeared when their card number was entered.
    A pop-up window exactly like the one that opens when you open a patron's account using the “Manage Patron Services” option.

    This solution would allow the users to be immediately informed of their obligations and avoid being sent from one station to another.

    For example: In our library, fines can only be paid at the station on the ground floor. If the employee at that desk orders… 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  ·  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