Natalee
My feedback
17 results found
-
391 votesNatalee supported this idea ·
-
201 votesNatalee supported this idea ·
An error occurred while saving the comment -
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.
Natalee supported this idea · -
420 votesNatalee supported this idea ·
-
226 votes
Dear all, we are currently looking into the possibility of a re-design of the quick cataloging functionality - we will take this request into consideration as part of this future change.
Natalee supported this idea · -
163 votesNatalee supported this idea ·
-
221 votes
The core user record will have a field for selecting a preferred pronoun. The options will be from a configurable drop down such as:
- he, him, his
- she,her,hers
The field will be updatable from:
- Alma form
- SIS
- API
- Primo (VE)
The preferred pronoun will in the Manage Fulfillment Options screen.
It will be possible to locally override this field without overriding from the SIS, like other fields allow (such as user group).
Natalee supported this idea · -
190 votes
Dear community,
Thank you for raising this idea.
I would like to better understand the use case here:
1 How often such check is done? if this is a "cleanup" that is done once in a few month, for example, perhaps an analytics report would be sufficient?
2 In the description you wrote about the "has inventory" index. Can you give more details, why it is not useful for the described use case?
Thanks,
Tamar Fuches
Alma product team
Natalee supported this idea · -
4 votesNatalee supported this idea ·
-
125 votesNatalee supported this idea ·
-
64 votesNatalee supported this idea ·
-
58 votesNatalee supported this idea ·
-
19 votesNatalee supported this idea ·
-
63 votes
-
57 votesNatalee supported this idea ·
-
51 votesNatalee supported this idea ·
-
78 votesNatalee supported this idea ·
Adding 630 fields to the Subject Browse search would be useful for patrons. 630 fields are already included in the Advanced Search (subject contains, is exact, starts with). Most patrons won’t know that 630 fields are excluded from the Subject Browse search. Including 630 subject fields in both keyword and browse searching would provide a more consistent user experience. Other library catalogs, including the Library of Congress catalog, include 630 fields in subject browse searches. The 630 field is the Subject Added Entry—Uniform Title field, and is defined as “A preferred title used as a subject access point”--https://www.oclc.org/bibformats/en/6xx/630.html [oclc.org]
Here are a few examples:
630 00 $a Aesop's fables.
630 00 $a Arabian nights.
630 00 $a Beowulf $x Authorship.
630 00 $a Bible. $pActs $vCommentaries.
630 00 $a Bible. $pNew Testament.
630 00 $a Chanson de Roland $x Criticism, Textual.
630 00 $a New York times $v Indexes.
630 00 $a Qu'ran.
Additionally, complex subject headings can be challenging to get right in a keyword search. Browse searching can make it easier for patrons to find information on the topics they are researching. Finding books on biblical passages is easier with browse searching.
The format for biblical passage subjects is:
Bible—Book--Chapter in Roman numerals--Verse(s) in Arabic numerals.
Example:
Bible.--Luke, XV, 11-32--Relation to Genesis.