Difference between revisions of "Float field"

From EPrints Documentation
Jump to: navigation, search
 
 
(11 intermediate revisions by 5 users not shown)
Line 1: Line 1:
 +
{{fieldtypes}}
 +
 +
 +
== 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 <tt>FLOAT</tt> in the database.
 +
 +
This field is used for the latitude and longitude built in fields in [[User Object]]s and [[EPrint Object]]s.
 +
 +
The usefulness of this field will be expanded in later versions of EPrints.
 +
 +
== Inheritance ==
 
* [[Metadata]]
 
* [[Metadata]]
 
** [[Float field]]
 
** [[Float field]]
  
== Description ==
+
== Additional Properties ==
 +
No additional properties beyond a [[Metadata#Properties|standard metadata field]].
 +
 
 +
== Required Phrases ==
 +
No additional phrases beyond [[Metadata#Required_Phrases|standard metadata field phrases]].
  
== Properties ==
+
== Database ==
 +
Float fields are stored in the database as
 +
fieldname FLOAT
  
No extra properties.
+
== API ==
 +
See [[API:EPrints/MetaField/Float|API page]].
  
== Required Phrases ==
+
== Examples ==
 +
Most basic example.
 +
{
 +
    name => 'impactfactor',
 +
    type => 'float',
 +
},
 +
Limit the width of the input field.
 +
{
 +
    name => 'latitude',
 +
    type => 'float',
 +
    input_cols => 15,
 +
}

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 - 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

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,
}