User fields.pl - Revision history

Drn@ecs.soton.ac.uk: Removed category configuration as provided by cfgd template.

2022-01-31T08:13:03Z

Removed category configuration as provided by cfgd template.

Drn@ecs.soton.ac.uk: Added cfgd and dirs templates

2022-01-31T08:06:49Z

Added cfgd and dirs templates

Drn@ecs.soton.ac.uk: Added actually file name in bold.

2022-01-31T08:04:51Z

Added actually file name in bold.

Drn@ecs.soton.ac.uk: Added Configuration category to page

2021-12-30T19:17:51Z

Added Configuration category to page

Drn@ecs.soton.ac.uk: Added user_fields.pl page

2021-12-30T19:09:36Z

Added user_fields.pl page

New page

= User Fields =
user_fields.pl defines all the optional fields which an User object has. These fields all have mappings to the database. There are a variety of field types which you can see here [[:Category:EPrints_Metadata_Fields|here]].

Users have various field types which enforce various constraints. Each field type has its own method of storing in the database, retrieving the value from the database, rendering the value in HTML, and rendering the input component HTML for use in workflows, etc.

Note removing fields from user_fields.pl does not usually cause data to be deleted from the database. To add or remove fields from eprint_fields.pl you must run:
EPRINTS_PATH/bin/epadmin update_database_structure <ARCHIVE_NAME>
and then reload your configuration (or restart the webserver).

==Field Definition==
The field list is represented by an arrayref of hashrefs. Each hashref has at minimum a <code>name</code>, which is the field name used when referring to the field (e.g. in search) and a <code>type</code>, which describes the type of data the field will hold. Depending on a field's type there may also be other compulsory fields and some optional ones. [[:Category:EPrints_Metadata_Fields |See the details of field definition on the page for that <code>type</code>.]]

<pre>$c->{fields}->{user} = [
{
name => 'name',
type => 'name',
render_order => 'gf',
},
...
];</pre>

← Older revision		Revision as of 08:13, 31 January 2022
Line 21:		Line 21:
	...		...
	];</pre>		];</pre>
−
−	~~[[Category:Configuration]]~~

← Older revision		Revision as of 08:06, 31 January 2022
Line 1:		Line 1:
		+	{{dirs}}
		+	{{cfgd}}
		+
	'''user_fields.pl''' defines all the optional fields which an User object has. These fields all have mappings to the database. There are a variety of field types which you can see here [[:Category:EPrints_Metadata_Fields\|here]].		'''user_fields.pl''' defines all the optional fields which an User object has. These fields all have mappings to the database. There are a variety of field types which you can see here [[:Category:EPrints_Metadata_Fields\|here]].

← Older revision		Revision as of 08:04, 31 January 2022
Line 1:		Line 1:
−	~~= User Fields =~~	+	'''user_fields.pl''' defines all the optional fields which an User object has. These fields all have mappings to the database. There are a variety of field types which you can see here [[:Category:EPrints_Metadata_Fields\|here]].
−	user_fields.pl defines all the optional fields which an User object has. These fields all have mappings to the database. There are a variety of field types which you can see here [[:Category:EPrints_Metadata_Fields\|here]].

	Users have various field types which enforce various constraints. Each field type has its own method of storing in the database, retrieving the value from the database, rendering the value in HTML, and rendering the input component HTML for use in workflows, etc.		Users have various field types which enforce various constraints. Each field type has its own method of storing in the database, retrieving the value from the database, rendering the value in HTML, and rendering the input component HTML for use in workflows, etc.

← Older revision		Revision as of 19:17, 30 December 2021
Line 19:		Line 19:
	...		...
	];</pre>		];</pre>
		+
		+	[[Category:Configuration]]