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.
37 results found
-
Allow same URL functions/rules possible for Dynamic URL in General Electronic Service URL Template
When constructing Dynamic URLs for electronic portfolios, Alma can parse URL functions such as SUBSTR, REPLACE, and URLENCODE to create working links.
General Electronic Services often require or would be improved by use of these URL functions for the same reasons as the Dynamic URLs, when the OpenURL attributes alone are not enough to create the best possible link.
It would seem that Alma already has the potential to parse these functions since they are used in Dynamic URLs, so allowing them in GES URLs should be possible.
8 votes -
Link resolver should use ISSN and title from external resource
When the link resolver receives a URL from an external resource, it should use the ISSN and the journal title from the incoming URL to create links for Interlibrary loans and ignore any related links if related links are activated (Fulfillment > Fulfillment Configuration > Configuration Menu > Discovery Interface Display Logic > Related Records). Currently, the link resolver will change the incoming ISSN and journal title to that of the related link when creating ILL requests, which makes the ILL article information incorrect.
7 votes -
Provide complete Factiva full text service
The Factiva full text service is incomplete. When searching with Primo, a complete set of results from Factiva is not retrieved. it is explained that the Factiva collection does not provide full coverage from the provider, but the alternative coverage mechanism also does not work. This was not an issue when we used Summon. It will be good for users to get a complete set of results from Factiva.
7 votes -
Use all of the author fields when creating a display record from an Alma resolver call.
Right now, if you pass an openurl call to the resolver with fields of rft.au fields and rft.aufirst or rft.aulast the record created does not include the main author represented in the rft.aufirst and the rft.aulast.
6 votes -
Resolvable URL that links to the ALMA record
From doing a search outside of ALMA, I have an MMS_id for a record I want to look at. (E.g. 9913920213502836 )
I want to be able to share this record page with a colleague, or store a pointer to the record in a document or spreadsheet.
The most useful approach would be to use a URL, where I could display the MMSid as the text, while pointing to the record as the URL ( e.g. www.myalmadomain/mng/action/showrecord.do?mms_id=9913920213502836 )
Because of how the page is built, there doesn’t appear to be a single url I can use…
5 votes -
Create a parser parameter for 'domain' that can be used in Dynamic URLs
We have electronic services that comprise portfolios from multiple publishers, and the portfolio URLs link to the publishers' websites rather than a common platform. Currently, this means that Alma can only link to the journal level, unless we edit each individual portfolio to use a Dynamic URL. However, because the structure of the URLs after the domain is consistent, we would be able to apply a single, article-level Dynamic URL at the Service level if Alma had a parser parameter we could use in place of the domain. Here is the URL format with a couple of examples:
http://{domain}/content/{rft.volume}/{rft.issue}/{rft.spage}
http://www.eje-online.org/content/176/3/349…5 votes -
4 votes
-
Show item title in browser tab name (title) for uresolver landing page
At present if users follow a link from one of our website or our VLE to an item with more than one content provider or a Public Note it takes them to an Alma landing page for the uresolver, which opens in a new window or tab.
The <title> of the Alma uresolver tab or window shows as 'Home'. If the user has several tabs open the word 'Home' is not likely to help them identify the one that contains the links to the item they were trying to access. It would be much more helpful if the browser tab…4 votes -
3 votes
-
Openurl resolver to search CDI when no full text services found in Alma
Sometimes the Alma openurl resolver can't locate an item, but you can find it in the CDI, so could the openurl resolver search the CDI by title + authors for possible matches? Perhaps present any results as suggestions, a bit like bX recommendations, so as not to raise expectations that the correct document has been found.
Here's an example. JSTOR has a record for a paper that was published in print in SAE Transactions, ISSN 0096-736X, 2001, Vol.110, p.86-92
https://www.jstor.org/stable/44724287But the paper is published online as SAE Technical Paper 2001-01-0233, ISSN 0148-7191
https://www.sae.org/publications/technical-papers/content/2001-01-0233/It is available in SAE Mobilus…
3 votes -
Allow General Electronic Services links to populate the services menu
Currently, the only way for a link from one of our sources such as Web of Science through Primo to the resource is using the General Electronic Service (GES). The problem is that "No full text available" will display in the services menu. SFX had the ability to make the GES link display in the services menu. Is there a way to force the Proquest D&T GES link to display in the services menu instead of the "No full text available" message?
2 votes -
More linking parameters for links in CDI records
I meant to submit this as an enhancement request but missed the deadline. We need the ability to do more than say Proxy Yes/No to links in CDI records. If you are an OpenAthens library, some vendors use the Proxy and others don't and Proquest in particular doesn't. In OpenAthens Proquest URLs get no redirector and instead have a ?accountid=*** with the customer ID. We need to be able to customize CDI links depending on vendor and to put a customer ID to build the correct URL, at least for Proquest CDI URLs. Also, it seems like if there is…
1 vote -
Full text hyperlink from the title level.
Direct linking to the article (when available) directly from the title result (that is make the titles hyperlinked to the full-text).
1 vote -
resolver proxy
Provide the ability to use Azure AD as a resolver proxy
1 vote -
Link Resolver API Plugins
While this would be helpful across the board, specifically with ProQuest's ownership of ExLibris it seems a logical step to add a link resolver API to increase the efficacy of the services page.
Specifically request a Proquest Link Resolver API Plugin that would allow Alma to do a pre-check to ProQuest to see if full text is available. If the pre-check API query returns 0 matches, then the Full Text Service would be suppressed and the user would see 'No Full Text' on the Services Page. This would address certain linking issues where the services page recognizes full text is…
1 vote -
Use user data in general electronic services
Currently in a general electronic service we can pass bibliographic metadata via openurl format through to the target webpage. It would be useful to also pass through user data. The "Adding a General Electronic Service" section in the Online Help mentions a requester (req.) category of attributes but these don't seem to be used at the moment.
Passing through the requester's name, email address, etc would allow us to auto-populate an external form (eg interloans, purchase suggestion forms, etc) and save the user time / potential typing errors.
0 votes -
add conditions in General Electronic Services based on ebook Collection
We request to add conditions based on ebook Collection.
We want to be able to display additional services only for records that belong to a specific collection.0 votes
- Don't see your idea?