Difference between revisions of "Idci field"
m |
(Text not an ancestor class) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 7: | Line 7: | ||
== Inheritance == | == Inheritance == | ||
* [[Metadata]] | * [[Metadata]] | ||
| − | + | ** [[Id field]] | |
| − | + | *** [[Idci field]] | |
| − | |||
== Additional Properties == | == Additional Properties == | ||
| − | As for [[Id field# | + | As for [[Id field#Additional_Properties|Id fields]]. |
== Required Phrases == | == Required Phrases == | ||
Latest revision as of 21:49, 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 metadata field is very similar to a Id field. The main difference is that indexes the ID in a case-insensitive way, which is useful for things lik usernames and email addresses (which have their own sub-type) that often get capitalised and will work with or without capitalisation in most situations.
Inheritance
Additional Properties
As for Id fields.
Required Phrases
No additional phrases beyond those required for Id fields.
Database
Idci fields are stored in the database as
fieldname VARCHAR(255)
API
See API page.
Examples
Most basic example.
{
name => 'username',
type => 'idci',
},
