Christian
My feedback
59 results found
-
86 votes
An error occurred while saving the comment Christian
supported this idea
·
Christian
shared this idea
·
-
14 votes
-
30 votes
Hello,
We will reach out to the provider and ask for the metadata for this collection.
Thanks,
Tamar Ganor
Content Product ManagerChristian
supported this idea
·
-
53 votes
AdminTamar Ganor
(Admin, Ex Libris)
responded
Hello,
This idea has been closed by mistake, I apologize for the inconvenience.
It will be reviewed and addressed according to the regular workflow of content requests.
My sincere apologies.
Kind regards,
Tamar Ganor
Content Product Manager
Christian
supported this idea
·
-
12 votesAdminTamar Ganor
(Admin, Ex Libris)
responded
Hello,
This idea has been closed by mistake, I apologize for the inconvenience.
It will be reviewed and addressed according to the regular workflow of content requests.
My sincere apologies.
Kind regards,
Tamar Ganor
Content Product Manager
Christian
supported this idea
·
-
18 votesAdminTamar Ganor
(Admin, Ex Libris)
responded
Hello,
This idea has been closed by mistake, I apologize for the inconvenience.
It will be reviewed and addressed according to the regular workflow of content requests.
My sincere apologies.
Kind regards,
Tamar Ganor
Content Product Manager
Christian
supported this idea
·
-
15 votesAdminTamar Ganor
(Admin, Ex Libris)
responded
Hello,
This idea has been closed by mistake, I apologize for the inconvenience.
It will be reviewed and addressed according to the regular workflow of content requests.
My sincere apologies.
Kind regards,
Tamar Ganor
Content Product Manager
Christian
supported this idea
·
-
9 votesAdminTamar Ganor
(Admin, Ex Libris)
responded
Hello,
This idea has been closed by mistake, I apologize for the inconvenience.
It will be reviewed and addressed according to the regular workflow of content requests.
My sincere apologies.
Kind regards,
Tamar Ganor
Content Product Manager
Christian
supported this idea
·
-
220 votes
An error occurred while saving the comment Christian
commented
Hi,
this idea has been accepted in August 2022.
When will the implementation take place?
Will the important suggestions for improvement from our comment from 19.09.2020 also be taken into account?Thank you in advance for any further information!
Kind regards,
Christian.An error occurred while saving the comment Christian
commented
Some further improvements would be fine:
Due to short-term library closings, we also have to change the due dates for many books.
If you enter an exception (a closed day) in the Calender Management, the due dates of the books concerned are changed with a job that runs overnight. So far, so good.
But if a closed day is entered for the next day, we also use the function "Bulk Change Due Dates" to change the due dates immediately so that our users are also informed immediately (to avoid user requests) and not just as part of the overnight job.
However, the "Bulk Change Due Dates" job does not work the same as the job that runs overnight.
(1) Different behaviour:
If a book is recalled
- the "Bulk Change Due Dates" job does NOT change the due date
- the overnight job changes the due dates of recalled books as wellIdea: We would be glad to have an option to include recalled books, if wanted.
(2) Running the job:
The "Bulk Change Due Dates" job can only be executed for a single sublibrary and for all user groups (if you select none) or only for a single user group.
Sometimes we have to run the job for the whole institution or for several libraries, but only for some user groups.Idea: We would be glad to have the possibility to select several sublibraries at once or even all sublibraries (= whole institution) and also multiple user groups.
Otherwise you have to run the job multiple times and each new job can only be started if the previous job has finished.Example: We had a temporary closure of the library for some user groups only. Therefore we could not enter an exception (closed days) in the Calender Management, because this change would have affected all user groups.
So we had to run the "Bulk Change Due Dates" job in 40+ sublibraries for 5 different user groups.(3) Letters to users
Currently the "Bulk Change Due Dates" job sends one letter per borrowed book. This means that if a user has borrowed 30 books that qualified for the job, then she/he will receive 30 emails.Idea: Only one email should be send a user which includes all books from all sublibraries.
Thank you in advance!
(Note: Salesforce case #00896443)
-
74 votes
-
1 vote
An error occurred while saving the comment Christian
commented
The notes-tab also stores other "notes" that do not belong here, e.g. "Line was removed from Order PO-123456"
-
6 votes
An error occurred while saving the comment Christian
commented
Yes, please.
Unfortunately I have no more votes left ... -
6 votes
An error occurred while saving the comment Christian
commented
Hi Kylie,
see also: Add a link from the PO line to the "Receive" workbench (https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/47291660-add-a-link-from-the-po-line-to-the-receive-workb) and the comment - in the new layout of the PO Line Task List receiving is possible directly within the PO Line.
Best regards,
Christian. -
2 votes
An error occurred while saving the comment Christian
commented
Hi,
you can set parameters like "User group" for "Booking" fulfillment unit rules or have i misunderstood this idea?
Christian. -
20 votes
An error occurred while saving the comment Christian
commented
In the new layout of the PO Line Task List receiving is possible directly within the PO Line.
1. Open the PO Line in "Edit" mode
2. Go to "Ordered items" section
3. Click the ellipsis menu ("...") and choose "Receive" -
25 votesChristian
supported this idea
·
An error occurred while saving the comment Christian
commented
A note about the CSS work-a-round:
When you open the "full view" of a record the HTML code for this pages looks like:
<body class="md-dialog-is-showing" ...>
<primo-explore>
<prm-report-problem>
Due to a CSS directive the "Feedback" dialog is displayes.However, when you reload such a "full view" page, the HMTL codes changes to:
<body>
<primo-explore>
<prm-report-problem>
Now the class "md-dialog-is-showing" and the CSS directive does not work anymore and the "Give us Feedback" section is not displayed.
The work-a-round does not work in this case.Please provide us a solution via the Primo backend (Primo BO) where we can define on which pages in Primo the "Feedback" dialog should be displayed.
Thank you in advance!An error occurred while saving the comment Christian
commented
It is the same with us, also we have only one option active ('Report a broken link'), because we currently use another tool for general user requests. So the feedback option only makes sense in the full display, but Ex Libris support told us that this configuration possibility is not planned for the near future.
Therefore, currently we control the display resp. non-display via CSS:/* Generally do not show the 'Feedback tool' ... */
prm-report-problem {
visibility: hidden;
}
/* ... but show it only on the Full Display screen (desktop view) ... */
body.md-dialog-is-showing prm-report-problem,
prm-full-view-page prm-report-problem {
visibility: visible;
}
/* ... and also on mobile devices (not only in 'landscape mode') ... */
body.md-dialog-is-showing prm-report-problem div.report-container button#reportProblem,
prm-full-view-page prm-full-view-page prm-report-problem {
display: block;
}
/* ... but do not show it in top menu ('...' menu) */
body.md-dialog-is-showing primo-explore.background-dark prm-report-problem {
visibility: hidden;
}
div button.report-problem-menu-mobile {
display: none;
} -
184 votes
An error occurred while saving the comment Christian
commented
Please see also: Enable customization of Receive New Material columns
https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/20588140-enable-customization-of-receive-new-material-colum
Our colleagues are also missing columns in this list (like Vendor information).Christian
shared this idea
·
-
72 votes
An error occurred while saving the comment Christian
commented
Addendum:
The idea made it to the 2nd round of NERS 2023 voting, but then did not receive enough votes to be implemented.Attached the implementation plans discussed with Ex Libris (8212-solution with images.docx) and two notes:
(1) Side effect: Have all identifiers on the PO line ("Preferred" and "Proposed Identifiers") be searchable in the Receiving workbench.
(2) Additional information for an identifier like (hardcover : alk. paper):
Our colleagues would be pleased if this information could be printed on the order letters. Correctly this information is stored in subfield $c. Sometimes it is stored in subfield $a but this is not common practice.https://www.loc.gov/marc/bibliographic/bd020.html
020 - International Standard Book Number (R)
$a - International Standard Book Number (NR)
$c - Terms of availability (NR)
$q - Qualifying information (R)https://www.loc.gov/marc/bibliographic/bd024.html
024 - Other Standard Identifier (R)
$a - Standard number or code (NR)
$c - Terms of availability (NR)
$q - Qualifying information (R)https://www.loc.gov/marc/bibliographic/bd028.html
028 - Publisher or Distributor Number (R)
$a - Publisher or distributor number (NR)
$b - Source (NR)
$q - Qualifying information (R)Ideally the content of subfield $c and $q will be stored in the XML field <type> under the node <meta_data_values>.
And if subfield $a contains not only the identifier, Ex Libris "splits" the content:
- identifier ... goes to <identifier>
- and the rest ... goes to <type>Christian
shared this idea
·
-
53 votesChristian
shared this idea
·
-
24 votes
An error occurred while saving the comment Christian
commented
Note: this is not only a Primo VE issue. It is also relevant for the 'classic' Primo UI.
Christian
supported this idea
·
@Analytics Product Management:
The idea currently has two-thirds of the votes of the original idea. We hope this is enough to show that the fields are also important in Analytics.
Thank you very much in advance!