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

    124 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. Add Breadcrumbs (Collection Path) to Alma Viewer

    Like Hansel & Gretel, would be good for users to have a trail of breadcrumbs to follow home.

    That is option for Alma Viewer to display the context of the item (which collection the item belongs to if any) as defined by Alma Collections and published to Primo discovery collection lobby.

    This would enable the user, provided with a deep-link to an item in Alma Viewer, to browse related items (other items in the same collection) in Primo or return home where applicable.

    69 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. Free text input option for Rep Label in Global representation Changes job

    Currently there is no option to remove Rep Label or create a rule that can make it void on the "Global Representation Changes" job. Please provide with Free text input option for Rep Label in Global representation Changes job, like Public Note.

    66 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. All fields for Alma Digital MARC21 end user deposit form

    Currently the MARC21 form for deposit only support 245$a , $b , $c and 520$a
    However the Qualified Dublin Core form can choose from all DC fields.
    We would like the MARC21 Form to have the option to support all MARC fields. This would bring the MARC21 form functionality in parity with the DC Form functionality.

    A use case for this is the Alma Digital end user deposit functionality. Currently the minimal 4 MARC fields are not sufficient to capture the wealth of information we need for end user deposit. With more MARC 21 fields supported we could create very…

    58 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    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.

    52 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. Prevent Download Pictures (Alma Digital) when Download is not allowed

    Prevent Download Pictures (Alma Digital) when Download is not allowed

    When Access rights indicate to “Allow View” but not download, Alma viewer currently allows downloading the picture by “saving as”.
    The digital Viewer should prevent this option.

    43 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. 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.

    32 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. 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.

    28 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. 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.

    28 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. alma digital

    When our MARC metadata displays in the Alma Digital viewer, a semicolon is added in the format field where a space appears in our MARC record 300 field between subfields a and b.

    We have not encountered other fields where punctuation is added or changed between what we have entered into the Alma Metadata Editor and delivery, so we're not sure why this field has this problem.

    26 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. Make Public Note of a Representation Translatable

    The public note of a representation is not translatable. This would be useful for following use cases:


    • The library wants to offer high-resolution digital reproductions of individual files from representations on demand.

    • The library wants to comment on the quality of files from a representations (eg. not OCRed).

    • The library wants to inform, that the digital files does not contain complete content, etc.

    By now following components in relation with digital content are translatable :


    • Collection name and description

    • Copyright declarations

    • The denied note in the access right policy

    It would offer a more streamline experience to discover digital content,…

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. 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…

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. Enable provenance ID field in batch ingest for digital representations

    In the November 2019 release new fields (Provenance ID and File provenance ID) were added for digital representations and files.

    These fields are not supported in the batch ingest processes.

    It should be possible for institutions to specify these fields in whichever batch ingest methods they use. eg. Upload CSV or Excel should have corresponding columns. For xml uploads the inventory information tab in the import profile should allow the user to specify where these IDS are to be extracted from.

    https://knowledge.exlibrisgroup.com/Alma/ProductDocumentation/010AlmaOnlineHelp(English)/040ResourceManagement/050Inventory/030ManagingDigital_Resources

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. Patron Deposit Forms: full control over the normalization rules on all Marc21 fields

    When using NRs on Patron Deposit Forms, it is not possible to apply these rules on fixed fields. On the other hand, some rules are running in the background and set indicators or add new fields upon existence of some subfields (eg. 245 $c) that cannot be turned off.


    • Allow normalization rules for the point of import for all fixed fields (that would add the 006, 008, LDR and so on)

    • Remove all out of the box normalization rules for all fields (e.g. field 245 sets the indicators 1 | 0 and creates a 100 field with the indicators 1…
    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. 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

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. 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…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. Access rights: Not available after X date

    Add an access rights parameter 'not available after x date' OR 'available till dd/mm/yyyy'

    Essentially an inverse embargo period.

    This would be extremely helpful for purchased and copyright material for which we have a limited licence, e.g. one semester or one calendar year.

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. Publish Alma-D to Google (Fulltext .txt, .pdf) and Google Images (.jpg, .tiff etc.)

    Provide option to Publish collection from Alma to Google (files of type .txt, .pdf for full-text indexing by Google) and Google Images (in the case of img formats .jpg, .tiff, etc.)

    This is an alternative to Primo discovery layer (Google is moderately popular search engine, Bing and Baidu etc.)

    https://images.google.com (or click Images tab in Google) show photos and thumbnails from all over the Internet, and Google allow you to upload an image and search where it came from or similar images which may be helpful to publish/assert the origins of a file.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. 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…

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  20. 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.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base