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.
1914 results found
-
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 votesThis idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.
-
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 votesThis idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.
-
Expose metadata dictionary to customers in Alma Analytics
Oracle OBIEE provides functionality to describe metadata associated with fields in the subject area tables:
https://docs.oracle.com/middleware/1221/biee/BIEUG/analyses.htm#BIEUG587
This does not seem to be enabled in Analytics, but having it as a ready reference would greatly facilitate creation of reports.
Thanks!
34 votesDear all,
Thank you for submitting your idea.
As it has not gained the traction we typically look for to move forward, it is unlikely to be implemented in the foreseeable future.
That said, your feedback remains valuable, and we will continue to keep it in mind as our roadmap evolves.
Best regards,
Hadas Granot
Analytics product team
-
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 votesThis idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.
-
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 votesThis idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.
-
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)
31 votesThis idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.
-
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 votesThis idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.
-
Ability to remove Associated PO Lines from a POL
If we add a POL # to the Additional section of a POL > Associated PO Lines and then discover that it was incorrect we are not able to remove it. We can change it but not remove it.
We would like to be able to remove the Associated PO Lines if we find that we have made a mistake
30 votesDear all,
This idea hasn’t gained the traction we typically look for to move forward. As a result, it’s unlikely to be implemented in the foreseeable future.
That said, your feedback remains valuable, and I’ll continue to keep it in mind as our roadmap evolves.
Best regards,
Tamar Fuches
Alma product team
-
In Metadata Editor, open records by MMS id directly
It's common to have a list of MMS ids that need to be worked on in Metadata Editor. The current workflow is to do a repository search, be taken out of MDE, click "Edit Record" and wait to be slowly taken back into MDE.
It would speed things up tremendously if there was a way for users in MDE to input an MMS id and just have the record open up straight away.
30 votesThis idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.
-
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 votesThis idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.
-
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.
30 votesThis idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.
-
Idea Exchange Login
Get rid of what has been called the "magic link" login for the Idea Exchange. We'd like to go back to just a username and password. ("Magic link" is what it's been called on ALMA-L. It's where instead of asking for a username and password, you have to enter your password and wait for an email.)
30 votesThe platform used for Idea Exchange is called User Voice. User Voice has changed the authentication mechanism appx 2 month ago, to gain more security.
This is not configurable to admins and apply to all type of users by UserVoice.https://help.uservoice.com/hc/en-us/articles/360058706693-UserVoice-Authentication-Updates-
-
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.
30 votesThis idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.
-
reorder tags / fields in metadata editor mde using drag and drop
Sometimes repeatable field must be sorted/reordered.
For example, we have records with many 505 tags that are added overtime and we have to arrange their order so that they are properly displayed in Primo.
Right now one must copy the content of the tag to move; add a tag in the proper position with indicators etc.; paste the content; delete the source tag. Quite a long and error prone procedure.
Having the chance to simply drag and drop the fields in the mde to reorder them would be therefore a great enhancement.29 votesThis idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.
-
Remove MARC Relator terms ($e) from Author and Author (Contributor) fields (1XX/7XX) in Analytics
The Author and Author (Contributor) fields in Bibliographic Details in Alma Analytics are mapped from several subfields in MARC fields 100/110/111 and 700/710/711, respectively, including subfield e. But subfield e should not be included in the Author and Author (Contributor) mapping because it is not part of the author name. It is instead a separate element that denotes the relationship between the named author/contributor and the work, the Relator. Thus the $e value may vary or be absent from records although the author/contributor is the same, making it impossible to search upon, identify, and unite author/contributor names in Analytics. Any…
28 votesHello,
Thank you for this suggestion.
With the recent introduction of "Flexible definitions of local parameters", libraries can now configure their variations of author fields in Analytics.
Several institutions have already implemented this capability successfully and confirmed that it meets the underlying need described in this request.
As the enhancement now enables the desired workflow, we will proceed to close this Idea Exchange.
We appreciate the community’s input and engagement.
Hadas Granot
Analytics Product Manager
-
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 votesThis idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.
-
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 votesThis idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.
-
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 votesThis idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.
-
Enable Individual Portfolios for Publish to PubMed Profile
There is not a way to set up individual profiles for the Publish to PubMed Profile for individual colleges that share one Alma instance. This functionality is important and should be enabeled. Without it, patrons using PubMed will not be aware which results are available in full-text through their college's databases. The expected outcome of this improvement is that it would provide a way in the Publish to PubMed profile manager to set up individual profiles per college, like there is in the Publish to Google Scholar Profile.
26 votesNLM PubMed Library LinkOut supports placing the library link resolver icon on every PubMed citation therefore there is no need to
upload the library holdings to PubMed
Publishing to PubMed is no longer needed
for more information about how to setup PubMed Outside Tool to place a link on every PubMed record see
https://www.ncbi.nlm.nih.gov/books/NBK3803/#related.Outside_Tool -
Set analytics refresh date to a specific time
We need some of our analytics reports rather early in the morning. The analytics refresh time is sometimes so late that our coworkers have problems to finish their work before we open our library, at which point their work needs to be done. We would appreciate a fixed time for the daily analytics refresh.
26 votesDear Colleagues,
Thank you for your request to end the daily analytics data refresh by a specific time. Unfortunately, we are unable to accommodate this request as we run an ETL at the same time for all the institutions in a specific data center. It is impossible to configure different run times per institution or even per instance. Additionally, we cannot predict the duration of the run-time in advance, which could take anywhere from a few hours to 10 hours.
We apologize for any inconvenience this may cause. Please refer to our online documentation for more information.
Best regards,
Shoshana de la Fuente
Senior Product Owner
- Don't see your idea?