François Renaville
My feedback
21 results found
-
191 votesFrançois Renaville
supported this idea
·
-
14 votesFrançois Renaville
supported this idea
·
-
28 votes
An error occurred while saving the comment François Renaville
supported this idea
·
-
20 votesFrançois Renaville
supported this idea
·
-
84 votesFrançois Renaville
supported this idea
·
-
25 votesFranç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
·
-
32 votesFranç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
·
-
73 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
·
-
78 votesFranç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
·
-
62 votesFrançois Renaville
supported this idea
·
-
93 votesFrançois Renaville
supported this idea
·
-
47 votesFrançois Renaville
supported this idea
·
-
39 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
·
-
28 votesFrançois Renaville
supported this idea
·
-
78 votesFrançois Renaville
supported this idea
·
-
22 votes
An error occurred while saving the comment François Renaville
commented
I agree this feature would be useful for end-users.
I would like to add that customers should be able to customize by language the way months are displayed, in full (MMMM > January, February…) or in brief (MMM > Jan, Feb…).
For institutions using Alma/Primo in other languages than English, Alma should be able to support a translation for the months so that it is coherent in the letters.François Renaville
supported this idea
·
-
175 votes
An error occurred while saving the comment François Renaville
commented
Thanks! You put your finger on it, Anonymous, and are right! Codes and data are closely linked, particularly when structure and hierarchy come into the picture! Good point! I’m mortified… :-/
We recently refreshed our Standard Sandbox and have added very few data since then. There are currently more than 120,000 bibliographic records, 39 active ledgers and funds, 650 POLs, 450 users... Do we really need 120,000 bib records in the IZ Standard Sandbox? I don’t think so. I would be happy with many less; I can always import or manually add and create what I need.
Since it is true that production configuration in the Sandbox makes really sense with real data from the institution, we could consider the following scenario:
-100% of the Alma Production CONFIGURATION copied on the Standard Sandbox
- 2% of the Alma Production DATA copied on the Standard SandboxThis scenario would allow codes, etc. to match the appropriate data and make testing effective for some cases. But with a sample of 2% we can certainly not expect to always come to a correct mapping. Not difficult to imagine the problems in case of a POL is copied to the Sandbox and if the associated interested user is not part of the sample, if an invoice is copied without the associated POL, if an item has been requested by a non-copied user... There must certainly be solutions to avoid this situation, but no doubt that this would also make the whole thing much more difficult to implement… Why not only a sample of the Repository and User data that would be migrated? We can always easily create the POLs, invoices, loans, requests... we need for our tests.
Of course, there must be other possible scenarios! And upgrading to the Premium Sandbox would still make sense for institutions that need or want all their data and can pay for such additional service.
I agree with you that the usefulness of the Standard Sandbox is limited without our own data. But I find it easier to add the few data we really need for staff training, testing of setup scenarios, new enhancements, etc. rather than manually duplicating the whole Production configuration in our Sandbox.Moreover, if Ex Libris still plans to allow customers to go further in testing the Alma releases and still hopes the customers will help them to detect bugs and issues asap and if possible before the new release being implemented in the Production environments, so that we all (politically correct) "enjoy a better release experience", then it makes really sense for customers to have an understandable and meaningful configuration in their Sandbox. I cannot go very far in testing new releases with an OOTB config...
And thanks again for your relevant comments!
François Renaville
supported this idea
·
François Renaville
shared this idea
·
I completely agree! There should be a better distinction between the Main Menu and the Configuration Menu.