⧼vector-jumptocontent⧽

Langid field: Difference between revisions

From EPrints Documentation
No edit summary
Amended structure to standardise for metadata field type.
Line 1: Line 1:
{{fieldtypes}}
{{fieldtypes}}


== Inherritance ==


== Description ==
This field is like a [[Set field]] but intended for providing language ID options where phrases can be provided by existing <tt>languages_typename_LANGID</tt> phrases.
== Inheritance ==
* [[Metadata]]
* [[Metadata]]
** [[Set field]]
** [[Set field]]
*** [[Langid field]]
*** [[Langid field]]


== Description ==
== Additional Properties ==
 
As for [[Set field#Additional Properties|Set fields]] except for
== Properties ==
 
As for [[set field]]s with the following differences...


{| border="1" cellpadding="3" cellspacing="0"
{| border="1" cellpadding="3" cellspacing="0"
Line 17: Line 17:
|-
|-
| '''input_style''' || short || ''as for [[set field]] but with a different default.''
| '''input_style''' || short || ''as for [[set field]] but with a different default.''
|-
|}
|}


== Required Phrases ==
== Required Phrases ==
No additional phrases beyond those required for [[Set field#Required_Phrases|Set fields]].
== Database ==
Langid fields are stored in the database as
  fieldname LONGTEXT
== API ==
See [[API:EPrints/MetaField/Langid|API page]].
== Examples ==
Most basic example.
{
    'name' => 'language',
    'type' => 'langid',
}

Revision as of 22:27, 10 April 2023


Description

This field is like a Set field but intended for providing language ID options where phrases can be provided by existing languages_typename_LANGID phrases.

Inheritance

Additional Properties

As for Set fields except for

name default description
input_style short as for set field but with a different default.

Required Phrases

No additional phrases beyond those required for Set fields.

Database

Langid fields are stored in the database as

 fieldname LONGTEXT

API

See API page.

Examples

Most basic example.

{
    'name' => 'language',
    'type' => 'langid',
}