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.
116 results found
-
Allow sorting of itemized set members similarly to logical set results.
In Manage Sets, enable sorting the members of itemized record sets by title, creator, and publication date, similar to the criteria available for sorting results of logical sets. Currently our only option for sorting the members of an itemized set is by exporting to Excel and manipulating the resulting spreadsheet, which doesn't allow for clean sorting by the same criteria.
100 votes -
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!
19 votes -
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.
25 votes -
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…24 votes -
create brief record
In Resource Management, there are options for creating a physical item using a template that list the MARC fields as their type, not like the field numbers in Metadata Editor. Such as, Title is listed with a field to enter this information, and Author and so on for the Resource Information. As a cataloger, I know the MARC field numbers and can easily catalog in Metadata Editor, but this is not the case for the acquisition coworkers I collaborate with to order new materials.
In the Add Physical Item function, you can create a brief record with only the title,…
42 votes -
Add members to set from results screen
We would like an easier way of adding individual titles to itemized sets. It would be nice if, on the results screen after performing a search, you could click the ellipses menu for more options and see "Add to set" there, which would then direct you to select a set to which you'd like to add that record.
14 votes -
Allow configuration of quick cataloguing form required fields
We currently only use the quick cataloguing form at circulation desks to create quick records to loan items found on the shelves but not found on Alma. The items are loaned and then the work order routes them to the cataloguing team on return. All these items already have call numbers so we'd like the call number field to be a required field in the quick cataloguing form. Sometimes returned items are incorrectly returned to the shelves and if the quick catalogue record does not include the call number they are often impossible to track down.
226 votes -
Ability to edit records during import when manual handling required
During the import of records, we sometimes get the "Manual Handling Required" notice, from which we can view the record in question as well as its error.
On that screen you can view the record and we have often found that only a small fix is needed to correct the error, and would be best done at this point in the process rather than getting the original file, making a change, and either reloading the whole thing or extracting the one file to fix and reload it alone.
It would be nice if, along with the ability to simply view…
12 votes -
Ability to browse all call numbers in a single search
We would like the ability to browse all call numbers, regardless of call number type. In Alma, many of our local Library of Congress, Dewey, and SuDocs call numbers are retrievable only by the call number type Other Scheme. An “all call number” browse would allow us to retrieve a complete shelf list of our call numbers and would be especially helpful when assigning new call numbers.
20 votes -
Editing multiple collections from a set in bulk
We have a lot of historic collection records left over from our migration which we would like to update in bulk, for example, there collections have no portfolios so I would like to be able to add services to them all at once rather than individually. I'd also like to be able to update the "Library" field etc.
I can create a set of all these collections however, I can't make bulk updates to it. It would be great if there was an ability to run a job to add services and download a spreadsheet of all the fields in…
19 votes -
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 -
Unclutter index for F3 lookup from field 830 (Series Added Entry - Uniform Title)
F3 lookup from field 830 is used to verify if a series title has been entered into the database in a standardized form, and, if so, to link the bib record to that title . At present, the index searched by F3 contains a mixture of headings from fields 830 and 490 (where the non-standardized series title is entered) and headings with volume numbers (which refer to a part of a series, not the series as a whole). To best serve its purpose, the index looked up from 830 with F3 should contain and display only the fields $a, $p,…
20 votes -
Expand "Create Physical Items Work Order" job to include work order Status
The “Create Physical Item Work Orders” job should be expanded to allow users to add work order Status in addition to Type and Department to a set of records. Currently adding Status is a 2nd separate step. After running the job to apply Type and Department, you must then sign into the appropriate Currently At location, Manage In Process Items, and then apply the Work Order Status (limited to one screen of 20 records at a time). Very Inefficient!
78 votes -
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.
42 votes -
Ability to use import profiles on OCLC Connexion exported records
Currently import profiles can applied to Marc files that are uploaded into Alma. One can use the import profile to specify match methods, tell Alma how to deal with matches of existing and incoming records (overlay, merge, or use NZ record), and also specify inventory info to map the Marc 949 field to holdings and item records. Although the OCLC Connexion integration profile deals with importing records it lacks the features described in the previous sentence. Please see screenshot of settings in Oclc integration profile versus in an import profile.
Basically we would like the ability to specify an import…
58 votes -
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 -
Import Profiles - Match Profile add 028 - Publisher or Distributor Number to one of the match methods
When loading records via import profiles it would be great to be able to match on the 028 - Publisher or Distributor Number. Could this be added to one of the match methods currently available or added as a new match method>
17 votes -
Ability to run a job on a set from the Manage Sets screen
Currently we need to create a set in the Manage Sets area then go to "Run a Job", select the job to run and then select the set.
Wouldn't it be great if you could go to Manage Sets then click on "Actions" for a particular set, then choose "Run a Job". You could then be prompted to choose the job to run but you wouldn't need to go through the additional step of choosing the set (and you wouldn't have to exit the sets screen to go to the "Run a job" screen). And only the jobs that can…
47 votes -
Ability to create a chosen quantity of predictions
As someone who manages serial subscriptions, I would like the ability to choose the quantity of predictions I create for any given holdings record. This would allow for quicker navigation of list of items, and reduce the number of inaccurate predictions.
It is not always desired to predict an entire year’s worth of predictions (which currently is the only option). Depending on the publishing frequency and the number of copies of a subscription, we can have 11 pages of predictions in a list of items, in addition to the received items. This greatly increases the amount of clicking needed at…
164 votes -
Definition of local search indexes on the level of indicator and subfield
We need a possibility to define local search indexes on the level of MARC indicator and MARC subfield.
16 votes
- Don't see your idea?