Difference between revisions of "Namedset field"
m (→Additional Properties) |
|||
(11 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
− | + | {{fieldtypes}} | |
− | + | ||
− | |||
== Description == | == Description == | ||
+ | This field allows a choice from a set of options like a [[Set field]]. However, here the options can be defined within a namedset file rather than under the <tt>options></tt> attribute of the field configuration. This makes it easier to update the available options, potentially programmatically. | ||
+ | |||
+ | This field offers a halfway house between a [[Set field]] and a [[Subject field]]. Being more easily re-configurable that the former whilst less complex than the latter. | ||
− | == | + | == Inheritance == |
+ | * [[Metadata]] | ||
+ | ** [[Id field]] | ||
+ | *** [[Text field]] | ||
+ | **** [[Set field]] | ||
+ | ***** [[Namedset field]] | ||
− | As for [[ | + | == Additional Properties == |
+ | As for [[Set field#Additional_Properties|Set fields]] except for: | ||
{| border="1" cellpadding="3" cellspacing="0" | {| border="1" cellpadding="3" cellspacing="0" | ||
− | + | ! Name !! Default Value !! Required !! Description !! Notes | |
|- | |- | ||
− | | '''set_name''' || n/a | + | | '''set_name''' || n/a || YES || Specifies the filename of the namedset file. || |
|- | |- | ||
− | | '''options''' || undef || ... | + | | '''options''' || <tt>undef</tt> || NO || Options from which to choose. || NOT inherited from [[Set field]]. Options provided by namedset file defined in <tt>set_name</tt>. |
|} | |} | ||
== Required Phrases == | == Required Phrases == | ||
+ | No additional phrases beyond those required for [[Set field#Required_Phrases|Set fields]]. However, you may need to add phrases for some or all the values on the namedset file, depending on whether this is a bespoke namedset file. These will take the form: | ||
+ | namedset_filename + "_typename_" + value | ||
+ | For example for <tt>[[lib/namedsets/]]</tt>'s <tt>security</tt> file, the phrase for <tt>staffonly</tt> has the ID: | ||
+ | security_typename_staffonly | ||
+ | |||
+ | == Database == | ||
+ | Namedset fields are stored in the database as | ||
+ | fieldname VARCHAR(255) | ||
+ | |||
+ | == API == | ||
+ | See [[API:EPrints/MetaField/Namedset|API page]]. | ||
+ | |||
+ | == Examples == | ||
+ | Most basic example. | ||
+ | { | ||
+ | name => 'archive', | ||
+ | type => 'namedset', | ||
+ | set_name => 'archives', | ||
+ | } | ||
+ | Make field required and only show one input row. | ||
+ | { | ||
+ | name => 'security', | ||
+ | type => 'namedset', | ||
+ | required => 1, | ||
+ | input_rows => 1, | ||
+ | set_name=> 'security', | ||
+ | } | ||
+ | Allow multiple values with long input style (i.e. a list of labelled checkboxes). Link rendered values to a browse view listing. | ||
+ | { | ||
+ | name => 'category', | ||
+ | type => 'namedset', | ||
+ | set_name => 'artwork', | ||
+ | multiple => 1, | ||
+ | required => 1, | ||
+ | input_style => 'long', | ||
+ | browse_link => 'category' | ||
+ | } |
Latest revision as of 11:02, 16 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 field allows a choice from a set of options like a Set field. However, here the options can be defined within a namedset file rather than under the options> attribute of the field configuration. This makes it easier to update the available options, potentially programmatically.
This field offers a halfway house between a Set field and a Subject field. Being more easily re-configurable that the former whilst less complex than the latter.
Inheritance
Additional Properties
As for Set fields except for:
Name | Default Value | Required | Description | Notes |
---|---|---|---|---|
set_name | n/a | YES | Specifies the filename of the namedset file. | |
options | undef | NO | Options from which to choose. | NOT inherited from Set field. Options provided by namedset file defined in set_name. |
Required Phrases
No additional phrases beyond those required for Set fields. However, you may need to add phrases for some or all the values on the namedset file, depending on whether this is a bespoke namedset file. These will take the form:
namedset_filename + "_typename_" + value
For example for lib/namedsets/'s security file, the phrase for staffonly has the ID:
security_typename_staffonly
Database
Namedset fields are stored in the database as
fieldname VARCHAR(255)
API
See API page.
Examples
Most basic example.
{ name => 'archive', type => 'namedset', set_name => 'archives', }
Make field required and only show one input row.
{ name => 'security', type => 'namedset', required => 1, input_rows => 1, set_name=> 'security', }
Allow multiple values with long input style (i.e. a list of labelled checkboxes). Link rendered values to a browse view listing.
{ name => 'category', type => 'namedset', set_name => 'artwork', multiple => 1, required => 1, input_style => 'long', browse_link => 'category' }