François Renaville
My feedback
27 results found
-
166 votes
François Renaville supported this idea ·
-
17 votes
AdminTamar Ganor (Admin, Ex Libris) responded
Hello,
This idea has been closed by mistake, I apologize for the inconvenience.
It will be reviewed and addressed according to the regular workflow of content requests.
My sincere apologies.
Kind regards,
Tamar Ganor
Content Product Manager
François Renaville supported this idea ·
-
61 votes
AdminTamar Ganor (Admin, Ex Libris) responded
Hello,
This idea has been closed by mistake, I apologize for the inconvenience.
It will be reviewed and addressed according to the regular workflow of content requests.
My sincere apologies.
Kind regards,
Tamar Ganor
Content Product Manager
François Renaville supported this idea ·
-
38 votes
AdminTamar Ganor (Admin, Ex Libris) responded
Hello,
This idea has been closed by mistake, I apologize for the inconvenience.
It will be reviewed and addressed according to the regular workflow of content requests.
My sincere apologies.
Kind regards,
Tamar Ganor
Content Product Manager
François Renaville supported this idea ·
-
55 votes
AdminTamar Ganor (Admin, Ex Libris) responded
Hello,
This idea has been closed by mistake, I apologize for the inconvenience.
It will be reviewed and addressed according to the regular workflow of content requests.
My sincere apologies.
Kind regards,
Tamar Ganor
Content Product Manager
François Renaville supported this idea ·
-
67 votes
AdminTamar Ganor (Admin, Ex Libris) responded
Hello,
This idea has been closed by mistake, I apologize for the inconvenience.
It will be reviewed and addressed according to the regular workflow of content requests.
My sincere apologies.
Kind regards,
Tamar Ganor
Content Product Manager
François Renaville supported this idea ·
-
196 votes
François Renaville supported this idea ·
-
18 votes
François Renaville supported this idea ·
-
28 votes
An error occurred while saving the comment François Renaville supported this idea ·
-
20 votes
François Renaville supported this idea ·
-
84 votes
François Renaville supported this idea ·
-
25 votes
François Renaville supported this idea ·
-
797 votes
Thanks for the examples - we will review them and discuss our options.
Best,
Tamar
François Renaville supported this idea ·
-
34 votes
François Renaville supported this idea ·
-
79 votes
An error occurred while saving the comment François Renaville commented
I support this very much!
François Renaville supported this idea ·
-
79 votes
An error occurred while saving the comment François Renaville commented
Hi 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 commented
Hi 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 ·
-
76 votes
François Renaville supported this idea ·
-
103 votes
An error occurred while saving the comment François Renaville commented
Sure! Let's be ambitious! ;-)
An error occurred while saving the comment François Renaville commented
Very 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 ·
-
65 votes
François Renaville supported this idea ·
-
97 votes
François Renaville supported this idea ·
I completely agree! There should be a better distinction between the Main Menu and the Configuration Menu.