-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dates displayed in search results concatenated without separator #48
Comments
Just to clarify -- are you saying there should or should not be a separator? |
There should be a separator. |
this looks like it's maybe fixed now. @arcadiafalcone can you confirm? |
@thatbudakguy I think this is still not displaying as desired but I'm not entirely sure what the desired display would be. I'll take this to Gryphon Search for discussion. |
Gryphon Search discussed concerns over the larger imprint statement and how to make it useful to users. A date separator would help to a certain extent, but wouldn't actually help the user interpret the dates displayed. A larger analysis on MODS imprint statements is probably needed, but time intensive. Arcadia also indicated that much is in flux right now, which might make analysis difficult. We'll lean on Arcadia to start analysis on the imprint statement - at the minimum to understand breadth of the issues with dates displaying in the imprint. For now, we're blocked on that larger imprint analysis. |
Adding a separator to the dates field also requires a bit of analysis to determine what types of dates might display in the imprint currently. Then ux to help determine what separator should be used (semi-colon, comma, etc.) |
Example: https://searchworks.stanford.edu/catalog?q=bh845qb8447&search_field=search&utf8=%E2%9C%93
The text was updated successfully, but these errors were encountered: