Knut A Bøckman
My feedback
23 results found
-
115 votes
An error occurred while saving the comment Knut A Bøckman supported this idea ·
-
9 votes
An error occurred while saving the comment Knut A Bøckman commented
Thank you for raising this. I'd like to extend this idea to:
a) also take account for 008 pos6 "r" for reprint. An edition from 2015 but reprinted in 2028 should, according to M21 standard have pos6 "r", "2018" in pos7-10, and "2015" in pos11-14. Now only 2018 is displayed, which is incorrect for publication year in these cases.
b) not restrict this correction to facets, but also to the Primo VE addata section, which is being used in Citation services in Primo. In this case, too, the addata/date field is :
"date" : [ "2018 - 2015"], as if it was a serial, perhaps, but Citation services only takes the four first digits, i.e. 2018, instead of the publication year,Knut A Bøckman supported this idea ·
-
9 votes
Knut A Bøckman shared this idea ·
-
17 votes
-
8 votes
Knut A Bøckman supported this idea ·
-
36 votes
Knut A Bøckman supported this idea ·
-
23 votes
Knut A Bøckman supported this idea ·
-
257 votes
Knut A Bøckman shared this idea ·
-
40 votes
An error occurred while saving the comment Knut A Bøckman commented
Agreed, and this information should also be available for intra-institutional transit (e.g., from one library to another, or to a work order department). Currently, the available elements are calculated_destination_name and delivery_address, both of which are populated with the destination library name only. We would like to be able to display the address information that is already in place in Alma.
Knut A Bøckman supported this idea ·
-
211 votes
Knut A Bøckman supported this idea ·
-
22 votes
Knut A Bøckman supported this idea ·
-
18 votes
An error occurred while saving the comment Knut A Bøckman commented
So here's an idea of how this could be done: on locations of type, say "Closed" and "Remote Storage" (or any type not "Open") have a check box to indicate if call number should be displayed or not. No end user will need to know the call number of items in such locations.
Knut A Bøckman supported this idea ·
Knut A Bøckman shared this idea ·
-
19 votes
Knut A Bøckman supported this idea ·
-
43 votes
-
30 votes
Knut A Bøckman shared this idea ·
-
760 votes
Knut A Bøckman supported this idea ·
An error occurred while saving the comment Knut A Bøckman commented
Excellent idea, and convincingly argued. Thanks for posting; there went my last votes (only 2, unfortunately)
-
28 votes
An error occurred while saving the comment Knut A Bøckman commented
Thank you for creating this idea - it will be a great improvement
Knut A Bøckman supported this idea ·
-
74 votes
Knut A Bøckman supported this idea ·
-
41 votes
Knut A Bøckman shared this idea ·
-
27 votes
An error occurred while saving the comment Knut A Bøckman commented
Lesli, you're absolutely correct about the location "external name", of course. Thanks for helping! :)
I'll modify the idea to allow the same for libraries and, most importantly, to let such external names be available to the Discovery-Admin role, e.g. in Discovery Labels table.Knut A Bøckman supported this idea ·
Knut A Bøckman shared this idea ·
A job like this would be very helpful - when can we see it implemented?