Kristen Fredericksen
My feedback
16 results found
-
9 votes
An error occurred while saving the comment Kristen Fredericksen
supported this idea
·
-
5 votesKristen Fredericksen
supported this idea
·
-
11 votesKristen Fredericksen
shared this idea
·
-
8 votesKristen Fredericksen
supported this idea
·
-
31 votes
An error occurred while saving the comment Kristen Fredericksen
commented
Yes, this would be very useful for Primo VE discovery import profiles as well. This feature would be especially valuable for consortia like CUNY, where the number of sets can run into the hundreds.
Kristen Fredericksen
supported this idea
·
-
58 votesKristen Fredericksen
supported this idea
·
-
15 votesKristen Fredericksen
supported this idea
·
-
26 votes
An error occurred while saving the comment Kristen Fredericksen
commented
Strongly in favor of this Idea. At one of our campuses, each piece of equipment—like an iPad—was originally cataloged with its own bib, holdings, and item record. After some cleanup, we were able to consolidate everything so that all equipment items now share a single bib record. However, each item is still attached to its own separate holdings record, even though the call numbers and locations are identical. What we really need is the ability to merge those holdings so that all items can sit under a single bib and a single holdings record, with individual item records as expected. Right now, Alma only allows us to move items between holdings attached to the same bib record, and it doesn’t offer a way to merge holdings. This creates unnecessary clutter and complicates maintenance.
Kristen Fredericksen
supported this idea
·
-
60 votesKristen Fredericksen
supported this idea
·
-
29 votes
An error occurred while saving the comment Kristen Fredericksen
commented
I don't have enough votes to support this, but it would be so helpful. It is time consuming to change each expiry date manually, especially since the screen refreshes after every change. That means a lot of scrolling.
-
9 votesKristen Fredericksen
supported this idea
·
-
2 votesKristen Fredericksen
shared this idea
·
-
78 votesKristen Fredericksen
supported this idea
·
-
83 votesKristen Fredericksen
supported this idea
·
-
106 votesKristen Fredericksen
shared this idea
·
-
114 votesKristen Fredericksen
supported this idea
·
The CUNY consortium runs discovery import profiles for Springshare products, ArchivesSpace, JSTOR Digital Stewardship Services, and our institutional repository (Academic Works) across multiple IZs plus the NZ. Because OAI sources don't propagate deletions through incremental harvests, we have to manually open each profile, edit the Harvest Start Date, and trigger "Reload and Delete" on a recurring basis — that's dozens of profiles touched by hand every cycle.
Exposing two things on /almaws/v1/conf/md-import-profiles/{id} would close this entirely:
1. Read/write access to the OAI Harvest Start Date.
2. A ?op=run&mode=reload_and_delete (or equivalent) on the profile or its linked job.
Today the API returns only profile metadata (name, type, active) — none of the harvest controls — so there's no programmatic path at all.