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.
123 results found
-
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 -
Improve ME Browse Call Numbers Tool
When editing a holding record in the Metadata Editor, the Browse Call Number tool shows the call number from the current holding record in a shelf list display. However, the resulting list starts with the call number in your holding record and shows the following call numbers. What we need is to see the call numbers both before and after the one we're working on. Request the list show at least 2-3 call number prior to the one we're working on, plus those following.
39 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>
39 votes -
Further filtering in Authority control task list
We are regularly getting old bib records in the Authority control task list and they make it hard for us to spot new bib headings that we need to add to our local authority file. It would be very helpful if it would be possible to filter the list by creation date to limit the list to new bib records.
36 votes -
Disallow deletion of sets that are used by jobs (publishing profiles, etc)
When deleting sets, please perform a check to see if that set is in use by a publishing profile or other job, and show a popup dialog telling the user that the set cannot be deleted because it is in use, or allow deletion but warn the user that the set is in use by a publishing profile etc.
35 votes -
Index fields 772 $$w and 830 $$w for the Alma Repository Search
As these fields are currently not indexed but would be very useful, we strongly suggest adding them to the search indexes which are available for the Alma Repository Search.
Field 773 $$w is already indexed and we think these two additional fields could be used for similar search queries.(Follow up of support case 6659197)
32 votes -
Authority linking issue with bibliographic field 240
We'd request that when Alma links up bib field 240 with a uniform title entered in authority record, it should take into account of bibliographic contents in field 240 PLUS field 100 ALTOGETHER, and link these combined contents with uniform titles entered in authority records.
Currently, it links up the uniform title in field 240 only with authority record. So, those generic uniform titles e.g. Works, Poetry, etc. will be ambiguous, and do not have proper linking with their authority records established with author's name.
Details, please refer to Salesforce case # 823121
32 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 -
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
30 votes -
Index field 310 for the Alma Repository Search
It would be useful to be able to search within all records with field 310 not only through the codes in 008 but also via the text in 310. We therefore suggest adding the field to the indexes for the Alma Repository Search.
29 votes -
Add the NOT Boolean operator to the Advanced Search in Alma
Advanced Search in Alma contains currently only AND and OR Boolean operators - it would be very useful to have the NOT operator included, so that we can exclude particular records from Logical Sets, rather than creating 2 Logical sets and then combining them with NOT, resulting always in an Itemized set.
27 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…27 votes -
Option to export Alma search results and sets as CSV
Right now Alma search results and sets can only be exported in XLSX-format. For performance (and other) reasons it would be good to have the option to export in CSV format.
(Publishing this as an enhancement request was suggested by Ex Libris in public Salesforce case #00825531)
27 votes -
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 -
Add an option to search the repository by "Assign to" cataloger / operator
Currently there is no way to know which records are assigned to a certain user except for the "assigned to" note indication. We need a way to retrieve the records that were assigned in order to restore them back to the users' MDE, in case they dissappeard from the opened records pane. See full usecase in SFC#00957311.
26 votes -
Add a job for adding Repository search labels
please create a job to add Repository search labels for titles and holdings based on a set. This would be a convenient solution for managing large numbers of records in the new UI and the addition to bulk labeling.
26 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 -
Use of parentheses in advanced search
Currently advanced search does not allow the use of parentheses. We'd like to suggest the capability of using parentheses in doing some complicated search logic. This can shorten the search query a lot. Currently, we have to repeat the search queries, and apply a combination of AND/OR search logic. The attachment explains the situation with a screen shot of current search logic.
24 votes -
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 -
Index field 773 $$g for the Alma Repository Search
Our libraries would like to have subfield $$g in field 773 indexed for searching in Alma, because it would allow to have more precise search queries including e.g. the issue number within a journal collection.
24 votes
- Don't see your idea?