Eprint fields.pl

From EPrints Documentation
Revision as of 10:12, 18 July 2010 by Pm705 (Talk | contribs)

Jump to: navigation, search

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 here.

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.

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).


name The identifier used for this field in EPrints. The name used to refer to a field whe you $eprint->value(), as part of a search, in citations etc.
type The type of the field. Different types of field can result in different data structures begin returned when $eprint->value() is called. Types also enforce some basic validation again what is entered into them. Types include: text, longtext, name, email, compound, int, set, namedset, subject and so on. For a full list of possible field types you can see a full list of types Category:EPrints_Metadata_Fields
multiple A multiple=>1 field can have many values. Say for example: an item can have multiple tags, the tags field in this case would be a multiple field. Note if you use $eprint->value() on a multiple field it returns and array ref rather than a single scalar.
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.