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.
121 results found
-
Make configurable pop-up assistance in metadata editor
Currently the po-up assistance in metadata editor for subfields 260$a$b$e$f, 264$a$b, 505$r$t and 561$a is hardcoded and it can not be deactivated. Activation/Deactivation should be configurable. We have many queries from our catalogers about that.
300 votes -
Add a drool normalization process option, to Publish to Primo job
This will enable libraries to export to Primo their activated CZ bibliographic records, under the same conditions applied on their local bibliographic records.
46 votes -
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
221 votesDear all, since this idea combines various very different enhancement requests for Alma's normalization rules infrastructure, we are unable to add these to our roadmap at this time. This may change as we get more information on prioritization and needs. In the meantime, we suggest opening dedicated ideas for specific enhancements you would like to promote.
-
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.
128 votes -
Ampersand symbol (&) in Repository search
It's found that the repository searches using the ampersand (&) symbol and the word 'and' produce different results. Our request is to make the ampersand symbol and the word ‘and’ interchangeable when Alma does repository searches.
SF case # 00646924
60 votes -
Create a task that orders the 6xx (subject) fields
Alma currently does not have a way to mass resequence the 6xx subject fields, at least into consecutive order. This is an issue in analytics if subject is the field you organize your results by, as the initial subject field (600) may no longer be the first subject displayed and therefore searched on.
25 votes -
Create a Separate Search Index for Specific OCLC Number
Currently, the OCLC Number for a record is indexed in the search index "Other System Number." This is not ideal, since the Other System Number indexes other numbers related to vendor record, CONSER, related item, etc.
We request that Ex Libris provide a separate search index for OCLC number based on the presence of the '(OCoLC)' prefix in the 035 $a and/or $z, or (without prefix) in the 019 $a if there is a number in the 035 with an (OCoLC) prefix. Currently these specific (OCoLC) numbers are mixed in with other numbers occurring in the 019, 035, 773, 774,…30 votes -
Bibliographic records editing history
Here is an enhancement request concerning bibliographic records editing history.
Currently, the "View Versions" can only tell the different version of a bib. record. However, this cannot tell logging history of updating/editing the bib. records, e.g. who add/remove a MARC fields/who suppressed/released the bib. record etc. This is no history tab to keep tracking the changes of a bib. record which is unlike other history tab functionality available in other Alma pages, e.g.
• The PO Line Summary page when editing a PO line
• The Physical Item Editor page when editing item records
• The License Terms Details page…89 votes -
Lists of Name Authorities similar Subject Authorities
Lists of Name Authorities similar Subject Authorities
When cataloging a bibliographic record, Alma allows selecting different lists of Subject Authorities (LC, UC or UANDES, etc.). In the case of the Name Authorities, it currently only allows the use of a list of Name Authorities. We propose that the authorities of name are handled in the same way as the Matter Authorities.// Al momento de catalogar un registro bibliográfico, Alma
permite seleccionar distintos listados de Autoridades de Materia (LC, UC o UANDES, etc.). En el caso de las Autoridades de Nombre, actualmente sólo permite usar un listado de Autoridades de…27 votes -
Preferred term correction - correct coding when flipping LCSH to LCGFT
When a 655 field is coded for LCSH and matches a non-preferred term in LCGFT, Alma flips the heading to the preferred LCGFT term but does not update the coding (it should change the 2nd ind to 7 and add $2 lcgft).
The problem is limited to cases where:
A bib heading 655/_0 matches a non-preferred term in an LCGFT authority
What happens is:
The PTC job flips the heading to the LCGFT preferred form, but it does not change the 2nd-indicator from 0 to 7, and does not add $2lcgft
What is not a problem:
655/0 headings that…
61 votes -
Preferred term correction should flip headings that change tag number
Alma authority control does not handle cases where the bib heading is linked to an authority via a cross-reference, but the preferred and non-preferred terms are in different fields, e.g. preferred term is in authority field 130 and cross-reference in authority is in 410.
Alma should be able to handle this scenario. Currently when the bib heading matches the authority cross-reference, Alma won't correct these and instead puts them on this report: Preferred Term Correction - Bib Heading found no authorized term.
Example bib heading that Alma won't correct:
110/2_ $$a Allied and Associated Powers (1914-1920). $$t Treaties, etc. $$g…
249 votesWe will add this improvement to our roadmap
-
Create a "natural language" editor to create Normalization rules
The process for creating Normalization rules is unnecessarily complex and difficult, particularly for those of us who are not familiar with Drools logic. Our previous LSP had an intuitive interface which made creating rules to change details in MARC records much less time consuming. Ex Libris would do well to create such an interface.
15 votes -
browse by subject headings to include 600/610/611
currently browse bib headings by subject does not include 600/610/611 fields (they are placed in 'names'). When browsing by subject one would expect to find all subjects including those that describe people/companies etc.
57 votes -
add security levels to norm rules
Because all norm rules can be edited by all staff with cataloger roles, there is great room for erroneous changes for rules that are applied to batch jobs. For example, the norm rule that is applied to records being brought in from Z39.50 targets can be edited by any staff member. A single error in the rule can break the z39.50 import process for all staff until the source of the error is identified. Likewise, if we have a rule applied to import profiles and a staff member inadvertently changes it and we load 50,000 records, that could cause huge…
287 votesWe are considering incorporating the idea and effect both templates and rules editing permission
-
Copy and paste multiple MARC fields into the metadata editor
We would like to be able to copy multiple lines from MARC records and paste them into the metadata editor so that multiple MARC fields are pasted into the record in one action. This would help us enormously with our workflow of importing MARC authority records from LibrariesAustralia into Alma.
For us, this is necessary because the LibrariesAustralia headings are not in the community zone and are unlikely to ever be included there and Alma does not allow for Z39.50 import of authority headings.
We have this functionality of copying and pasting multiple fields in the LibrariesAustralia Cataloguing Client and…
542 votesDear all,
I believe we now understand the requirement better: To be able to paste a block of text in MARC 21 format, and have Alma parse it and populate the MARC tags, indicators and subfields accordingly.
This is a larger development, but we hope to be able to add a solution for it to our future roadmap.
-
Put full 100 field information in search results
Please put the full 1XX field in the search results.
We have many people with the same or similar names which are distinguished by dates or other information from the 100 field. It would be very useful to have all the personal name information this display in the metadata editor and also to be available in the Excel download of the search results.
20 votes -
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).
114 votes -
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…
78 votes -
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.
145 votes -
Indication that shows I edited an open record
Icons in MD-Editor only show if a record has been saved or not. I would like to have an indication to see if the record has been edited by me after I opened it.
212 votes
- Don't see your idea?