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. Community Zone records: subfield t missing in 780 and 785 MARC tags

    In the CZ please add $t (Title of the related resource) to tags 780 (Continues) and 785 (Continued by).

    The lack of $t causes issues in discovery where 780 and 785 tags are set to be displayed, linked and searchable. With no $t this is not possible.

    31 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. Normalization rules - adding dates

    It would be great if the normalization rules could be enhanced to use variables such as date, or add datestamps.

    We would like the ability to insert dates into MARC notes fields via normalization rules.

    Ideally inserting variables something like %DAY%/%MONTH%/%YEAR% in a rule would add today's date in the format DD/MM/YYYY once a rule is run.

    28 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. Enable labeling enumeration and chronology fields

    It can be difficult to recall the meaning of enumeration and chronology fields, e.g., Enumeration A, Enumeration B, Chronology I, etc.). It would be helpful if general system administrators could change the labels of these that show to staff, for example, change Enumeration A to Year.

    27 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. Allow overlap analysis tool to include print as well as e

    We would find it useful if the overlap analysis tool could also compare against print holdings, as well as electronic. Currently it only allows you to compare overlap within electronic titles, however the functionality of the tool is useful in that you can upload a file containing a list of identifiers, set up the overlap and leave it to run.

    The only way to conduct print and e overlap analysis in Alma at the moment is to use the Title level overlap analysis dashboard in Analytics, which includes various overlap reports and includes both print and electronic. However, we have…

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

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

    Hello,

    The assimilation of Melingo in Primo for the customers in Israel proved to be a useful solution.
    It would be nice if it can also be implemented in ALMA.
    If Melingo will indeed be in ALMA, the catalogers will no longer need to add Ktiv Maleh or Ktiv Haser in Hebrew in variant titles.

    Thanks.

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. Add a mapping structure for normalization/merge rules in MDE

    The numbers of normalization rules is getting quite annoying. When we are in a consortium we also see every rule in the network zone.
    I would like a posibility to create folders like in Analytics.
    This would be helpful to group rules by institution or category.

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. Allow option to abort import once it has been submitted

    Once an import has been submitted, there should be an option to abort or cancel the import.

    Sometimes mistakes are made. The wrong import profile is chosen, the wrong file is chosen. Often the mistake can be noticed very quickly, but there is no choice but to wait until the entire import file is loaded. And by then the damage is done, it can be very tedious in Alma to undo certain mistakes (portfolios imported to the wrong collection for example).

    Alma offers the action option to "abort" once a job has been submitted. This same option should be available…

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. Index the Marc 546 field in Alma Repository Search

    Libraries have expressed the need to search the Marc 546 language note field in Alma repository search. https://www.oclc.org/bibformats/en/5xx/546.html

    Use cases:
    to search for specific languages that do not have a Marc language code in the 041 field.
    Or to search for closed-captioning or subtitle info in the 546 field. (Example: "English, Spanish, French or Mandarin dialogue with optional English for the hearing impaired; closed-captioned."

    https://www.oclc.org/bibformats/en/0xx/041.html

    Like how other 5xx fields are indexed in the Notes search index, could the 546 be indexed as well?

    https://knowledge.exlibrisgroup.com/Alma/ProductDocumentation/010AlmaOnlineHelp(English)/040ResourceManagement/040MetadataManagement/180SearchIndexes/MARC21SearchIndexes

    Voters: If you would like…

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. Add a lock feature to prevent selected items from being withdrawn when running a job

    I envisage this as a simple checkbox within an item's record which prevents that item from being accidentally withdrawn. (A parallel exists in many photo editing software packages.)

    I also envisage this as being a property which could be engaged or disengaged on a set of items via a job.

    When running a withdrawal job, any such "locked" items which were not withdrawn should be listed individually in the job report so that the user can determine whether this was correct (in case an item has been accidentally locked by a user, for example).

    A use case is as follows:

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. Combining multiple itemized sets

    We'd really like the ability to flag multiple sets to be combined to create a single combined set. Several times we've wanted to do this to facilitate data analysis (e.g. on sets created logging weekly data loads), but it's far too time-consuming to combine them two at a time!

    23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. Full PCRE Regular Expressions in Normalization rules

    Supporting full PCRE regular expressions would make Normalization rules so powerful. Allow capturing data in one place and re-using it somewhere else, checking for substrings, etc.

    23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. Add more times to scheduled weekly bibliographic import jobs

    When running import jobs on a schedule Alma only gives us one weekly option (Saturdays at 3:00 a.m.). OCLC WorldShare generally posts new, delete and updated files on Saturday mornings in the early a.m., although not always by 3:00 a.m.
    Since it doesn't make sense to run these import jobs daily since record sets are only delivered weekly, we have them set up to run at 3:00 a.m. on Saturday (the only weekly option that Alma gives us). This causes the following problems:

    1) Files of deleted records are loaded concurrently with files of new records for the same collections…

    23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. Add 775 field in the search index.

    Currently this field is not indexed in the search index. Would you please add it so that it can be searched?

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. Raise the limit to total number of rejections ( currently 1000) for exporting records that are not imported (due to import profile setup)

    There is currently no limit to the number or records that can be imported into Alma (as far as I am aware).. there is however a limit of 1000 when needing to export the rejected data.. Workflows would be much better managed if this limit was raised to the total number of rejected records

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. Enable 'recall' option on individual work orders

    At present work order types can be set to recall items or not.

    It would be useful to have this as an option for individual work orders (much as 'do not pick from shelf' is an option).

    This would make work orders more versatile and save having two work order types ('recall' and 'no recall') for essentially the same process.

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

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. Add active link function to all fields where a URI in subfield u is valid

    Subfield u for uniform resource identifiers has been defined as a valid subfield in many bibliographic fields to provide automated access to electronic resources.
    As noted in the OCLC bibformats: "Subfield ǂu defined as the URI is valid in the following fields: 031, 370, 381, 505, 506, 510, 514, 520, 530, 538, 540, 542, 545, 552, 555, 561, 563, 852, 856, 880, 883, 884, and 956. Additionally, subfield ǂu can be used in fields 901-907 and 945-949, either in accord with its control subfield definition or as a locally-defined subfield" (http://www.oclc.org/bibformats/en/controlsubfields.html#subfieldu).
    Currently, only URIs in 856 subfield u…

    20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  20. Brief result display options per Alma login

    Enable Alma users to choose "brief display" options (either very brief or extended information). Many of our Alma users would like to be able to do a search in Alma (in both repository search and course reading lists) and ONLY see a list of titles (e.g., do not display Format, Subject, ISBN, Availability). However, recognize that many Alma users would like to see extended display, so we would like each Alma user to be able to set their display preferences (e.g., brief, title only OR additional information). Ideally, users could choose exactly what data elements to display (e.g., OCLC number,…

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

Feedback and Knowledge Base