metadata language field vs system language field

[Natkeeran]

Currently the language field pulls the languages from the configured languages for the site. It is a system property and we are using it for metadata as well. There should be a language field for the metadata independent of the site's configured languages. This can possibly be a controlled vocabulary: https://en.wikipedia.org/wiki/List_of_ISO_639-2_codes, https://id.loc.gov/

[seth-shaw-unlv]

Our local content type has a language field to indicate the language of a resource, if that is what you mean:

field.field.node.dc_object.field_language.yml

langcode: en
status: true
dependencies:
  config:
    - field.storage.node.field_language
    - node.type.dc_object
  module:
    - languagefield
id: node.dc_object.field_language
field_name: field_language
entity_type: node
bundle: dc_object
label: Language
description: "<p>A language of the resource.</p><p>If the item includes written or spoken language, select the language used.</p>"
required: false
translatable: false
default_value: {  }
default_value_callback: ''
settings: {  }
field_type: language_field

field.storage.node.field_language.yml

langcode: en
status: true
dependencies:
  module:
    - field_permissions
    - languagefield
    - node
third_party_settings:
  field_permissions:
    permission_type: public
id: node.field_language
field_name: field_language
entity_type: node
type: language_field
settings:
  language_range:
    11: '11'
    1: 0
    12: 0
    2: 0
    site_default: 0
    und: 0
    current_interface: 0
    authors_default: 0
  included_languages: {  }
  excluded_languages: {  }
  groups: ''
  maxlength: 12
  allowed_values_function: languagefield_allowed_values
module: languagefield
locked: false
cardinality: -1
translatable: true
indexes: {  }
persist_with_no_fields: false
custom_storage: false

[Natkeeran]

@seth-shaw-unlv yes, basically another field to indicate the language of the resource.

[rangel35]

my project has a separate language field, I just call it field_dcterms_language to differentiate from field_language

[Natkeeran]

@dannylamb

Can we load this list http://id.loc.gov/vocabulary/languages.html as a taxonomy and create a reference field to point to it!

Or, we can create it as a taxonomy and leave it to the end user to populate the vocabulary.

[seth-shaw-unlv]

@Natkeeran, @dannylamb Once the vocabulary is setup it would be easy to create a CSV migration of the tabbed version; although that would slurp in all of the terms. I imagine most repositories won't have a diverse enough content set to warrant all of them. (Having a lot of unused taxonomy terms isn't the best UX.)

[seth-shaw-unlv]

We could build the framework and recipe though. Build the taxonomy and a migration aimed at a local path, then tell repository admins to download the TSV and remove the unwanted entries before migrating...

[rangel35]

any thoughts on pre-populating with some of the more common languages for our out of the box users

there must be a list of the most common languages we can use...

[seth-shaw-unlv]

Considering the global use of the software, I don't know that there is. Sure, on the North American continent we can generally assume English, French, and Spanish; the only other collection material we have here I belive is in Korean (so says my quick database search). But that is going to be very different for other areas such as Europe. I don't think we can make any assumptions here.

[rangel35]

that's true...I didn't think it all the way through :) maybe we can provide a step by step guide to how to import taxonomies in general (or do we already have that and I just haven't checked)