Biotics Views Classification:  Last Updated 11/04/04
Configurable Views (views that were created by users for use in queries and exports.  These views can be customized as needed, but changes should be coordinated with the author of the view.)[1] Configuration Guidelines  
BCD_EOR                                                                         This view is displayed on the Tracker Data tab of the Element Occurrence window (PB).  It is also considered a "core view" in the Add/Remove Oracle Attributes function.  The columns in this view can be altered.  However this view should be kept minimal to maintain performance.  The view must contain the following columns: shape_id.
BCD_ET                                                                          This view is used extensively by Biotics-Mapper.  It powers the Select Element window, and is used in many other AVE & PB windows to display the element's scientific and common names.  It is what is displayed on the Element tab of the Source Feature and Element Occurrence windows (PB).  It is also used by many of the views that are joined to the themes (e.g., EO_VIEW_STD_ATT), and is also considered a "core view" in the Add/Remove Oracle Attributes function.  The columns in this view can be altered.  However this view should be kept minimal to maintain performance.  The view must contain the following columns: element_subnational_id, elcode, sname, scomname, gname, gcomname, name_category_desc, and subnation_name.  In addition g_rank, s_rank, and eo_track_status_desc are referenced by the EO_VIEW_ALL_ATT view.
BIOTICS_UNMAPPED_MA_VW                                                          Used in the Link Shapes to Data Records function - lists all MAs that do not yet have a shape.  Can add/remove columns if desired, but feature_id must always be included.  The column and row order can also be adjusted if desired.
BIOTICS_UNMAPPED_SITE_VW                                                        Used in the Link Shapes to Data Records function - lists all Sites that do not yet have a shape.  Can add/remove columns if desired, but feature_id must always be included.  The column and row order can also be adjusted if desired.
EO_REF_PT_VIEW_STD_ATT                                                          Source of the "EO Point Reps - Std Attributes" theme.  There are no requirements for the content of this view, but name_category_desc should be included as there is a default legend based on this column.  However it should include the common and scientific names to be useful, and generally should be kept minimal to maintain performance.
EO_VIEW_ALL_ATT                                                                 Users can join this view to the EO Rep theme (Polygon) on an ad-hoc basis using the Add/Remove Oracle Attributes function.  Can add/remove columns if desired, but feature_id must always be included.  Should exclude records that are logically deleted.
EO_VIEW_STD_ATT                                                                 This view is joined to the EO Rep theme (Polygon) by default (i.e., usually all of the time).  This view should be kept minimal to maintain performance. Can add/remove columns if desired, but feature_id must always be included, and name_category_desc and map_qc_status should be included as there are default legends based on these columns.  Should exclude records that are logically deleted.
MANAGED_AREA_VIEW                                                               This view is joined to the Managed Area theme by default (i.e., usually all of the time).  This view should be kept minimal to maintain performance. Can add/remove columns if desired, but feature_id must always be included.  Should exclude records that are logically deleted.
SITE_VIEW                                                                       This view is joined to the Site theme by default (i.e., usually all of the time).  This view should be kept minimal to maintain performance. Can add/remove columns if desired, but feature_id must always be included.  Should exclude records that are logically deleted.
SOURCE_VIEW_ALL_ATT                                                             Users can join this view to the Source Feature themes (Point, Line, and Polygon) on an ad-hoc basis using the Add/Remove Oracle Attributes function.  Can add/remove columns if desired, but feature_id must always be included.  Should exclude records that are logically deleted.
SOURCE_VIEW_STD_ATT                                                             This view is joined to the Source Feature themes (Point, Line, and Polygon) by default (i.e., usually all of the time).  This view should be kept minimal to maintain performance. Can add/remove columns if desired, but feature_id must always be included, and name_category_desc, eo_shape_id, and map_qc_status should be included as there are default legends based on these columns.  Should exclude records that are logically deleted.
[1]
Ian Finlay:
A lot of these views were created by NatureServe and Linnet, but can be tailored to suit an individual program's requirements.  I don't think it's necessary to coordinate changes with the author - just follow the guidelines for each.