Erin Grant
My feedback
18 results found
-
128 votes
-
72 votes
-
85 votes
-
3 votes
An error occurred while saving the comment -
88 votes
-
165 votes
Dear all,
Thank you for sharing this idea.
I have read it carefully, and would like to make sure that I understand it:
Current situation:
There are several processes in PO line workflow which add automatic internal notes, for example:
- Renewal ("PO Line has been renewed automatically on…")
- Moving PO line out of PO (""Line was removed from Order ...")
- other.
Desired outcome:
Have a configurable option to disable these notes from being created. Each of these processes is/will be saved in the PO line history.
Please let me know if this understanding is correct.
Thanks,
Zohar Shemesh
Alma product team
-
122 votes
-
46 votes
-
97 votes
-
209 votes
-
427 votes
-
66 votes
-
106 votes
-
98 votes
-
70 votes
-
108 votes
-
64 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).
-
92 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.
My colleague created a Requests report for this use case as an Analytics workaround. This uses the theory that work orders create a Request. We would like to know if this work order -> request behavior is accurate, and if this Requests report would provide accurate work order info.