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.
212 results found
-
MARC field 026 should be searchable
To identify ancient editions, it's important to register the "fingerprint", that MARC21 register in tag 026. This tag should be searchable in ALMA and in Primo
10 votes -
Adding the "Assign record to another cataloger" functionality in search results actions links
We use regularly the 'Assign record to another cataloger' functionality in the MD editor for corrections, for records enhancements, ... But this is unfortunately limited to catalogers roles.
It would really improve our resource management workflows if this Assign function was made available from search results lists. Other staff roles would so push records in an enhancements flow (such as improve marc records for newly created portfolios, such as indexing tasks, such as apply corrections that don't require having book in hands...). We actually use work orders for some in those tasks but this workflows are not always appropriate and…9 votes -
Duplicate MARC fields
The ability to duplicate MARC fields in the bib and holdings.
9 votes -
Enable separate authority control for LC children's subject headings (6xx second indicator 1).
I have been told that the LC children's subject headings have been merged into the LC adult headings, and that therefore the only way to control those headings is to change the existing 2nd indicator 1 to 0. This is non-standard MARC coding per MARC 21 Format for Bibliographic Data, which specifies second indicator 1 for LC subject headings for children's literature. It is my understanding that other libraries requested this change, so the activation of a separate LC children's subject headings thesaurus should be an option for those libraries that wish to continue standard MARC coding practice.
9 votes -
Ability to make the option suppress from discovery and Don't publish to WorldCat default in Metadadata Editor templates
In cases whena a library manages collections that should not be visible in PRIMO or in WorldCat, it would be of value if Metadata Editor Templates could be configured so that suppress from discovery and Don't publish to WorldCat is set as default.
9 votes -
Push bib record to MDE and make it as selected or opened by default or configurable
At present, bib record record pushed into MDE are not selected or opened in MDE. We want to make the record that is most recently pushed into MDE as the selected or opened record in MDE for streamline the workflow and improve productivity. If this requirement is not common, please think about making it configurable via a Customer Parameter.
9 votes -
Add option to Print bib record from MDE
We find it useful to have a printed bib record to reference on paper for various purposes, but Alma lacks the means to "Print" a bib record in the MDE. It would be extremely helpful to add Alma's print functionality as a button in the MDE menu options so that we can print specific records on physical sheets, as PDFs, etc.
9 votes -
Metadata Editor: Search Resources: Enhance importation of OCLC WorldCat records into Alma
As an alternative to using OCLC Connexion or OCLC Record Manager, we like to import OCLC records into Alma using Search Resources (z39.50) in the Metadata Editor. It is a more streamlined workflow for us to stay within the Alma environment for record search and importation, rather than switching between Alma and OCLC Connexion.
However, this method of importation does not inform OCLC that we have taken a record, for their purpose of flagging us as a holdings library in WorldCat.
Additionally, the imported record is not automatically saved in Alma, as it would be when imported via OCLC Connexion…
9 votes -
8 votes
-
Bibliographic creation date should be original load date
Currently, when you reload a bibliographic record, it updates the creation date, so you have no way of knowing when the record was loaded for the first time. This makes statistics gathering difficult. It would make more sense to have some sort of original creation date (at least in analytics), so you can see when that bibliographic record/MMSID was created in the system for the first time.
8 votes -
Show Brief Record Levels in Search External Resources
It would be really useful if we could see the brief record level when searching for catalogue records via "Search External Resources".
Currently the only way to perform a brief level analysis on a record is to import and save it. It would be really useful to see this when searching external resources, without having to save and import the record first.
This will be useful to ensure a good level of metadata is maintained across our catalogue.
8 votes -
Ability to publish data from different tags in the holdings record into a single tag per holdings record
When publishing data for external parties, we would like to be able to combine data from different tags in the holdings record into a single tag in the published record. E.g. we want to export library, location and call number details from tag 852$b$c$h as well as details of volumes held from the 866$a:
852 8_ $b J $c BJ $h PPPP007189-007195
866 41 $a v.31:no.1(1970)-v.34:no.11/12(1973)as 949 $a J $b BJ $c PPPP007189-007195 $d v.31:no.1(1970)-v.34:no.11/12(1973)
What we end up with is (in OAI) 2 separate published tags:
<datafield tag="949" ind1="8" ind2=" ">
<subfield code="a">J</subfield>
<subfield code="b">BJ</subfield>
<subfield code="c">PPPP007189-007195</subfield>
<subfield…8 votes -
Sort by Publication Date: Full MARC21 capability for sorting (detailed date sorting via 008).
In Alma the option of sorting search results by "publication date" (emphasis on "date") is included in the "sort by" function. For the publication date of television materials, a detailed date can be given in 008[11-14] in MARC21 (with the code 008[6]=e). This should be taken into account when sorting.
8 votes -
Remove Automatically Created Extra Space Before Subfields in the Metadata Editor
In the Metdadata Editor, an extra space is automatically created before the first full word after a subfield. This space shows up only when you begin to type the word.
Not only is this annoying, but it also affects the functionality of the authority record search, as that extra space has to be edited out for the authority to be found either with the automatic dropdown, or with the F3 command.
I have attached an image that shows this phenomenon. Note the margin difference between all of the other fields and the 090.
Please remove the automatic space.
7 votes -
(Metadata editor) Make the "yes" and "no" Release All Records buttons keyboard actionable
It would be great to be able just to type Y or N in the Release All Records dialogue window, rather than having to mouseclick on "Yes" or "No."
7 votes -
Visually accessible display of MMS IDs etc.
The MMS IDs and other IDs (e.g. holdings IDs, PIDs, item IDs, etc.) are very long. It's very difficult to distinguish one MMS ID from another.
In the case of MMS IDs in our IZ and our associated NZ, the last 4 digits are fixed and have specific meaning, e.g.:
MMS IDs ending with -3409 refer to our institution's MMS IDs
MMS IDs ending with -3406 refer to the associated NZ's MMS IDsWe'd like Alma to provide an option to display the 5 digits before the 4 ending digits in a different colour in order to make it easier…
7 votes -
Allow the contents of MARC subfield 041 $$h to be considered for Search Index Mapping
The MARC 21 Bibliographic Tag to Search Index Mapping table (https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/040Resource_Management/040Metadata_Management/180Search_Indexes/050MARC_21_Search_Indexes) confirms that the contents of 041 subfields $$a, $$b, $$d, $$e, $$f, $$g, $$j, plus those of the 008 field positions 35-37, map to an advanced search of the Language (Title) index in Alma.
The contents of 041 subfield $$h ("language code of original"), however, do not. This discriminates against those works which are translated from an original language into the one stipulated in 041 $$a subfield.
There are plenty of titles in our stock where information regarding the language of the original material is no less…
7 votes -
Active/inactive indicator for electronic collections
We propose an indicator - e.g. a yes/no radio button set - to indicate whether or not an electronic collection is active. This will make it easier to exclude inactive electronic collections from searches and Analytics reports. Current methods of indicating this status aren't comprehensive. The bib can be suppressed, and/or the URL removed, but there are other reasons to suppress bib records and remove URLs (such as when we want only portfolios to display in our discovery layer). In aggregator and selective packages, we can delete the service or mark it inactive, but this doesn't apply to database-type electronic…
7 votes -
Some Important Shortcuts in Alma and OCLC -- Consider User Friendly Changes
Some often used shortcuts in Alma are similar to those used in OCLC Connexion, except for their function. Control + D will delete a record in Alma (and any keystroke after the shortcut is interpreted as confirmation by the popup window), but in Connexion the same shortcut adds a delimiter $.
F8 keyboard function in Alma adds a field, but in OCLC it produces and adds a new record. Many of us, especially special collections catalogers use first OCLC and then Alma for local notes.
Please, consider shortcut changes, which support both important platforms, used daily by many of us.…7 votes -
Follow NACO rules when linking bib headings (reduce number of "ambiguous" headings in ACTL reports)
When linking bib headings, Alma does not follow NACO comparison rules when checking for ambiguous headings. This results in numerous headings not linking at all, and being reported as ambiguous. This reduces the utility of Alma's authority control process, because there are too many headings to link manually.
Examples of headings that Alma won't link because they are "ambiguous"
- Peabody Essex Museum
Peabody & Essex Museum
Ciné+ (France)
Cine France
Mohammad, Ali
Mohammad Ali (a cross-reference in the authority record for Ali, Mohammad)
McFarland & Company
McFarland Company (cross-reference in authority record for J. Horace McFarland Company)
Authority File Comparison…
7 votes
- Don't see your idea?