François Renaville
My feedback
36 results found
-
141 votesFrançois Renaville supported this idea ·
-
254 votesFrançois Renaville supported this idea ·
-
763 votes
This improvement is planned for the 2024 Roadmap.
François Renaville supported this idea · -
25 votesFrançois Renaville shared this idea ·
-
28 votes
An error occurred while saving the comment François Renaville supported this idea · -
20 votesFrançois Renaville supported this idea ·
-
81 votesFrançois Renaville supported this idea ·
-
327 votes
An error occurred while saving the comment François Renaville commentedThanks for the update!
If I'm not mistaken, the new colors with the January 2020 release are still at the institutional level. So, there is no possibility (or not yet?) for staff user to define their own Color Theme, which is important in terms of Accessibility since color experience may be very different from one individual to another.
Please correct me if I'm wrong.
Kind regards,Fr.
An error occurred while saving the comment François Renaville commentedThank you!
An error occurred while saving the comment François Renaville commentedUpdate: with the November 2017 release, we can now select one of 11 basic colors! Well, everything seems to be going in the right direction...
François Renaville shared this idea · -
31 votesFrançois Renaville supported this idea ·
-
7 votesFrançois Renaville supported this idea ·
-
794 votes
Thanks for the examples - we will review them and discuss our options.
Best,
Tamar
François Renaville supported this idea · -
32 votesFrançois Renaville supported this idea ·
-
5 votesFrançois Renaville supported this idea ·
-
197 votes
The Purchase Request library will be supported vi SIS/API and user update job, just as the Resoruce Sharing library is.
We’ll also look into making the Purchase Request and the Resoruce Sharing library be searchable in the users advanced search option.
François Renaville shared this idea · -
81 votes
An error occurred while saving the comment François Renaville commentedI support this very much!
François Renaville supported this idea · -
70 votes
An error occurred while saving the comment François Renaville commentedHi Rosemary,
Several messages related to this topic were posted on the Alma list in January 2018.
Subject: "ACQ: Interested In letter for e-books -- way to include URL?"
https://exlibrisusers.org/private/alma/2018-January/François
An error occurred while saving the comment François Renaville commentedHi Rosemary,
Some customers added a URL to their Interested In letter. It might not be exactly what you need, but it takes a user to the appropriate MMS ID in Primo (deep link). The MMS ID was added in the XML outpout some months ago.
Example for the Classsic UI:
<a><xsl:attribute name="href">https://<BASE_URL>.exlibrisgroup.com/primo-explore/search?tab=default&vid=YOUR_VIEW_ID&query=any,exact,"<xsl:value-of select= '/notification_data/mms_id' />"</xsl:attribute> <xsl:value-of select="notification_data/title"/></a>Example for the New UI:
<a><xsl:attribute name="href">https://<BASE_URL>.exlibrisgroup.com/primo_library/libweb/action/search.do?fn=search&ct=search&initialSearch=true&mode=Basic&tab=default_tab&indx=1&dum=true&srt=rank&vid=YOUR_VIEW_ID&frbg=&vl%28362751202UI1%29=all_items&vl%281UI0%29=contains&vl%28freeText0%29=<xsl:value-of select= '/notification_data/mms_id' /></xsl:attribute> <xsl:value-of select="notification_data/title"/></a>François Renaville supported this idea · -
37 votes
An error occurred while saving the comment François Renaville commentedVery nice that this is already effective! Thanks for updating, Myriam.
I had a look at your SF case. Support should not have advised you to put it on Idea Exchange if this was already planned for the December release. Weird... -
4 votes
An error occurred while saving the comment François Renaville commentedI agree that deleting unused obsolete pipes or at least hiding pipes that are very little used (like DELETE or DELETE_RELOAD), for example in the same way it works on http://status.exlibrisgroup.com, would be of great help for Primo administrators!
-
78 votesFrançois Renaville supported this idea ·
-
103 votes
An error occurred while saving the comment François Renaville commentedSure! Let's be ambitious! ;-)
An error occurred while saving the comment François Renaville commentedVery nice! However, not all PCI articles are real articles: many other resource types are identified as articles (most probably already in the provided sources). Therefore, excluding records based only on the resource type can also remove ‘useful’/’meaningful’ records from discovery. I would prefer a solution in Primo BO:
(1) that combines indexes, search options, operators and search terms:
- Exclude records where TITLE contains phrase “table of contents” AND where COLLECTION is “proquest”
--> To avoid this: https://www.screencast.com/t/6e0DPbyRu- Exclude records where TITLE is exactly “JAMA” AND where COLLECTION is (“crossref” OR “jama”) AND where resource type is “article”
-->To avoid this https://www.screencast.com/t/nsLRvnYH- Exclude records where TITLE is exactly “Index Volume” AND where COLLECTION “sciversesciencedirect_elsevier” AND where resource type is “article”
--> To avoid this https://www.screencast.com/t/rIr3QAZIp(2) and that allows to remove/suppress PCI records based on the PCI IDs (= list of excluded records)
François Renaville supported this idea ·
I completely agree! There should be a better distinction between the Main Menu and the Configuration Menu.