--- Attributes.html 2005/07/12 14:34:15 1.4 +++ Attributes.html 2005/07/18 03:12:11 1.5 @@ -6,18 +6,22 @@

Contents

  • Overview
  • Definitions
  • +
  • File Locations
  • +
  • Scripts for working with attributes
  • Methods for accessing attributes
  • -
  • get_attributes
  • -
  • add_attribute
  • -
  • delete_attribute
  • -
  • change_attribute
  • -
  • erase_attribute_entirely
  • -
  • get_keys
  • -
  • get_values
  • -
  • key_info
  • -
  • get_key_value
  • -
  • guess_value_format
  • -
  • attribute_location
  • +

    I have added attributes to the database in a more significant way. This page is to document those attributes and ways to access/modify them. The page has two sections, a non-technical section for general discussion and overview, and a technical section for behind-the-scenes type information.

    @@ -70,19 +74,34 @@
  • URL. The URL is optional, and not required for any data set.
    -
  • File Locations
  • +
  • File Locations
  • +
  • Scripts for working with attributes
  • +
  • Here are a few common scripts that you may want to use: +
      +
    1. load_attributes
    2. +

      This will delete the current attributes database, look through all the potential places that attributes are stored and add those attributes into the database. Both genome-specific and global attributes will be added. Finally, each of the transaction_logs are processed and the data added back into the database. This is used to add new data to a database, and to rebuild an existing database.

      +
    3. gather_attributes
    4. +

      Atrributes are stored in disparate locations (global, genome, etc) and this will look through all the various locations and print out any attributes that are found. This can be piped through sort -u to remove any duplicate attributes.

      +
    5. distribute_attributes
    6. +

      This script will take any attributes on STDIN and write them to their appropriate locations.

      +
    7. dump_attributes
    8. +

      Dumps the current value of each attribute from the database, so these have all the changes in transaction_log already enacted.

      +
    + + +