Susan Chakmakian
My feedback
28 results found
-
178 votesSusan Chakmakian supported this idea ·
-
42 votesSusan Chakmakian supported this idea ·
-
182 votesSusan Chakmakian supported this idea ·
-
2 votesSusan Chakmakian shared this idea ·
-
131 votesSusan Chakmakian supported this idea ·
-
20 votesSusan Chakmakian supported this idea ·
-
2 votesSusan Chakmakian shared this idea ·
-
4 votesSusan Chakmakian shared this idea ·
-
1 voteSusan Chakmakian shared this idea ·
-
1 voteSusan Chakmakian shared this idea ·
-
197 votes
The Purchase Request library will be supported vi SIS/API and user update job, just as the Resoruce Sharing library is.
We’ll also look into making the Purchase Request and the Resoruce Sharing library be searchable in the users advanced search option.
An error occurred while saving the comment -
3 votesSusan Chakmakian shared this idea ·
-
257 votesSusan Chakmakian supported this idea ·
-
1 voteSusan Chakmakian shared this idea ·
-
80 votesSusan Chakmakian supported this idea ·
-
8 votesSusan Chakmakian supported this idea ·
-
11 votesSusan Chakmakian supported this idea ·
-
20 votes
Some of this has already been implemented in the new UI:
Citations: instructors can no longer set specific visibility dates per item.
Sections: Sections can still be hidden/display according to the section date. No changes are planned.
Lists: List dates will not impact the list visibility starting with the May 2024 release.
Susan Chakmakian supported this idea · -
22 votesSusan Chakmakian supported this idea ·
-
55 votesSusan Chakmakian supported this idea ·
As of February 22, 2023, I also don't see an option to assign a value to the "Purchase request library" field in batch using the user update job in Alma, but I would find this functionality to be quite helpful (as I think it should limit the libraries that users can choose from when they submit a purchase request form in Primo VE).