Eprint fields.pl - Revision history

Drn@ecs.soton.ac.uk at 00:36, 6 March 2022

2022-03-06T00:36:02Z

Drn@ecs.soton.ac.uk at 08:50, 30 January 2022

2022-01-30T08:50:16Z

Drn@ecs.soton.ac.uk: Put actual filename in bold. Add to dirs and cfgd templates.

2022-01-27T10:12:02Z

Put actual filename in bold. Add to dirs and cfgd templates.

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

2021-12-30T19:17:32Z

Added Configuration category to page

Drn@ecs.soton.ac.uk: /* EPrint Fields */

2021-12-30T19:10:58Z

‎EPrint Fields

Adb1a11@ecs.soton.ac.uk: Fix typos

2012-08-10T10:20:50Z

Fix typos

Pm705 at 22:07, 19 July 2010

2010-07-19T22:07:08Z

Pm705 at 22:06, 19 July 2010

2010-07-19T22:06:45Z

Pm705 at 21:54, 19 July 2010

2010-07-19T21:54:06Z

Pm705: /* Properties */

2010-07-18T10:12:37Z

‎Properties

@@ Line 9: / Line 9: @@
 Note removing fields from eprint_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
+  EPRINTS_PATH/bin/epadmin update_database_structure ARCHIVEID
 and then reload your configuration (or restart the webserver).

← Older revision		Revision as of 08:50, 30 January 2022
Line 2:		Line 2:
	{{cfgd}}		{{cfgd}}

−	~~= EPrint Fields =~~
	'''eprint_fields.pl''' defines all the optional fields which an EPrint 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]].		'''eprint_fields.pl''' defines all the optional fields which an EPrint 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]].

@@ Line 1: / Line 1: @@
 = EPrint Fields =
-eprint_fields.pl defines all the optional fields which an EPrint 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]].
+'''eprint_fields.pl''' defines all the optional fields which an EPrint 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]].
 EPrints have a broad range of 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 21:		Line 21:
	...		...
	];</pre>		];</pre>
		+
		+	[[Category:Configuration]]

@@ Line 2: / Line 2: @@
 eprint_fields.pl defines all the optional fields which an EPrint 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]].
-EPrints have a broad range of 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.
+EPrints have a broad range of 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.
 EPrints also has [[Compound_field|compound]] fields. This is a field made up of compound field definitions. This allows you to make very powerful data structures without having to worry about the complexities of how they are stored in the database.
-Note removing fields from eprint_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 <eprintsroot>/bin/epadmin update_database_structure <repo_id> and then reload your configuration (or restart the webserver).
+Note removing fields from eprint_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:
 ==Field Definition==

@@ Line 9: / Line 9: @@
 ==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 refering 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 fields 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>.]]
+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 refering 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 fields 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}->{eprint} = [

@@ Line 4: / Line 4: @@
 EPrints have a broad range of field types which enforce various constraints. Each field type has it's own method of storing in the database, retriving the value from the database, rendering the value in HTML, and rendering the input component HTML for use in workflows etc.
-EPrints also has compound fields. This is a field made up of compound field definations. This allows you to make very powerful data structures without having to worry about the complexities of how they are stored in the database.
+EPrints also has [[Compound_field|compound]] fields. This is a field made up of compound field definations. This allows you to make very powerful data structures without having to worry about the complexities of how they are stored in the database.
 Note removing fields from eprint_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 <eprintsroot>/bin/epadmin update_database_structure <repo_id> and then reload you configuration (or restart the webserver).
-==Properties==
+==Field Definition==
 <pre>$c->{fields}->{eprint} = [
+           {
@@ Line 15: / Line 17: @@
              'input_rows' => 3,
            },
 ];</pre>

@@ Line 22: / Line 22: @@
 |input_style
 |The width of the input elements which are rendered when this field is viewed (in a workflow for example). Possible values are: small,medium, large. If this value is not specifed the field will pick a sensible default.
 |}