Difference between revisions of "Namedset field"
m |
m |
||
Line 12: | Line 12: | ||
*** [[Namedset field]] | *** [[Namedset field]] | ||
− | == Properties == | + | == Additional Properties == |
− | As for [[ | + | As for [[Set field#Additional_Properties|Set fields]] except for: |
{| border="1" cellpadding="3" cellspacing="0" | {| border="1" cellpadding="3" cellspacing="0" | ||
Line 24: | Line 24: | ||
== Required Phrases == | == Required Phrases == | ||
− | No additional phrases. However, you may need to add phrases for some | + | No additional phrases beyond those required for [[Set field#Required_Phrases|Setvfields]]. 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 | 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: | For example for <tt>[[lib/namedsets/]]</tt>'s <tt>security</tt> file, the phrase for <tt>staffonly</tt> has the ID: |
Revision as of 22: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 field allow sa 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 | description |
set_name | n/a | Specifies the filename of the namedset file. This property is always required. |
options | undef | This property should not be set as will be overridden by the options in the namedset file specified by set_name. |
Required Phrases
No additional phrases beyond those required for Setvfields. 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' }