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.

How can we improve Alma?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Include access information as part of the data that are published from Alma to Primo for Alma-D records

    We would like to have the possibility to include access information in the data that are published from Alma to Primo for Alma-D records (per representation).
    Use case:
    At this moment, we make the digitized content of all institutions searchable in the views of all institutions of the network.
    This is can be very useful for items that are freely available, including digitized heritage.
    However, it is inconvenient and confusing for items with restricted access, when the content can only be viewed by users of the institution.
    Yet the availability indication for these items is "Online access", because we cannot…

    121 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. Customisation of Alma patron deposits page

    We would like to have the ability to customise the Alma patron deposits page, including:
    - Logo + other branding elements eg. footer with University/Library details, link to privacy policy etc.
    - Access to the landing page html to include deposit instructions and/or embed video tutorials
    - Option to add links to help, contacts, policies for patron deposit
    - Option to include a chat widget
    - Css styling
    - Sign in options to mimic Primo (in our case we might want to use SAML + Alma login)

    25 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. Related Digital Record Support

    For physical and electronic records there is a support for "related records" functionality / analytic cataloging (represented by 773 MARC field).

    We suggest to add this important functionally to digital records, so that the digital representation will be displayed in the View-It section of the related record as well as in the View-It of the main record (just as it is done for physical records by inheriting the inventory to the related record).

    27 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. Do not publish to Primo bibliographic record if all its representations are inactive

    If a record does not include any material that the end-user can display or access, then it should not be searchable in Primo.
    For physical inventory, there is an option to enable the suppressBibWithSuppressedHol setting which means that if all physical holdings in a bib record are suppressed, then the bib record will automatically be suppressed from discovery.
    This idea asks to add similar option to digital content (Alma-D): when enabling the suppressBibWithSuppressedRep setting, any bib record that all its digital representations are inactive, will be automatically suppressed from discovery.

    34 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. Digital itemized sets

    Currently it is impossible to create an itemized set of digital titles/representations/files as the option of Rep ID header is not recognized by the system.

    45 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. Rights information in MARC records to display in Alma viewer

    1. Rights information for digital objects may be recorded in MARC fields:
    a. 540 (https://www.loc.gov/marc/bibliographic/bd540.html)
    b. 542 (https://www.loc.gov/marc/bibliographic/bd542.html)
    c. Possibly some other places too.
    There are only limited options in Configuring Delivery Profiles Metadata for MARC profile. - https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/030Fulfillment/080Configuring_Fulfillment/070Digital_Fulfillment?uxp=true#Configuring_Delivery_Profiles_Metadata There are no options to choose which MARC tags appear in the description area of the viewer.

    We would like to be able to configure the display of these fields in the Alma Viewer.

    19 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. Publish Alma-D to Google Scholar

    By now it is not possible to publish Alma-D (Bib/Representation/File) to google scholar. There should be an option to publish Alma-D to google scholar at least on a set- or collection level.

    5 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. Support best practice for CC licence for digital titles/files

    To meet best practice we currently have to encode html into either a non-compliant MARC tag, or into a dc:rights field in Dublin Core records.

    We would like to see a better for this linking to the licence to be accommodated. We should not have to put html inside fields. A method that works for both MARC and Dublin Core would be ideal.

    The copyright declarations are associated with access rules and apply to many records, whereas these rights statements need to be customised for individual records, potentially for individual representations eg. In a research data set, some files may…

    15 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. Short url in sharing Buttons Added To Alma Digital Viewers

    At the October 2018 release the following change was made "Social Network Sharing Buttons Added To Alma Digital Viewers". Now it would be a good idea to add the option to generate a "short url" for the records, since it generates a very long url for services such as twitter for example.
    Thanks

    6 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. Create or modify XMP, IPCT or Exif metadata of digital assets in batch

    The owner or copyright statement in the XMP, IPCT or Exif metadata of a digital object stored in Alma can change. If this happens, you need to export the digital Objects like PDFs or images change the XMP, IPCT or Exif metadata and reimport the assets. By consequence, the docid changes and permalinks to these images are not valid anymore.
    It would be useful, if Alma could create or modify XMP, IPCT or Exif metadata of digital assets stored in the AWS cloud in bulk.

    3 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. Add MMSID header when creating digital titlles sets

    Currently, when we import digital material records as digital representations which is digitized from the physical books, first, we usually create all titles set using the “MMSID”header, to put the physical titles into a collection. But only digital titles can run the withdraw digital representations job. So it would be very useful to add MMSID header when creating digital titles set. And then we can use this set to apply the withdraw digital representations job. Or add “all titles”content type in withdraw digital representations job instead.

    18 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. Display record format in search results and browse pages

    We catalogue Alma-D material in both MARC and DC formats.
    We would like an easy way to determine which format a record is in when viewing it from either an Alma results page or browsing through a collection.

    This could be done with the addition of the record format field to the brief record display.

    9 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. Selecting/deselecting multiple sets for OAI harvest

    The configuration of the digital collections import profile allows you to declare sets, but the only current options seem to be to harvest all sets or to harvest single sets individually. There's no way to CTRL-Click to include multiple sets.

    This CTRL-Click functionaity and/or set exclusion should be a feature request. For most collections, we have one or two sets that should be excluded and dozens that should not. Doing dozens of individual harvests is impractical.

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. Extension Indexing for Alma-D

    Publish the complete amazon S3 repository URL of a file contained as a digital object, so that Primo could fetch the data with a file splitter.

    18 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. Enhance reporting for digital import profiles to harvest remote repositories

    Currently the report generated after a digital import profile to harvest metadata from a remote repository has run is extremely minimal. It just states that a job "completed with errors", see attached file.

    I'd like to recommend 3 enhancements. The first is to provide more information about the errors. For example, the harvest failed because the records listed below are invalid. The second recommendation is to provide a maximum error threshold like what is currently available in Primo. Lastly, integrate an option to strip any HTML and escape invalid characters as part of an import profile normalization process.

    These enhancements…

    4 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. Reverse sort order option in ALMA for Digital Representation list displayed in Primo for a Bibliographic record

    If you attach several Digital Representations to one bibliographic record in ALMA, and each representation has one file attached, then all those Digital Representations (with their file) will be displayed in the U-Resolver display in Primo for the bibliographic record.
    In this scenario, there is currently no way in ALMA to alter the sort order of how the Digital Representations display in Primo. The default is alphabetical order, or numeric order. It would be useful to be able to choose reverse alphabetical or numeric order. This would allow a scenario where the year could be placed at the start of…

    11 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  • Don't see your idea?

Feedback and Knowledge Base