-
Notifications
You must be signed in to change notification settings - Fork 28
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
Title as multivalued field #127
Comments
Actually, there can be more than one title. See the screenshots I've attached 😄 The question is whether we want to pretend like this can't be the case. It seems like sorting on title is a more typical and compelling use case than having more than one title. We'll talk about this and see what we think. Thanks for bringing it to our attention. |
You're right : it can. But in my case : it won't :D. Making a title a multivalue field in Omeka seems to be an odd choice to me in the first place anyway, but well. I changed the value in schema.xml and it appears to be harmless. My sorting works. Thanks for your quick answer. Have a nice day. |
I'm going to open this back up. I think this is an important use case that we need to consider supporting. No promises yet, but I'd like to keep it in mind. Thanks, |
Hi and thanks for your work on this plugin.
I would like to propose result sorting, mainly on the title field.
For some reason, it's defined as a multivalued field in schema.xml, and don't see why. It prevents passing a parameter like "sort title asc"
As I understand it, the title field in Omeka will never have multiple values, so could you tell me if it's safe to reconfigure my Solr instance with this parameter set to "false" ?
Any other solution would of course also be fine.
The text was updated successfully, but these errors were encountered: