This is a position of responsibility, good judgment, and malacological knowledge, along with the ability to clearly and accurately portray a concept to others without being verbose. Editors insure that definitions released to the public (to the world!) are correct.
Status:
The "Editor" level is level of use at which definitions get edited and/or approved.
At this level of use, the visitor is logged in to their account AND have supplied the Editor password.
Capabilities:
Approve definitions that others ("Visitors" and "Contributors") have entered (i.e., Editors can set a definition to "active").
Edit ANY definition in the glossary, and decide whether or not to designate the term as "active" after the edit.
Hide any definition from Visitors and Contributors (i.e., set a definition to "inactive").
Delete a term and its definition (actually "flag" it for deletion, which suppresses its display).
Add links, graphics, and photos to the glossary terms. Note, however, that presently these images must be edited, made web-ready, and uploaded to the site by a Developer.
Procedures:
The "Editor" level account must be designated as a Editor by an glossary "Administrator" or "Developer".
The user may log into his/her account alone, and thus sign in at the "Contributor" level.
The user may optionally also supply the Editor password at login, providing the login session with Editor rights.
Details:
How to add an apostrophe to a word in a definition.
Many terms were added directly into the database, which accepts a single apostrophe. The web pages even display that apostrophe. However, when editing a definition via the web page interface, a single apostrophe in the definition will cause failure when attempting to save the definition. Work-a-round: place two apostrophes in the definition where one is needed... only one will display!
How to add hidden words into the "Terms" field, that are thus searchable but don't show!
Just a little bit of html knowledge is helpful, but not necessary; following these instructions is "mission critical"!
In the "Terms" field, sometimes it is necessary to have searchable text that doesn't display on screen. For example, you might search for lip, apertural which would fail because that combination is not how it is entered, i.e., apertural lip. Therefore, we would embed the text combination lip, apertural into the Terms field, but code it as an html comment, causing it not to display. It is thus searchable (because it is text in the Terms field, but the web browser interprets the comment code and does not display the hidden/comment text!
Example Term text for APERTURAL LIP, shown without html and then with html coding for hidden/comment text:
Without the html: APERTURAL LIP
With html codes and hidden/comment text:
APERTURAL LIP <!-- LIP, APERTURAL -->
In red, just for emphasis:
APERTURAL LIP <!-- LIP, APERTURAL -->
(note: each "line" is two hyphens, adjacent to each other)
User then sees on the web page: APERTURAL LIP
Sometimes you'll want to add capability for the user to search for a term, IF they split it into two words. For example, the term SHIPWORK is in the clossary, but an Editor should include (hidden in the Terms field) two words SHIP WORM thereby facilitating the search for the term as either one word or two!
Sometimes you'll want two terms listed in the "Terms" field, the singular and pleural of the term, and display them on separate lines. To do so, add the html code for line break: <br> between the two terms.
RADULA <br>(pl. RADULAE)
The user can then search for (and see!) the singular or pleural of the term! Technically, you don't need a space after RADULA, but doing so causes the term RADULA to properly sort out before RADULA FORMULA and RADULA RIBBON, etc.
Note: do a search for pl. and you'll see each term that also lists its pleural!!! (because pl. exists in the "Terms" field)
How to add links to terms while editing definitions
Just a little bit of html knowledge is helpful, but not necessary; following these instructions is "mission critical"!
Example definition text for ALBINISTIC, shown without html and then with html coding for a linked term:
Without the html:
Tending toward being an albino; nearly all white.
With html codes:
Tending toward being an <a href="Terms.asp?textfield=albino">ALBINO</a>; nearly all white.
In red, just for emphasis:
Tending toward being an <a href="Terms.asp?textfield=albino">ALBINO</a>; nearly all white.
User then sees on the web page:
Tending toward being an ALBINO; nearly all white.
Note the two instances of the linked term inside the html code. The lowercase term is what is actually searched for... this must match and link to an existing term! The uppercase term is what is displayed to the user... its only function is display and can be the pleural of the term if thats what fits in the definition's text.
An easy way to add a link is to "copy" the text provided below, and "paste"
it into a definition, then add the lowercase and uppercase version
of the linked term EXACTLY where they should be in the code:
<a href="Terms.asp?textfield="></a>
Note: After editing and saving a term and definition, ALWAYS check your work! ...does the link work?
|