The PropertiesTab

  Meta::

    Valid for:  Silva 0.9.3, Zope 2.6.2, Python 2.1.3
    Authors:    kit blake
                Jan Smith
    Email:      kitblake+infrae.com
                jan+curpheymedia.com
    CVS:        $Revision: 1.2 $ $Date: 2003/11/14 22:11:14 $

  Both containers and versioned content have a PropertiesTab. These
  tabs contain metadata and possibly other settings relevant to that
  object.

  Metadata section

    The metadata section is common to both containers and content
    objects.

    The metadata sections has a number of metadata set subsection, one
    for each metadata set associated with this object. The core sets
    are defined by Silva itself and needed for Silva's operation are
    silva-content and silva-extra.

    You can change the metadata associated with the object by filling
    in new values. Some information is always filled in automatically
    by Silva.

    For some metadata elements it is very useful to be able to acquire
    their values from higher up in the tree. This way an element like
    "subject" only needs to be filled in once per subsite,
    instead of for each and every object in this subsite.
 
    If a metadata element can be acquired this is indicated by a
    marker (<sup>&#134;</sup>) in the "acquired content"
    column for that element. If a value is acquired from this object's
    parents then this is also shown in the "acquired
    content" column. If there's nothing entered higher up in the
    tree, then this column will be empty (but for the marker). The
    column is always empty for elements which cannot be acquired; this
    metadata element has to be filled manually in for each object
    which needs it set.

    In case of versioned content objects like Silva Document, metadata
    is versioned along with document contents. In this case the
    metadata becomes uneditable as soon as the document version
    becomes approved. The properties tab will in this case just
    display the metadata without allowing the user to edit it.

    As soon as a new editable version of the object is created, the
    metadata becomes editable again. The published version's metadata
    is still available to the public site, however, until a new
    version with changed metadata is published.

    Metadata of containers and assets is unversioned and thus can always
    be edited.

  Metadata set silva-core

    - **title**: the title of the content object. As a special case,
      the title of a container cannot be edited by a normal author if
      something in the folder has been published. Editors and up can
      always edit the title. This way an author is forbidden from
      affecting the displayed titles in the public site without editor
      intervention.

    - **short title**: if the standard title is long a short title can
       be entered. This is useful for site navigation. For instance
       the Python script which creates the Silva breadcrumb trail
       checks first for a short title. If the field is empty, the
       script uses the normal titcle.

  Metadata set silva-extra

     - **subject**: subject of the content in this area. Inherits from
       parents.

     - **keywords**: a list of keywords and keyword phrases relating
       to the content. This information can be used by public layout
       templates to place keywords in the HTML header metatags, where
       it can be found by search engines. Inherits from parents.

     - **description**: a longer description of the content in this
       area. Can also be exposed in metatags for search
       engines. Inherits from parents.

     - **comment**: this element does not inherit, and is a place to
       add local comments or notes which only apply to this location
       or object.

     - **creation time**: creation date and time of this
       object. Automatically set.

     - **modification time**: date and time of the last modification
        of this object. Automatically set.

     - **publication time**: If set, the time when this object was or
       will be published. Set in the publish tab.

     - **expiration time***: If set, the time when this object will
       (or did) expire from publication. Set in the publish tab.

     - **creator**: User who created the object. Automatically set.

     - **last author**: User who last edited the object. Automatically set.

     - **url**: URL as it would appear in the location bar in the
       browser when viewing this object. Can be affected by virtual
       hosts. Automatically set.

     - **contact name**: appears at the bottom of all public pages in
       the default Silva setup. Inherits from parents.

     - **contact email**: in a rendered page the contact name is a
       'mailto:' link with this address. Inherits from parents.

  Properties for Folders

    For Silva Folders, the |_convert to publication_| button appears
    on the top left in the properties section. Pressing this button
    will convert the Silva Folder to a Silva Publication. The button
    will then change to |_convert_to_folder_| in case you want to
    convert back.

  Properties for Publications

    For Silva Publications, the |_convert to folder_| button appears
    on the top left in the properties section. Pressing this button
    will convert the Silva Folder to a Silva Folder. The button will
    then change to |_convert_to_publication_| in case you want to
    convert back.
    
    If you have the Chief Editor or Manager role, the |_configure
    addables_| button will appear on the right side of the properties
    section. Clicking it will bring you to the "addable
    settings" screen for this publication. This screen allows
    you to control which content objects may be used inside this
    publication.
    
    By default the "acquire" is set in this screen. This
    means that the addable settings will be acquired from higher up in
    the site. If you want to override the addable settings in this
    publication, first turn off the acquire setting by unchecking
    it. Then check the addable objects you want to allow in this
    publication, and uncheck those objects you want to disallow users
    to add. Then click the |_save addable settings_| button. It is always
    possible to go back to acquiring the settings from above by 
    checking the "acquire" checkbox and saving again.

    Developers can create pluggable objects, new content types which
    can be plugged into Silva. Like Silva core objects, they can also
    be turned on and off per publication, and will appear in these
    controls.  See the SilvaDeveloper docs for more information.

<br />
Copyright &copy; 2002, 2003 Infrae. All rights reserved.<br />
See also "LICENSE.txt":license.txt
