-
Notifications
You must be signed in to change notification settings - Fork 4
Does dc_language need to be single valued? #67
Comments
No, I don't think this needs to be a single value. Good catch! |
Perhaps we were thinking about the metadata language? In our deployment, we're not using language now as everything we're indexing is in English -- we removed the language facet a while ago. |
I would say that almost everything we are indexing is in English as well, but we've come across a set of files from the China Data Center where column headers in the attribute table are in Chinese. Similarly, we're also adding some files from the Cuidad de Buenos Aires in which both the data in the attribute table and the documentation for the data is in Spanish. Even though this is an anomaly, I think it might be wise to make language a multivalued field. Other thoughts? |
👍 for multivalued... http://dublincore.org/documents/usageguide/elements.shtml#language |
Sounds ok to me. On Tue, Aug 18, 2015 at 2:22 PM, Jack Reed notifications@github.com wrote:
|
You can add dc_language_s to your catalog_controller.rb configuration. To make it multivalued, just rename the field dc_language_sm. Change the view if you want to put it in the metadata vaules. You may also want to change the Solr schema.xml to copy dc_language_sm into a text field so it gets searched.
|
Sounds good! Thanks for the help, all! |
So that can be the change in your local app, but maybe we should look at something more global to geoblacklight-schema. I'll work on putting a proposal together for a v1 schema that starts to handle these problems. |
Great, thank you! |
Just curious what the rationale for making dc_language a single instead of multivalued field is. Was thinking about this a little while accessioning some datasets that contain both English and Chinese data, and noticed that I couldn't list both languages in this schema. Not a big deal, but I am interested to hear thoughts on it.
The text was updated successfully, but these errors were encountered: