Namedset field: Difference between revisions
mNo edit summary |
|||
| (6 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
== Description == | == Description == | ||
This field | 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. | 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. | ||
| Line 9: | Line 9: | ||
== Inheritance == | == Inheritance == | ||
* [[Metadata]] | * [[Metadata]] | ||
** [[Set field]] | ** [[Id field]] | ||
*** [[Namedset field]] | *** [[Text field]] | ||
**** [[Set 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" | ||
! 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. However, you may need to add phrases for some | 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 | 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: | ||
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
Description[edit]
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[edit]
Additional Properties[edit]
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[edit]
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[edit]
Namedset fields are stored in the database as
fieldname VARCHAR(255)
API[edit]
See API page.
Examples[edit]
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'
}