Erin Grant
My feedback
17 results found
-
391 votes
-
140 votes
Dear Customers,
I'm happy to inform you that the capability to schedule manual jobs is planned to be released in May 2024 Release.
Thanks,
Uri Beladev
Product Manager
An error occurred while saving the comment -
201 votes
-
345 votes
Hi all,
This is to update that we plan to develop this option in the future. It is not in the current roadmap for this year, and we will update as soon as we have more details about the development planning.
Best regards,
Yael.
An error occurred while saving the comment There are so many different kinds of links - some useful/some not, some institution-specific/some not, etc. - in 856 in both P and E records. A greater ability for customers to customize their display at the IZ level using indicators (especially 2nd), regexp, or (preferably) a mix of both is absolutely CRUCIAL for user experience. We can't just throw 4-8 links of varying usefulness and applicability to users for every resource. There are some links (e.g. to archival finding aids on P records) that we need to display to users, but we don't want them lost in a sea of other links. An all-or-nothing link display approach is just not robust enough for most institutions in this regard. Please, please, please develop a way for institutions to more selectively display these links.
-
419 votes
-
64 votes
-
45 votes
-
245 votes
Hello all,
As planned, we are moving forward with this ingestion. You will see a zero-title database in the KBs, as we work towards indexing this content in CDI.
Best,
Rael
An error occurred while saving the comment This would be a big help.
-
104 votes
-
99 votes
-
68 votes
-
220 votes
We have added it to our plan. We will share more details as part of the design phase
-
108 votes
-
90 votes
-
190 votes
Dear community,
Thank you for raising this idea.
I would like to better understand the use case here:
1 How often such check is done? if this is a "cleanup" that is done once in a few month, for example, perhaps an analytics report would be sufficient?
2 In the description you wrote about the "has inventory" index. Can you give more details, why it is not useful for the described use case?
Thanks,
Tamar Fuches
Alma product team
-
68 votes
An error occurred while saving the comment That's a good point, Luigi. I have a few cases open about publishing profiles, and will add that detail to one of them. In the past at a prior institution when we had a similar problem exporting bibs that exceeded the maximum MARC record file size, the case was closed and we were told that this would need to be an enhancement (link to idea: https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/18740719-add-validating-marc-field-and-record-character-lim).
-
88 votes
An error occurred while saving the comment For more context, when a work order is created, the Item Record History tab tracks the date the item was scanned into the work order and the date the work order was removed (“doned”). However, the Item Record History tab does not:
1. Indicate the name of the work order type and status that was used. (All that shows is the generic “In Process”)
2. Track when the item was moved from one status to another within a work order.
We use work order statuses to advance items in a workflow within a department, changing the status as appropriate. For example, we might change the status from “In Acquisitions” to “In Copy Cataloging” or “In Original Cataloging”. It would be helpful if the Item Record history tab a) recorded what department work order was used and b) reflected the date the work order status was changed, so that if an item goes missing within a department, we can track when the status was changed.
This would help us as well. We need to regularly run a bib norm process to add a local field to IZ records in order for them to display in Primo VE with the correct resource type. We don't have bandwidth or enough staff expertise for scripting something using the API, or to do the same every time we need to regularly run a manual-only job/process.