Skip to content

Alma

Your feedback matters to us. Help us improve Alma by telling us what you’d like to see using the message areas below. You can also can support something already posted.

We would love to be able to respond to every idea that is submitted, but this is not feasible. We are, however, committed to responding to the most popular ideas—those that have received the most points.

For more information please review our FAQ and guidelines. Thank you.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

116 results found

  1. Ability to run a job on a set from the Manage Sets screen

    Currently we need to create a set in the Manage Sets area then go to "Run a Job", select the job to run and then select the set.

    Wouldn't it be great if you could go to Manage Sets then click on "Actions" for a particular set, then choose "Run a Job". You could then be prompted to choose the job to run but you wouldn't need to go through the additional step of choosing the set (and you wouldn't have to exit the sets screen to go to the "Run a job" screen). And only the jobs that can…

    47 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. LC call number search and index

    LC call number should support indexing all valid MARC fields as mentioned in http://www.loc.gov/marc/bibliographic/bd050.html and not only 050$a or local 090$a fields.
    It should index also $b and than enable to search for full LC call number, of course this should reflects also in the holdings level (i.e. $h,$i etc)

    25 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Thank you for submitting this idea. To be sure we fully understand the request, could you please specify which other MARC fields other than 050 and 090 you are asking to be added to the LC call number index? Thank you.

  3. Add Visual Materials to Quick Cataloging citation types options

    Our library uses the Quick Cataloging tool/interface to create records for materials in course reserves. Currently, the only options for citation types are books and articles. We have DVDs professors place on reserve. When records for DVDs are created, they are created on a record type for book. It would be great to choose citation type "visual materials" at the point of creating the bib record via the Quick Cataloging tool.

    52 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Add a safety feature to Delete Bibliographic Record Job to include option "Do not delete if ANY PO Line is attached"

    Currently there is only an option to protect Active PO Lines with this job. Acquisitions staff often place orders on bib records representing multi-volume sets. Cataloging staff then decided to use individual bib records for each volume and want to delete the set record and move POLs to the individual records. It would be very helpful to have this feature in place to protect order information.

    26 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Add an Owning Library facet in Repository searches

    Can we please have the owning library added as a facet in repository searches. At the moment it only appears in Acquisitions based searches as we have four libraries making up our collections this facet would also be very useful in the general searching

    22 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Linking bib records based on 830 $x should be optional

    Alma currently links bib records based on the presence of the ISSN in the 830 $x. This causes a terribly confusing display in Primo and Alma and is prone to messing up requests. This should be an optional "feature" and not automatically enabled. We do have the option to turn off all related records, but if we use that, we lose all our boundwith relations.

    We should not have to delete a valid MARC subfield (830 $x) in order to prevent related holdings record displaying in Alma and Primo.

    68 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Default search option setting for external resources

    MD editor > Tools > Search external resources

    Search options for external resources such as title, creator, isbn, system number and year of publication are automatically filled in from a bib record. This make us to delete fields manually and spend time. It would be great to set search options at the institution level or individually.

    95 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Ability to create a chosen quantity of predictions

    As someone who manages serial subscriptions, I would like the ability to choose the quantity of predictions I create for any given holdings record. This would allow for quicker navigation of list of items, and reduce the number of inaccurate predictions.

    It is not always desired to predict an entire year’s worth of predictions (which currently is the only option). Depending on the publishing frequency and the number of copies of a subscription, we can have 11 pages of predictions in a list of items, in addition to the received items. This greatly increases the amount of clicking needed at…

    164 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Normalisation rules that apply to holdings using information from Bib record, and vice versa

    Have normalisation rules that are applied to holdings able to use information from the bib record. This would allow more complex holdings and call numbers to be automatically generated more easily than using the current call number system as a workaround.

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. import profiles -- need the option to leave suppression codes "as is"

    When creating an import profile, the “set management tags” option is to either suppress record/s from publish/delivery, or to not suppress. This is for the entire file.

    We need a third option to leave the existing suppress status unchanged for replaced and merged records. (We had this option in Voyager, and it worked well)

    Rational: All GPO weekly brief Marcive records are loaded suppressed. When the monthly bib records overlay the weekly brief records, the suppress status needs to remain as is. “If” the bib record is suppressed, the cataloger will unsuppress at the point of cataloging

    30 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Improve ME Browse Call Numbers Tool

    When editing a holding record in the Metadata Editor, the Browse Call Number tool shows the call number from the current holding record in a shelf list display. However, the resulting list starts with the call number in your holding record and shows the following call numbers. What we need is to see the call numbers both before and after the one we're working on. Request the list show at least 2-3 call number prior to the one we're working on, plus those following.

    42 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Show 866 holdings field text on item records screen, so don't have to go back and forth to check holdings dates.

    Presently from the list of item records, we have to click on "Holdings" to see the 866 summary holdings for vol & dates. It would be very helpful for the 866 holdings to be visible on the item record screen.

    15 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Customize Alma search indexes

    We would like to customize the search indexes in Alma for all MARC21 fields (not just localized fields). For instance, in the Alma advanced search > all titles > "Title" > we would like to change to "245 (Title)" to make it easier to identify the MARC21 field we want to search.

    91 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Enhance Advanced Search to allow regular expressions

    Allow the matching of regular expressions as one of the criteria to perform an advanced search. This would be a much more powerful and precise method for gathering sets.

    46 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Ability to suppress licenses from discovery

    Sometimes, licenses have confidentiality clauses, so we can't show them in Primo, but right now, it is an all or nothing prospect. it would be great if a checkbox on the record could suppress a confidential license from showing up in Discovery.

    115 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. 11 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
1 2 3 4 6 Next →
  • Don't see your idea?

Feedback and Knowledge Base