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

203 results found

  1. Subdivided LCSH headings should be flipped by Preferred Term Correction

    Preferred Term Correction is not flipping all LCSH headings when the authority record changes. If there is an authority record that has a subdivision, it is only flipped by PTC if the heading in the bib has no additional subdivisions. This means there is a significant gap in the PTC process that requires manual attention and handling, which is unsustainable. The PTC process needs to be more thorough.

    For example, this LCSH:

    $a Germany $x Politics and government $y 19th century

    was updated by LC to be:

    $a Germany $x Politics and government $y 1789-1900

    When the authority record changed,…

    305 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. Metadata editor: Enable moving up and down within a field using arrow keys

    It would be nice to be able to move up and down within a field using arrow keys in MDE. For example, when a lengthy 505 or 520 MARC field has many lines, the cataloger must now move to the desired line using either mouse or left/right arrow keys, since pressing up/down arrow causes the pointer to move to the previous/next field.

    My suggestion is that the pointer should be able to move within the field using up/down arrows and move only to the previous/next field when the pointer is on the first/last line of the field.

    Using up/down arrow…

    279 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. Re-sequence MARC fields by each tag when running a normalization rule

    Currently, after running a normalization rule on a set of bib records, the bib records display the 5XX fields out of order, e.g. 500, 546, 506 etc. This occurs even after running the CnmarcBibReSequenceTask as fields between 500 and 899 are not sorted, or sorted only by hundreds (this was the information given to us by a member of staff when we reported the issue on the ExLibris Customer Portal).

    Having all fields in the correct order would ease any future cataloguing needed on these records, or when staff members view the record for work purposes.

    I've attached an example…

    256 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. Suggestions for Normalization Rules (NR) functions

    Hello,

    Please see the attached file.
    We would appreciate it if the suggested Normalization Rules functions would be developed in Alma.

    Thanks

    203 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. Decouple the bib-level material type of Music into Scores and Sound Recordings

    The bibliographic material type of Music inexplicably combines scores (Leader/06 c or d) and sound recordings (Leader/06 i or j) into a single facet. This makes no sense and makes standard statistics reporting extremely difficult as scores are usually reported with books (they are, after all, pieces of paper bound between covers) whereas sound recordings are usually reported with other media. Scores should be separated out as its own bib-level material type.

    184 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 this ideas exchange request.
    For the purpose of clarification:
    Alma uses (among others) two levels of faceting the bibliographic records: Material type and Resource type.

    Regarding the Material Type: There are seven different distinct bibliographic material types in Alma, and this corresponds to the seven different distinct bibliographic material types used by the MARC standard. These MARC standards are explained at https://www.loc.gov/marc/bibliographic/bdintro.html under section “Scope of the Bibliographic Format”. Ex Libris will leave these distinct seven formats, and not add or subtract from them. This is because there are seven distinct formats in the MARC standard. For this reason we will not add another format or change the name of an existing format. Each bibliographic record has one bibliographic material type. The Material Type is considered “Music” if the LDR pos. 6 is one of the following: c d i j. This is explained in the Ex…

  6. It would be helpful if there were an option to "print MARC record" within the MD editor and from the Repository Search.

    We sometimes have need of a hard copy of the MARC record for tracking certain workflows. One such example is for making notes about title changes and tracking them across several records. It would be nice if there was a "print full record" option, both in the MD editor and in the repository hit list. Right now, we need to either do print screens or do a screen capture and print from that. Thank you!

    166 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)

    Dear all,

    Since this idea was posted, the "Print Bib records" cloud app was developed, and support for it was added in the MDE. It is now possible to print one or more records from the MDE, in multiple formats, as described here: https://developers.exlibrisgroup.com/blog/how-to-install-and-use-the-print-bib-records-cloud-app/

    Does this answer the need raised in this idea? If not, could you provide more details on what it is you're missing in the app?

    Thanks!

  7. controlled vocabulary list upload

    Hi,

    Instead of create term by term when working with controlled vocabulary, enable the option of upload an excel file or any csv file that will do that.

    143 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. Allow cataloguers to choose which names are linked to authority files

    Allow cataloguers to choose which names are linked to authority files

    This is important because the all on or off automatic linking creates links for unqualified names and catalogers want the option to verify and thus link names in the way it is done in connexion.

    This when the authority data is updated - every record attached to it is improved and unqualified or non-established names do not get affected.

    137 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. Job or tool for extraction of related bibliographic records

    We would like the ability to get a hold of or extract the related bibliographic records in bulk based on a set of (other) bib-records.

    Alma already now automatically displays related records in "other details". We understand that the links are built based on bibliographic data in the MARC linking fields: 773, 774, 777, 786, 800, 810, 811, and 830 (subfield w,x,z).

    An example of a related record is a title within a monographic series. In this case, the bib record for the single monograph has a 830 $w with the MMS-ID/system number of the superordinate bib record.

    We would…

    117 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. Incorporation of All Indigenous Syllabics from the Canadian Aboriginal Syllabics Unicode Block

    I have a case open with Ex Libris (# 00517082) regarding this. Not all Indigenous syllabics render in Alma, and thus, do not render in Primo either. As an important aspect of Canadian Libraries' commitments to Truth and Reconciliation, and as it is UN's International Year of Indigenous Languages, it would be excellent if Ex Libris could prioritize resolving this issue so that we can allow Indigenous users full discoverability of resources in their own languages.

    112 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. Allow renaming of normalization, indication, and merge rules

    Please allow renaming of normalization, indication, and merge rules. Right now you can only duplicate the rule and change the name of the copied rule.

    110 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 a linking job for mass linking of NZ records to IZ

    Currently the only way to use records from NZ in an IZ is to search them in the NZ and perform an action like "order" or "link" on every single record one by one. There are, however, situations where an IZ wants to use a bulk of records. For this purpose we need a possibility to link records in bulk and create inventory for the linked records.

    We imagine a linking job that takes as an input a logical or itemized set of records saved from a search in the NZ. The linking job can create physical and electronic (and…

    109 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. Browsing Dewey in MD Editor

    We noticed that in Metadata editor the browsing in the 676 - Dewey field isn't available: we would like add the feature to scroll the lists from other records, as happens for the 6xx fields (subjects) and 7xx (authors).

    108 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. Add ORCID ID to CZ Authorities vocabularies search

    Field 0247 $$a XXXX-XXXX-XXXX-XXXX $$2 orcid used in authority records and is currently not searchable in CZ authority vocabularies.
    Using a unique identifier when searching for name authority records will improve the precision of authority search results. It would also save the time and effort currently invested in establishing the correlation between a name and its authority record.

    108 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. Identify headings linked to authority records in Simple Record View

    I frequently consult the Simple Record View page of bibliographic records when working on the Authority Control Task List. This view, however, does not indicate which headings are linked to authority records and which are not. The only place in Alma to confirm this is through the Metadata Editor.

    This proposal recommends adding a marker (such as the binoculars icon found in the Metadata Editor) to those fields in the Simple Record View with headings linked to authority records. This would save a step in the Task List review process, not to mention being helpful to any Alma user looking…

    97 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. Automatic dismissal of corrected authorities from the Authority Control Task List.

    Automatic dismissal of corrected authorities from the Authority Control Task List.
    Improve the Authority Control Task List linking functionality so that when an authority is upgraded/corrected in the metadata editor, it is automatically dismissed from the Task List. Items are added to the Task List before an institution has had a chance to upgrade the catalogue record. Many of these authorities will routinely be upgraded at the cataloguing stage. The need to then manually remove substandard authorities from the Task List which no longer exist in the bibliographic records adds a huge burden of extra work, especially for large institutions.…

    96 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. Reminders : extend the Add reminder functionality to other roles (only Cataloger now)

    Reminders functionality could be more effective if extended to other roles than only cataloger role. At least Electronic and Physical inventory operators should be able to add a reminder on a Bib record in a repository search result.
    The managing of reminders from Cataloging menu can be limited to catalogers.

    81 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. Prompt message if you have not saved a record before releasing

    Currently if you edit a record and then go to release it before you have saved, you do not get any kind of prompt asking if you want to release it without saving.

    There is also no prompt message if you try to save a record that has blocks to let you know that the action was not done.

    80 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. Management tags for new bibs - allow default to be changed to 'Don't publish' to WorldCat.

    The default when creating a new marc21 bib is for the management tag 'Force export to WorldCat' to be set to 'Publish bib'. This applies even when the Library isn't a member of OCLC. I'd like the default behaviour to be configurable so that 'Don't publish' can be set as default by those libraries who choose not to do so. In our case this would then mirror our existing stock, which was migrated from our previous LMS/ILS with the tag set to 'Don't publish'. In turn if a Library chose to join OCLC at a later date all items would…

    76 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. search filters and better results display in the "search external resources" function

    When we are searching WorldCat for a record to match a newly-ordered title, we often find duplicate records. The current search results display makes it difficult and time-consuming to choose the best record.

    The external resources search would be much improved if we could limit search results by the language of cataloging (040 |b) and format. This would save us having to wade through multiple vendor records that aren't even in our local language of cataloging, and multiple records for resources in a format other than the one we are looking for.

    It would save us a lot of time…

    74 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)
← Previous 1 3 4 5 10 11
  • Don't see your idea?

Feedback and Knowledge Base
https://ideas.exlibrisgroup.com/forums/308173-alma/category/339043-metadata-management
ideas.exlibrisgroup.com
CC-MAIN-2023-14
478641
application/http; msgtype=response
sha1:NOELTKZKXPETHRODVA7SBFTJFRFRI3ZJ
<urn:uuid:d693522d-b330-4a6f-bee5-50409444349f>
2023-03-27T14:31:56Z
104.17.31.92
text/html
sha1:TC7PRVIXOEXWAMMCH4GEUUZR4FF5JOOW
<urn:uuid:24aef3fd-b1bd-44a1-a673-ac4f0ed80cdf>
https://ideas.exlibrisgroup.com/forums/308173-alma/category/339043-metadata-management
response
<urn:uuid:c38631c1-35d2-4b14-b6ff-19949b560c29>
isPartOf: CC-MAIN-2023-14
publisher: Common Crawl
description: Wide crawl of the web for March/April 2023
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-142
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.4-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/