Difference between revisions of "Langid field"
(Amended structure to standardise for metadata field type.) |
m (→Database) |
||
Line 25: | Line 25: | ||
== Database == | == Database == | ||
Langid fields are stored in the database as | Langid fields are stored in the database as | ||
− | fieldname | + | fieldname VARCHAR(255) |
== API == | == API == |
Revision as of 13:30, 11 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 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 VARCHAR(255)
API
See API page.
Examples
Most basic example.
{ 'name' => 'language', 'type' => 'langid', }