Jump to content
Wiki Home
EPrints Home
Bazaar
Files
Main menu
Main menu
move to sidebar
hide
Navigation
Front Page
EPrints 3 Manual
EPrints Training Course
EPrints Glossary
Installing EPrints
How-to Configure EPrints
EPrints 3.2+ API
EPrints 3 Reference
EPrints Plugins
Wiki
All categories
Recent changes
Main Page
Help
EPrints Documentation
Search
Search
Appearance
Log in
Request account
Personal tools
Log in
Request account
Pages for logged out editors
learn more
Contributions
Talk
Editing
Understanding IDs in Workflow Forms
Page
Discussion
British English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{reference}} == Anatomy of an input ID == This is an explanation of how the id="" tags are generated for individual input elements. (ie. a <input>) in a HTML page generated by the EPrints workflow system. This is useful to understand if you're doing clever things with the autocompleter tools or if you want to make your own input components. First of all, some jargon: * The '''workflow''' contains '''pages''' * A '''page''' is rendered as a web page. It is displayed containing one or more '''input components''' * ''input components'' allow the inputing of zero or more ''eprint fields''. * '''eprint fields''' may be multiple. If so they contain multiple '''rows''' of input. Otherwise they contain a single '''row''' * a '''row''' in a compound field consists of all the '''input elements''' of all the sub-fields. * a '''row''' in a non-compound field consists of the fields own '''input elements''' * the '''input elements''' are the actual HTML bits needed to input the data (eg. 3 for date, 2 for page range, one for a title). The id is constructed thus... * EPrints assigns a prefix to the component. This is just a string eprints assigns when generating the page, and should not be relied on. ** eg. id3 ** This is the '''component prefix''' * For a field in a coponent, add "_" and the name of the field. ** eg. id3_creators ** This is the '''field prefix''' * If this is a multiple field, add "_" and the number of the row. Otherwise add nothing. ** eg. id3_creators_2 ** eg. id3_creators_3 ** eg. id4_title (not multiple) ** eg. id5_pagerange ** This is the '''row prefix''' * If this is a compound field, then add "_" and the sub-field id we're inputing. ** eg. id3_creators_2_name ** eg. id4_title (not compound) * If this (sub)field has more than one input component, add the suffix for that input component (see below). * eg. id3_creators_2_name_given * eg. id4_title * eg. id5_pagerange_from === Field types with more than one input component === * date: _day, _month, _year * name: _given, _family (and possibly _lineage and _honourific) * pagerange: _from, _to * time: _day, _month, _year, _second, _minute, _hour
Summary:
Please note that all contributions to EPrints Documentation may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
EPrints Documentation:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Templates used on this page:
Template:RefLinks
(
edit
)
Template:Reference
(
edit
)