Difference between revisions of "Langid field"
m (→Database) |
(→Additional Properties) |
||
Line 11: | Line 11: | ||
== Additional Properties == | == Additional Properties == | ||
− | As for [[Set field#Additional Properties|Set fields]] | + | As for [[Set field#Additional Properties|Set fields]]. |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== Required Phrases == | == Required Phrases == |
Revision as of 08:07, 12 April 2023
EPrints 3 Reference: Directory Structure - Metadata Fields - Repository Configuration - XML Config Files - XML Export Format - EPrints data structure - Core API - Data Objects
Metadata Fields: Arclanguage - Base64 - Bigint - Boolean - Compound - Counter - Dataobjref - Date - Decimal - Email - Fields - Float - Id - Idci - Image - Int - Itemref - Keywords - Langid - Longtext - Longtext_counter - Multilang - Multipart - Name - Namedset - Pagerange - Recaptcha - Recaptcha3 - Relation - Search - Secret - Set - Storable - Subject - Subobject - Text - Time - Timestamp - Url - Uuid
Contents
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.
Required Phrases
No additional phrases beyond those required for Set fields.
Database
Langid fields are stored in the database as
fieldname VARCHAR(255)
API
See API page.
Examples
Most basic example.
{ 'name' => 'language', 'type' => 'langid', }