Float field: Difference between revisions
Added examples. Improved other sections unhide ToC. |
Moved description to top |
||
| Line 1: | Line 1: | ||
{{fieldtypes}} | {{fieldtypes}} | ||
== Description == | == Description == | ||
| Line 12: | Line 8: | ||
The usefulness of this field will be expanded in later versions of EPrints. | The usefulness of this field will be expanded in later versions of EPrints. | ||
== Inheritance == | |||
* [[Metadata]] | |||
** [[Float field]] | |||
== Properties == | == Properties == | ||
Revision as of 08:24, 21 March 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
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
Properties
No bespoke properties.
Required Phrases
No additional 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,
}