Updated Editor View Config file:  %(datafile)s

TO DOWNLOAD FILE: Right-click on the above link and choose "Save Link As".


If you'd like to launch a CIF editor test session using the newly updated view config file,
PLEASE FIRST SAVE A COPY OF YOUR UPDATED CONFIG FILE ABOVE, and then
use the form below to upload a test coordinate data file and indicate the desired view context.















Color legend: Primary Key Field Read-Only Field Data Required Missing Required Data mmCIF Dictionary Violation New Row Added by User Row Selected for Action







Clone Options:

Duplicate View ID

Duplicate Primary Heading

Duplicate SubHeading

Duplicate Category Display Name


How many rows?

NOTE: rows will be added just below the row currently selected.

How many rows?

NOTE: rows will be deleted starting with highlighted row and continuing as necessary with rows directly below to satisfy quantity specified.

Use input below to submit value not already in the choice list.

Value being submitted, '', is not in list of accepted options.

Please confirm that you would like to submit this value.

Help Info on configuring CIF Editor UI

There are two cif categories which control aspects of the CIF Editor UI: pdbx_display_view_category_info and pdbx_display_view_item_info

Both categories contain the view_id item, which is the identifier that corresponds to a given "context" in which the CIF Editor UI is potentially used. Currently the view_id's in use are:

pdbx_display_view_category_info

This category determines:
  • what headings are used in the horizontal navigation menu
  • how these headings are mapped to CIF categories
  • whether there will be corresponding drop-down choices (and the labels for the drop-downs if these are desired), etc.
NOTE: the main purpose of each row in this category is to configure how a single cif category is to be associated with a top-level menu heading and optionally a drop-down sub-heading

Below are brief explanations of the category's columns/items.
  • view_id - explained above
  • Primary Heading - these identifiers correspond to the top-level navigation menu bar choices, under which 1 or more cif categories will be grouped
  • Sub Heading - for a given "Primary Heading" above, this item allows one to create sub-headings.
    If no sub-headings are desired for the top-level heading, the value for this item must be the same as "Primary Heading" for the cif category/row
    If sub-headings are desired (which will show as drop-down choices upon clicking the top-level label), the value for this item will be displayed as the label of the drop-down choice and
    this value must be different from the "Primary Heading". e.g. to create four drop-down sub-headings for the same primary heading, there should be four records with four
    distinct values for this item but which all share the same "Primary Heading"
  • category_name - used to specify which cif categories are to fall under the given top-level menu heading and optionally under a given sub-heading
  • category_display_name - user-friendly display name for the CIF category (not currently being utilized but may be of potential future use)
    Convention is to use default value of category name when not using a user-friendly alternative.
    IMPORTANT: this value serves as parent key to corresponding child key in the "pdbx_display_view_item_info" category discussed below
  • category_cardinality - whether or not the category will be restricted to having just one record

pdbx_display_view_item_info

This category is used to configure which actual cif items are "priority" items, i.e. are shown by default on initial viewing of the data.
Brief description of columns:
  • view_id - explained above
  • category_display_name - item used to map rows in this section to those in the first section
    IMPORTANT: must match a parent key in the 'pdbx_display_view_category_info" category above
  • item_name - fully qualified item name
  • item_display_name - user-friendly display name for the item
  • read_only_flag - whether or not the item is read-only