Rebecca Bearden
My feedback
7 results found
-
22 votesRebecca Bearden supported this idea ·
An error occurred while saving the comment -
15 votesRebecca Bearden shared this idea ·
-
35 votesRebecca Bearden supported this idea ·
-
528 votes
Dear community, as part of the ongoing UX improvements in Alma, the "Receive new material" screen (aka Receiving WB) is planned to be refactored and support the need described in this idea. For more information see Alma roadmap:
Thanks,
Noam Fass | Alma product team
An error occurred while saving the comment Rebecca Bearden commentedTo be clear, this is for continuous receiving.
Rebecca Bearden supported this idea ·An error occurred while saving the comment Rebecca Bearden commentedReceiving workbench should be the most logical place to have an Open Expected Items button when you run out of predicted items. An option to withdraw expected items on the receiving workbench should also be available if during receipt the receiving operator becomes aware that an issue will not be published.
-
26 votesRebecca Bearden supported this idea ·
An error occurred while saving the comment Rebecca Bearden commentedIn the new UI, the location of the receiving note is up in the far right and is very easy to not notice. Even if it stays where its located, making it a bright color, or treating it like a pop up notice like routing and binding if something is written in it would help bring attention to it during the receiving process!
-
217 votes
A new task will be added to the tasks widget, alerting catalogers when reminders' date arrives.
An error occurred while saving the comment Rebecca Bearden commentedI agree that this would be a great enhancement to reminders. Perhaps they could show up on the task list?
Rebecca Bearden supported this idea · -
161 votesRebecca Bearden supported this idea ·
We have encountered this issue as well. The workaround solution is that you can export your portfolios using the extended export, wipe this non-editable field out and reimport the portfolios. However, the search index in Alma pulls from both the non-editable field (Parser parameters field) AND the Static URL field, so if you do not remove the parser parameter URLs via the process I just described, and you are trying to search in Alma for errors/updates needed in the URL field for a group of portfolios, the task is near impossible since you keep getting the outdated URL's results as well. Bottom line: each unique URL field should be separately indexed in Alma.