Settings and activity
22 results found
-
30 votes
Mary Horman supported this idea ·
-
8 votes
The product team will review this idea for consideration for a future release.
Mary Horman shared this idea ·
-
21 votes
Mary Horman supported this idea ·
-
15 votes
An error occurred while saving the comment Mary Horman supported this idea ·
-
13 votes
This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
Mary Horman supported this idea ·
-
23 votes
The product team will review this idea for consideration for a future release.
Mary Horman supported this idea ·
-
55 votes
Mary Horman supported this idea ·
-
11 votes
Mary Horman supported this idea ·
-
58 votes
Mary Horman supported this idea ·
-
56 votes
Mary Horman supported this idea ·
-
22 votes
Mary Horman supported this idea ·
-
13 votes
Mary Horman supported this idea ·
-
32 votes
Mary Horman supported this idea ·
-
18 votes
Mary Horman supported this idea ·
-
17 votes
Mary Horman supported this idea ·
-
22 votes
Mary Horman shared this idea ·
-
17 votes
Mary Horman shared this idea ·
-
62 votes
Mary Horman supported this idea ·
-
27 votes
Mary Horman supported this idea ·
-
25 votes
Mary Horman supported this idea ·
We have discovered that when we have a name that appears transliterated on the cover, but the name in the authority file is not transliterated, (For example, Dyanchenko on the book cover and Di︠a︡chenko in the authority record) that when the patron searches Dyanchenko (on book cover!) the result in Vega is, rather unhelpfully, a very small "did you mean Diachenko?" The authority record in Sierra has Dyachenko as an alternate spelling in a 400 field, so that it would be hoped that Vega would map to Dyanchenko as an alternate spelling, if indeed authority data was ingested into Vega.