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

259 results found

  1. Allow Libraries to Set Default Action for Deleting Bib Records

    Currently, the default action for handling a bib record when deleting the associated item/portfolio is set to "Do Nothing." In our library, we almost universally choose to delete the bib record, which means it takes two extra clicks to perform each delete operation. Could this setting be made configurable so that a library could choose which operation to set as the default, without losing the choice of other options in the dropdown? Two extra clicks per record adds up to a lot of time when deleting large numbers of records!

    3 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. rerun Overlap and Collection Analysis

    There are certain reports that I would like to run in Overlap and Collection Analysis periodically. It would be helpful if I could rerun a past report instead of having to enter all the criteria every time.

    3 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)
  3. Preferred Term Correction job needs option to turn off the reordering of subfield URIs $$0

    We have implemented URIs into our bib records, but found that the Preferred Term Correction job is reordering the subfield $$0, where URIs are automatically clumped together at the end of the subject string and are no longer associated with the term. Even though the current best practice is for only one URI to be associated with the subject string and for it to be last in order, most subject headings with multiple subfields do not yet have a single identifier (URI) assigned to the entire subject string. There should be an option for the reordering to be turned off…

    3 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. 490's accompanying 830 field display

    When you search titles, Alma currently displays 830 in the Series field when traced (490 with a 1 indicator).
    However, 830 depending on 490 means that 490 takes precedence.

    It must be said that the trace which 830 is, is supposed to be used to be able to view 490 by the cataloguers and librarians.
    But currently, when using the trace, 490 is not displayed.

    When you have a 490 field with several $a, you write several 830s.
    For example ISBN: 9784043675043.
    245 00 $$a Tō enmei.
    490 1# $$a Kadokawa bunko ; $$v 13617. $$a Kadokawa sofia bunko ;…

    3 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. Additional Input Parameter Options for Item Description Templates

    When creating an Item Description Template it would be very helpful to include additional Input Parameter options such as Permanent Physical Location. We utilize different description orders on our labels dependent upon the different locations items are shelved and there doesn't seem to be a way to distinguish the differing order with the current parameter options. More input parameter options would allow for greater individual institutional nuances and their unique practices.

    For example, I could have an unclassed serial shelved in "serials" with material type issue and I want the description to display as:
    v.{EnumA} no.{EnumB} {ChronI} {ChronJ}
    I could…

    3 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. Local Authority Automation and Workflow

    Currently, Alma requires quite a bit of manual intervention when creating local authority records and linking them to the relevant records in the catalog. In order to relink an authority controlled field (ie. 1XX, 6XX, and 7XX) someone from the library must go through and change the second indicators from 0 to 7 and add a $2 with the local authority profile code. This can be done using normalization rules but it still must be done manually. There are no scheduled jobs that will do this.

    An example might be helpful to both show the problem and a possible solution.

    3 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. automated import profiles - create log file with useful information if process fails

    We are finding Alma less than helpful in cases where the automated download fails due to a parsing error. Apart from actually creating a log file as suggested here, there would be other ways to improve this experience.

    This is what currently happens:
    - for automated import profiles, no log file is created when the process fails, the emailed report simply states that the import failed, there is nowhere in alma where I could find any further information
    - because of this, we then need to try and run the import manually, so we can see what the issue is…

    3 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. Show all holdings in export list in column "availability"

    The results list exportet to excel shows only the first three to four holdings followed by “and others”.
    So you do not get the complete number/information about the holdings of the record.

    3 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. Allow form editing of Metadata Configuration profiles in addition to Extension files

    The metadata configuration profiles are currently only editable by uploading XML files, which become invisible upon upload. This can become a nuisance if a library wants to make small additions to existing fields, or wants to add multiple new fields with numerous subfield/indicator definitions. It would be much easier if new values could be added using a form within Alma, via an "add row" link at the top of each page. For example, in the MARC21 bibliographic profile, an "add row" button could add a new MARC field and definition. Within each field would be additional "add row" buttons for…

    3 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. Add option to import records as standalone upon multi-match

    In the "Automatic Multi-Match Handling" section, under the option "Choose a conclusive action in case the above selected criteria result in multiple records," I'd like to be able to select "skip and import record as standalone." I still want the record, but it doesn't know which record I plan to overlay. So, I must manually resolve the issue. It's an extra step to go back into the job's history, download the record it rejected, and reload it as standalone.

    3 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. Add 2FA for Import profiles

    Recent changes to our digital preservation system mean that two factor authentication is now required for API access to the system. This includes OAI Harvest tools.

    At present there is no field in the Alma/Primo import profile template I can add the authentication key required to harvest data from our preservation system.

    Is it possible to add such a field to the Alma import authentication template? This would benefit not only us, but others who have links to external systems which require two factor authentication.

    Information about the change as it relates to us can be found in the following…

    3 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. Add notes or internal description field to collections

    Currently the only place to put information into a (not electronic) collection is the Description, which is visible to the public. It would be very useful to have an internal note or internal description field where we can put in information such as why a collection was created, who wanted it, what criteria to use when adding titles, etc.

    3 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. Publish the electronic collection name so that it can be made displayable and/or searchable by configuring Primo BO normalisation rules

    Publish the electronic collection name so that it can be made displayable and/or searchable by configuring Primo BO normalisation rules.

    2 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. repository search sort by collection name (asc/desc)

    Ability to sort searches in the repository by collection name (ascending & descending) when searching by titles & portfolios. This sort feature is only available right now when searching for electronic collections; this feature, when turned on, applies to the other searches you can do (i.e. electronic portfolios) but only if one searches by collection first. Would like the sort feature to be available for all searches in the repository, not just for collections.

    2 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. Search package titles in "All titles"

    We would like to search package titles in the index "All titles". This is not possible in the moment.

    2 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. Ability to create a Titles set from a logical physical item set

    Currently it's not possible to create a Titles set from a logical Physical Items set. Instead, one must first create an itemized set from the logical set, then create a Titles set. We would love to see the option to create a Titles set from a logical physical items set.

    2 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)
  17. View It in Alma for physical resources

    In Aleph we were able to CTRL + O and see the physical item's record in the OPAC immediately. Now our metadata staff have to wait until the Alma pipe to Primo has run to view their record in Primo. Would it be possible to add a View It, like in the case for e-resources, for physical resources also.

    2 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)
  18. [Alma] - export items job - csv format - always add / embed in double quotes as text qualifiers / delimiters

    Right now in Alma, when running a job to export a set of Items in csv format, double quotes are added only to values containing commas (see attached example).
    Which is not wrong at all, but it would be much better (e.g. for postprocessing the file in a text editor or using regex) if the double quotes were always added by default in the .csv format.
    For example, right now is.
    03149898,Machine à lettres,MeMo,Book,"Magnani, Julien",AM 22800
    but it would be much easier to process if it were:
    "03149898","Machine à lettres","MeMo","Book","Magnani, Julien","AM 22800".

    2 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)
  19. make OCLC delimiter (double dagger (ǂ)) invalid in Alma

    Please make the OCLC delimiter (double dagger (ǂ)) an invalid character in Alma. We all copy and paste information from Connexion. Often, people forget to change the double dagger to the double $$. Please make the double dagger invalid, and require the cataloger to replace with the proper character ($$) before they save the record. Other systems like Voyager make the cataloger replace the double dagger delimiter before they can save the record.

    2 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)
  20. Include prefixes in 035 repository search and creating set

    Currently, when we do a repository search on Other System Number (035) with an identifier including a prefix, e.g. (EBL)165125, Alma would ignore the prefix and only match the remaining part of the identifier. That would result in retrieving incorrect record, e.g. record with (PQKBTitleCode)TC0000165125 in 035.

    The same imprecise search also occurs when creating a set from a file with 035 field header. The prefixes are ignored and incorrect records are retrieved.

    We would like the repository search on other system number and creating set with 035 field header to perform precise searches including the prefixes on the identifiers.

    2 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)
  • Don't see your idea?

Feedback and Knowledge Base