Difference between revisions of "Id field"
(Added structure to page) |
m |
||
Line 10: | Line 10: | ||
*** [[Id field]] | *** [[Id field]] | ||
− | == Properties == | + | == Additional Properties == |
− | + | As for [[Text field#Additional_Properties|Text fields]]. | |
== Required Phrases == | == Required Phrases == | ||
− | No additional phrases. | + | No additional phrases beyond those required for [[Text field#Required_Phrases|Text fields]]. |
== Database == | == Database == |
Revision as of 09:50, 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
This metadata field is very similar to a Text field, the main difference is for search where the whole value is indexed rather than in individual parts. In particular this is useful for things like ISBN or ISSN numbers which contain hyphens (-). For a text field the parts either side of the hyphen would be indexed separately but for a Id field this will be indexed as a single value. Therefore, allowing search to find only those items that match exactly.
Inheritance
Additional Properties
As for Text fields.
Required Phrases
No additional phrases beyond those required for Text fields.
Database
Id fields are stored in the database as
fieldname VARCHAR(255)
API
See API page.
Examples
Most basic example.
{ name => 'isbn', type => 'id', },
Use a bespoke value renderer to add links to DOIs where appropriate.
{ name => 'id_number', type => 'id', render_value => 'EPrints::Extras::render_possible_doi', },