Dean Lingley
My feedback
-
223 votesDean Lingley
supported this idea
·
-
22 votesDean Lingley
supported this idea
·
-
18 votesDean Lingley
supported this idea
·
An error occurred while saving the comment -
61 votes
An error occurred while saving the comment Dean Lingley
commented
We are looking to have the call # and physical location added to the Excel export for VE as well. I don't believe the suggestion for adding the AVA field for display applies to VE?
Dean Lingley
supported this idea
·
-
64 votesDean Lingley
supported this idea
·
-
25 votesDean Lingley
supported this idea
·
An error occurred while saving the comment Dean Lingley
commented
Ditto on this one. Trying to create a physical item set using a set of barcodes and 22,000 wouldn't match up... come to find out they all have a space stored at then end of them. Alma should fix this automatically,
-
66 votes
Thank you for posting this suggestions. We will check options to enhance users setting and let the users decide if to persist their search history
Dean Lingley
shared this idea
·
-
69 votesDean Lingley
supported this idea
·
-
24 votesDean Lingley
supported this idea
·
-
35 votesDean Lingley
supported this idea
·
-
150 votes
An error occurred while saving the comment Dean Lingley
commented
Just ran across another use for this... We set all our Hathitrust emegergency access title using material type and would like to suppress the link based on that: https://www.screencast.com/t/9sL1mzxUzZqy
There actually is the ability to create a GES based on material type now, but when you try to use that in the display logic to hide the purchase request Alma doesn't allow it. I think it is because the material type GES is item level, while the purchase request is title level so not letting them mix in display logic settings?
Dean Lingley
supported this idea
·
Dean Lingley
shared this idea
·
-
97 votes
Hello,
Thank you for raising this request.
We will check if a signed agreement is required here in order to start the analysis and then will prioritize for future acquisition.Best,
RaelDean Lingley
supported this idea
·
-
245 votes
Hello,
We have been able to establish contact with the provider and are currently discussing the details for this request.
We will keep the community informed with our progress.
Best,
RaelDean Lingley
supported this idea
·
-
298 votesDean Lingley
supported this idea
·
-
198 votesDean Lingley
supported this idea
·
-
170 votesDean Lingley
supported this idea
·
-
76 votesDean Lingley
supported this idea
·
-
40 votesDean Lingley
supported this idea
·
-
33 votesDean Lingley
shared this idea
·
-
16 votesDean Lingley
supported this idea
·
This was completed for Primo BO in May 2020. Now it needs to be implemented for Primo VE discovery harvest.
Simplify Data Reload Flow (NERS #6184)
May 2020
Previously, the Delete Data Source and Reload pipe allowed you to harvest records that had been exported since the last time the records were harvested and loaded into Primo. With this enhancement, you can retain the same date for subsequent pipe executions so that you can automatically reload the same set of harvested records.
Configuration Options
The Use Static Date field has been added to the Define Pipe page for Regular and Delete Data Source and Reload pipes. When selected, the Start harvesting files/records from field retains the date on which the pipe was first run instead of automatically changing it to the date on which the pipe was last run.