[Bio] / FigWebPages / Attributes.html Repository:
ViewVC logotype

Diff of /FigWebPages/Attributes.html

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.5, Mon Jul 18 03:12:11 2005 UTC revision 1.6, Tue Jul 19 04:54:22 2005 UTC
# Line 1  Line 1 
1  <h1 style="text-align: center">Attributes</h1>  <h1 style="text-align: center">Attributes</h1>
2    
3  <h2 style="text-align: center">Updated July 11th, 2005. Rob Edwards</h2>  <h2 style="text-align: center">Updated July 11th, 2005. Rob Edwards</h2>
4    
5    
# Line 69  Line 70 
70                          <li>Keys are case sensitive</li>                          <li>Keys are case sensitive</li>
71                          <li>An optional mapping is provided between a key and an explanation of what the key means (see below)</li>                          <li>An optional mapping is provided between a key and an explanation of what the key means (see below)</li>
72                          <li>By default, any key can have multiple values. If a key is to have only one value then a boolean can be set (see below) to limit this behavior</li>                          <li>By default, any key can have multiple values. If a key is to have only one value then a boolean can be set (see below) to limit this behavior</li>
73                            <li>keys cannot contain the following characters: space, tab or newline or any of @$!#%^&*()`~{}[]|\:;"'<>?,./
74    
75    
76                  </ul>                  </ul>
77                  <li><em>Value</em>. The value is free form and there are no limitations on what is contained in the value.                  <li><em>Value</em>. The value is free form and there are no limitations on what is contained in the value.
78                  <li><em>URL</em>. The URL is optional, and not required for any data set.                  <li><em>URL</em>. The URL is optional, and not required for any data set.
# Line 121  Line 125 
125                  <li>load_attributes</li>                  <li>load_attributes</li>
126                  <p>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.</p>                  <p>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.</p>
127                  <li>gather_attributes</li>                  <li>gather_attributes</li>
128                  <p>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.</p>                  <p>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. Gather attributes can take an optional -d on the command line, and will "delete" any attributes file that it finds. It doesn't actually delete the file, rather moves it to FIG_Config::temp/Attributes/deleted_attributes, and you can delete it from there.</p>
129                  <li>distribute_attributes</li>                  <li>distribute_attributes</li>
130                  <p>This script will take any attributes on STDIN and write them to their appropriate locations.</p>                  <p>This script will take any attributes on STDIN and write them to their appropriate locations.</p>
131    <p><b>Recommended</b> The recommended way to run these two commands is to first run gather attributes to collate the information and delete it:
132    <br><tt>
133    $gather_attributes -d > gathered_attributes.txt
134    </tt>
135    </br>
136    <br>And then to run the distribute command:</br>
137    <br><tt>
138    $sort -u gathered_attributes.txt | distribute_attributes
139    </tt></br>
140    
141    <p>This will recreate the attributes files, and overcome any potential problems of writing files that are being moved.</p>
142    
143                  <li>dump_attributes</li>                  <li>dump_attributes</li>
144                  <p>Dumps the current value of each attribute from the database, so these have all the changes in transaction_log already enacted.</p>                  <p>Dumps the current value of each attribute from the database, so these have all the changes in transaction_log already enacted.</p>
145          </ol>          </ol>

Legend:
Removed from v.1.5  
changed lines
  Added in v.1.6

MCS Webmaster
ViewVC Help
Powered by ViewVC 1.0.3