Anonymous
My feedback
40 results found
-
119 votes
Hi all,
We would like to update that we plan to add this functionality to the Primo Next Discovery Experience User Interface.
More details on the new interface planning can be found here:
Best regards,
Yael.
Anonymous supported this idea · -
69 votes
-
230 votesAnonymous supported this idea ·
-
21 votes
An error occurred while saving the comment Anonymous supported 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.
-
105 votesAnonymous supported this idea ·
-
19 votesAnonymous shared this idea ·
-
38 votesAnonymous supported this idea ·
-
23 votesAnonymous shared this idea ·
-
45 votesAnonymous supported this idea ·
-
53 votesAnonymous shared this idea ·
-
22 votesAnonymous shared this idea ·
-
129 votesAnonymous shared this idea ·
-
55 votes
-
336 votesAnonymous supported this idea ·
-
225 votesAnonymous supported this idea ·
-
54 votesAnonymous supported this idea ·
-
78 votes
-
4 votes
An error occurred while saving the comment Anonymous commentedThe check does Aleph in the time of renewal but no before and there is no kind of pre-programmed-check into the system.
Anonymous shared this idea · -
78 votes
We would like to massively change the Pattern type and Linking number fields. It can not be done either via API or with Job(Change physical items).
The purpose of these massive changes at the item level (fascicles) is the automatic creation of field 866 in the MARC record for each journal holding according to the fascicles received in Alma. In our case, it is essential to make this massive change but it can not be done via job or via API.
https://knowledge.exlibrisgroup.com/Alma/Knowledge_Articles/Create_Summary_field_866867868