Difference between revisions of "Float field"
(Moved description to top) |
|||
Line 13: | Line 13: | ||
** [[Float field]] | ** [[Float field]] | ||
− | == Properties == | + | == Additional Properties == |
− | No | + | No additional properties beyond a [[Metadata#Properties|standard metadata field]]. |
== Required Phrases == | == Required Phrases == | ||
− | No additional phrases. | + | No additional phrases beyond [[Metadata#Required_Phrases|standard metadata field phrases]]. |
== Database == | == Database == |
Latest revision as of 09:48, 9 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
Stores a floating point number (may be negative). In 3.0 there is no way to search these values. They might as well be just strings, but they are stored as FLOAT in the database.
This field is used for the latitude and longitude built in fields in User Objects and EPrint Objects.
The usefulness of this field will be expanded in later versions of EPrints.
Inheritance
Additional Properties
No additional properties beyond a standard metadata field.
Required Phrases
No additional phrases beyond standard metadata field phrases.
Database
Float fields are stored in the database as
fieldname FLOAT
API
See API page.
Examples
Most basic example.
{ name => 'impactfactor', type => 'float', },
Limit the width of the input field.
{ name => 'latitude', type => 'float', input_cols => 15, }