[Bio] / Sprout / Sprout.pm Repository:
ViewVC logotype

Diff of /Sprout/Sprout.pm

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

revision 1.14, Thu Jun 9 19:06:55 2005 UTC revision 1.25, Sun Sep 11 17:29:52 2005 UTC
# Line 70  Line 70 
70    
71  * B<maxSequenceLength> maximum number of residues per sequence, (default C<8000>)  * B<maxSequenceLength> maximum number of residues per sequence, (default C<8000>)
72    
73    * B<noDBOpen> suppresses the connection to the database if TRUE, else FALSE
74    
75  =back  =back
76    
77  For example, the following constructor call specifies a database named I<Sprout> and a user name of  For example, the following constructor call specifies a database named I<Sprout> and a user name of
# Line 86  Line 88 
88          # Compute the options. We do this by starting with a table of defaults and overwriting with          # Compute the options. We do this by starting with a table of defaults and overwriting with
89          # the incoming data.          # the incoming data.
90          my $optionTable = Tracer::GetOptions({          my $optionTable = Tracer::GetOptions({
91                                             dbType               => 'mysql',                     # database type                         dbType       => $FIG_Config::dbms,
92                                             dataDir              => 'Data',                      # data file directory                                                          # database type
93                                             xmlFileName  => 'SproutDBD.xml', # database definition file name                         dataDir      => $FIG_Config::sproutData,
94                                             userData             => 'root/',                     # user name and password                                                          # data file directory
95                                             port                 => 0,                           # database connection port                         xmlFileName  => "$FIG_Config::sproutData/SproutDBD.xml",
96                                                            # database definition file name
97                           userData     => "$FIG_Config::dbuser/$FIG_Config::dbpass",
98                                                            # user name and password
99                           port         => $FIG_Config::dbport,
100                                                            # database connection port
101                                             maxSegmentLength => 4500,            # maximum feature segment length                                             maxSegmentLength => 4500,            # maximum feature segment length
102                                             maxSequenceLength => 8000,           # maximum contig sequence length                                             maxSequenceLength => 8000,           # maximum contig sequence length
103                           noDBOpen     => 0,               # 1 to suppress the database open
104                                            }, $options);                                            }, $options);
105          # Get the data directory.          # Get the data directory.
106          my $dataDir = $optionTable->{dataDir};          my $dataDir = $optionTable->{dataDir};
# Line 100  Line 108 
108          $optionTable->{userData} =~ m!([^/]*)/(.*)$!;          $optionTable->{userData} =~ m!([^/]*)/(.*)$!;
109          my ($userName, $password) = ($1, $2);          my ($userName, $password) = ($1, $2);
110          # Connect to the database.          # Connect to the database.
111          my $dbh = DBKernel->new($optionTable->{dbType}, $dbName, $userName, $password, $optionTable->{port});      my $dbh;
112        if (! $optionTable->{noDBOpen}) {
113            $dbh = DBKernel->new($optionTable->{dbType}, $dbName, $userName,
114                                    $password, $optionTable->{port});
115        }
116          # Create the ERDB object.          # Create the ERDB object.
117          my $xmlFileName = "$optionTable->{xmlFileName}";          my $xmlFileName = "$optionTable->{xmlFileName}";
118          my $erdb = ERDB->new($dbh, $xmlFileName);          my $erdb = ERDB->new($dbh, $xmlFileName);
# Line 420  Line 432 
432          # Loop through the incoming table names.          # Loop through the incoming table names.
433          for my $tableName (@{$tableList}) {          for my $tableName (@{$tableList}) {
434                  # Find the table's file.                  # Find the table's file.
435                  my $fileName = "$dataDir/$tableName";          my $fileName = LoadFileName($dataDir, $tableName);
436                  if (! -e $fileName) {          if (! $fileName) {
437                          $fileName = "$fileName.dtx";              Trace("No load file found for $tableName in $dataDir.") if T(0);
438                  }          } else {
439                  # Attempt to load this table.                  # Attempt to load this table.
440                  my $result = $erdb->LoadTable($fileName, $tableName, $truncateFlag);                  my $result = $erdb->LoadTable($fileName, $tableName, $truncateFlag);
441                  # Accumulate the resulting statistics.                  # Accumulate the resulting statistics.
442                  $retVal->Accumulate($result);                  $retVal->Accumulate($result);
443          }          }
444        }
445          # Return the statistics.          # Return the statistics.
446          return $retVal;          return $retVal;
447  }  }
# Line 570  Line 583 
583  =item RETURN  =item RETURN
584    
585  Returns a list of the feature's contig segments. The locations are returned as a list in a list  Returns a list of the feature's contig segments. The locations are returned as a list in a list
586  context and as a space-delimited string in a scalar context.  context and as a comma-delimited string in a scalar context.
587    
588  =back  =back
589    
# Line 613  Line 626 
626                  push @retVal, "${contigID}_$beg$dir$len";                  push @retVal, "${contigID}_$beg$dir$len";
627          }          }
628          # Return the list in the format indicated by the context.          # Return the list in the format indicated by the context.
629          return (wantarray ? @retVal : join(' ', @retVal));      return (wantarray ? @retVal : join(',', @retVal));
630  }  }
631    
632  =head3 ParseLocation  =head3 ParseLocation
# Line 1230  Line 1243 
1243    
1244  =item RETURN  =item RETURN
1245    
1246  Returns a reference to a hash that maps the IDs of the incoming features to the IDs of  Returns a reference to a hash that maps the IDs of the incoming features to the best hits
1247  their best hits.  on the target genome.
1248    
1249  =back  =back
1250    
# Line 1259  Line 1272 
1272          return \%retVal;          return \%retVal;
1273  }  }
1274    
1275    =head3 SimList
1276    
1277    C<< my %similarities = $sprout->SimList($featureID, $count); >>
1278    
1279    Return a list of the similarities to the specified feature.
1280    
1281    Sprout does not support real similarities, so this method just returns the bidirectional
1282    best hits.
1283    
1284    =over 4
1285    
1286    =item featureID
1287    
1288    ID of the feature whose similarities are desired.
1289    
1290    =item count
1291    
1292    Maximum number of similar features to be returned, or C<0> to return them all.
1293    
1294    =back
1295    
1296    =cut
1297    #: Return Type %;
1298    sub SimList {
1299        # Get the parameters.
1300        my ($self, $featureID, $count) = @_;
1301        # Ask for the best hits.
1302        my @lists = $self->GetAll(['IsBidirectionalBestHitOf'],
1303                                  "IsBidirectionalBestHitOf(from-link) = ? ORDER BY IsBidirectionalBestHitOf(score) DESC",
1304                                  [$featureID], ['IsBidirectionalBestHitOf(to-link)', 'IsBidirectionalBestHitOf(score)'],
1305                                  $count);
1306        # Create the return value.
1307        my %retVal = ();
1308        for my $tuple (@lists) {
1309            $retVal{$tuple->[0]} = $tuple->[1];
1310        }
1311        # Return the result.
1312        return %retVal;
1313    }
1314    
1315    
1316    
1317    =head3 IsComplete
1318    
1319    C<< my $flag = $sprout->IsComplete($genomeID); >>
1320    
1321    Return TRUE if the specified genome is complete, else FALSE.
1322    
1323    =over 4
1324    
1325    =item genomeID
1326    
1327    ID of the genome whose completeness status is desired.
1328    
1329    =item RETURN
1330    
1331    Returns TRUE if the genome is complete, FALSE if it is incomplete, and C<undef> if it is
1332    not found.
1333    
1334    =back
1335    
1336    =cut
1337    #: Return Type $;
1338    sub IsComplete {
1339        # Get the parameters.
1340        my ($self, $genomeID) = @_;
1341        # Declare the return variable.
1342        my $retVal;
1343        # Get the genome's data.
1344        my $genomeData = $self->GetEntity('Genome', $genomeID);
1345        if ($genomeData) {
1346            # The genome exists, so get the completeness flag.
1347            ($retVal) = $genomeData->Value('complete');
1348        }
1349        # Return the result.
1350        return $retVal;
1351    }
1352    
1353  =head3 FeatureAliases  =head3 FeatureAliases
1354    
1355  C<< my @aliasList = $sprout->FeatureAliases($featureID); >>  C<< my @aliasList = $sprout->FeatureAliases($featureID); >>
# Line 1378  Line 1469 
1469          return %retVal;          return %retVal;
1470  }  }
1471    
1472    =head3 CouplingEvidence
1473    
1474    C<< my @evidence = $sprout->CouplingEvidence($peg1, $peg2); >>
1475    
1476    Return the evidence for a functional coupling.
1477    
1478    A pair of features is considered evidence of a coupling between two other
1479    features if they occur close together on a contig and both are similar to
1480    the coupled features. So, if B<A1> and B<A2> are close together on a contig,
1481    B<B1> and B<B2> are considered evidence for the coupling if (1) B<B1> and
1482    B<B2> are close together, (2) B<B1> is similar to B<A1>, and (3) B<B2> is
1483    similar to B<A2>.
1484    
1485    The score of a coupling is determined by the number of pieces of evidence
1486    that are considered I<representative>. If several evidence items belong to
1487    a group of genomes that are close to each other, only one of those items
1488    is considered representative. The other evidence items are presumed to be
1489    there because of the relationship between the genomes rather than because
1490    the two proteins generated by the features have a related functionality.
1491    
1492    Each evidence item is returned as a three-tuple in the form C<[>I<$peg1a>C<,>
1493    I<$peg2a>C<,> I<$rep>C<]>, where I<$peg1a> is similar to I<$peg1>, I<$peg2a>
1494    is similar to I<$peg2>, and I<$rep> is TRUE if the evidence is representative
1495    and FALSE otherwise.
1496    
1497    =over 4
1498    
1499    =item peg1
1500    
1501    ID of the feature of interest.
1502    
1503    =item peg2
1504    
1505    ID of a feature functionally coupled to the feature of interest.
1506    
1507    =item RETURN
1508    
1509    Returns a list of 3-tuples. Each tuple consists of a feature similar to the feature
1510    of interest, a feature similar to the functionally coupled feature, and a flag
1511    that is TRUE for a representative piece of evidence and FALSE otherwise.
1512    
1513    =back
1514    
1515    =cut
1516    #: Return Type @@;
1517    sub CouplingEvidence {
1518        # Get the parameters.
1519        my ($self, $peg1, $peg2) = @_;
1520        # Declare the return variable.
1521        my @retVal = ();
1522        # Our first task is to find out the nature of the coupling: whether or not
1523        # it exists, its score, and whether the features are stored in the same
1524        # order as the ones coming in.
1525        my ($couplingID, $inverted, $score) = $self->GetCoupling($peg1, $peg2);
1526        # Only proceed if a coupling exists.
1527        if ($couplingID) {
1528            # Determine the ordering to place on the evidence items. If we're
1529            # inverted, we want to see feature 2 before feature 1 (descending); otherwise,
1530            # we want feature 1 before feature 2 (normal).
1531            Trace("Coupling evidence for ($peg1, $peg2) with inversion flag $inverted.") if T(Coupling => 4);
1532            my $ordering = ($inverted ? "DESC" : "");
1533            # Get the coupling evidence.
1534            my @evidenceList = $self->GetAll(['IsEvidencedBy', 'PCH', 'UsesAsEvidence'],
1535                                              "IsEvidencedBy(from-link) = ? ORDER BY PCH(id), UsesAsEvidence(pos) $ordering",
1536                                              [$couplingID],
1537                                              ['PCH(used)', 'UsesAsEvidence(to-link)']);
1538            # Loop through the evidence items. Each piece of evidence is represented by two
1539            # positions in the evidence list, one for each feature on the other side of the
1540            # evidence link. If at some point we want to generalize to couplings with
1541            # more than two positions, this section of code will need to be re-done.
1542            while (@evidenceList > 0) {
1543                my $peg1Data = shift @evidenceList;
1544                my $peg2Data = shift @evidenceList;
1545                Trace("Peg 1 is " . $peg1Data->[1] . " and Peg 2 is " . $peg2Data->[1] . ".") if T(Coupling => 4);
1546                push @retVal, [$peg1Data->[1], $peg2Data->[1], $peg1Data->[0]];
1547            }
1548            Trace("Last index in evidence result is is $#retVal.") if T(Coupling => 4);
1549        }
1550        # Return the result.
1551        return @retVal;
1552    }
1553    
1554    =head3 GetCoupling
1555    
1556    C<< my ($couplingID, $inverted, $score) = $sprout->GetCoupling($peg1, $peg2); >>
1557    
1558    Return the coupling (if any) for the specified pair of PEGs. If a coupling
1559    exists, we return the coupling ID along with an indicator of whether the
1560    coupling is stored as C<(>I<$peg1>C<, >I<$peg2>C<)> or C<(>I<$peg2>C<, >I<$peg1>C<)>.
1561    In the second case, we say the coupling is I<inverted>. The importance of an
1562    inverted coupling is that the PEGs in the evidence will appear in reverse order.
1563    
1564    =over 4
1565    
1566    =item peg1
1567    
1568    ID of the feature of interest.
1569    
1570    =item peg2
1571    
1572    ID of the potentially coupled feature.
1573    
1574    =item RETURN
1575    
1576    Returns a three-element list. The first element contains the database ID of
1577    the coupling. The second element is FALSE if the coupling is stored in the
1578    database in the caller specified order and TRUE if it is stored in the
1579    inverted order. The third element is the coupling's score. If the coupling
1580    does not exist, all three list elements will be C<undef>.
1581    
1582    =back
1583    
1584    =cut
1585    #: Return Type $%@;
1586    sub GetCoupling {
1587        # Get the parameters.
1588        my ($self, $peg1, $peg2) = @_;
1589        # Declare the return values. We'll start with the coupling ID and undefine the
1590        # flag and score until we have more information.
1591        my ($retVal, $inverted, $score) = (CouplingID($peg1, $peg2), undef, undef);
1592        # Find the coupling data.
1593        my @pegs = $self->GetAll(['Coupling', 'ParticipatesInCoupling'],
1594                                     "Coupling(id) = ? ORDER BY ParticipatesInCoupling(pos)",
1595                                     [$retVal], ["ParticipatesInCoupling(from-link)", "Coupling(score)"]);
1596        # Check to see if we found anything.
1597        if (!@pegs) {
1598            Trace("No coupling found.") if T(Coupling => 4);
1599            # No coupling, so undefine the return value.
1600            $retVal = undef;
1601        } else {
1602            # We have a coupling! Get the score and check for inversion.
1603            $score = $pegs[0]->[1];
1604            my $firstFound = $pegs[0]->[0];
1605            $inverted = ($firstFound ne $peg1);
1606            Trace("Coupling score is $score. First peg is $firstFound, peg 1 is $peg1.") if T(Coupling => 4);
1607        }
1608        # Return the result.
1609        return ($retVal, $inverted, $score);
1610    }
1611    
1612    =head3 CouplingID
1613    
1614    C<< my $couplingID = Sprout::CouplingID($peg1, $peg2); >>
1615    
1616    Return the coupling ID for a pair of feature IDs.
1617    
1618    The coupling ID is currently computed by joining the feature IDs in
1619    sorted order with a space. Client modules (that is, modules which
1620    use Sprout) should not, however, count on this always being the
1621    case. This method provides a way for abstracting the concept of a
1622    coupling ID. All that we know for sure about it is that it can be
1623    generated easily from the feature IDs and the order of the IDs
1624    in the parameter list does not matter (i.e. C<CouplingID("a1", "b1")>
1625    will have the same value as C<CouplingID("b1", "a1")>.
1626    
1627    =over 4
1628    
1629    =item peg1
1630    
1631    First feature of interest.
1632    
1633    =item peg2
1634    
1635    Second feature of interest.
1636    
1637    =item RETURN
1638    
1639    Returns the ID that would be used to represent a functional coupling of
1640    the two specified PEGs.
1641    
1642    =back
1643    
1644    =cut
1645    #: Return Type $;
1646    sub CouplingID {
1647        return join " ", sort @_;
1648    }
1649    
1650  =head3 GetEntityTypes  =head3 GetEntityTypes
1651    
1652  C<< my @entityList = $sprout->GetEntityTypes(); >>  C<< my @entityList = $sprout->GetEntityTypes(); >>
# Line 1439  Line 1708 
1708                  if ($line =~ m/^>\s*(.+?)(\s|\n)/) {                  if ($line =~ m/^>\s*(.+?)(\s|\n)/) {
1709                          # Here we have a new header. Store the current sequence if we have one.                          # Here we have a new header. Store the current sequence if we have one.
1710                          if ($id) {                          if ($id) {
1711                                  $retVal{$id} = uc $sequence;                  $retVal{$id} = lc $sequence;
1712                          }                          }
1713                          # Clear the sequence accumulator and save the new ID.                          # Clear the sequence accumulator and save the new ID.
1714                          ($id, $sequence) = ("$prefix$1", "");                          ($id, $sequence) = ("$prefix$1", "");
1715                  } else {                  } else {
1716                          # Here we have a data line, so we add it to the sequence accumulator.                          # Here we have a data line, so we add it to the sequence accumulator.
1717                          # First, we get the actual data out. Note that we normalize to upper              # First, we get the actual data out. Note that we normalize to lower
1718                          # case.                          # case.
1719                          $line =~ /^\s*(.*?)(\s|\n)/;                          $line =~ /^\s*(.*?)(\s|\n)/;
1720                          $sequence .= $1;                          $sequence .= $1;
# Line 1453  Line 1722 
1722          }          }
1723          # Flush out the last sequence (if any).          # Flush out the last sequence (if any).
1724          if ($sequence) {          if ($sequence) {
1725                  $retVal{$id} = uc $sequence;          $retVal{$id} = lc $sequence;
1726          }          }
1727          # Close the file.          # Close the file.
1728          close FASTAFILE;          close FASTAFILE;
# Line 1572  Line 1841 
1841  The next statement inserts a C<HasProperty> relationship between feature C<fig|158879.1.peg.1> and  The next statement inserts a C<HasProperty> relationship between feature C<fig|158879.1.peg.1> and
1842  property C<4> with an evidence URL of C<http://seedu.uchicago.edu/query.cgi?article_id=142>.  property C<4> with an evidence URL of C<http://seedu.uchicago.edu/query.cgi?article_id=142>.
1843    
1844  C<< $sprout->InsertObject('HasProperty', { 'from-link' => 'fig|158879.1.peg.1', 'to-link' => 4, evidence = 'http://seedu.uchicago.edu/query.cgi?article_id=142'}); >>  C<< $sprout->InsertObject('HasProperty', { 'from-link' => 'fig|158879.1.peg.1', 'to-link' => 4, evidence => 'http://seedu.uchicago.edu/query.cgi?article_id=142'}); >>
1845    
1846  =over 4  =over 4
1847    
# Line 1970  Line 2239 
2239          return @retVal;          return @retVal;
2240  }  }
2241    
2242    =head3 GetProperties
2243    
2244    C<< my @list = $sprout->GetProperties($fid, $key, $value, $url); >>
2245    
2246    Return a list of the properties with the specified characteristics.
2247    
2248    Properties are arbitrary key-value pairs associated with a feature. (At some point they
2249    will also be associated with genomes.) A property value is represented by a 4-tuple of
2250    the form B<($fid, $key, $value, $url)>. These exactly correspond to the parameter
2251    
2252    =over 4
2253    
2254    =item fid
2255    
2256    ID of the feature possessing the property.
2257    
2258    =item key
2259    
2260    Name or key of the property.
2261    
2262    =item value
2263    
2264    Value of the property.
2265    
2266    =item url
2267    
2268    URL of the document that indicated the property should have this particular value, or an
2269    empty string if no such document exists.
2270    
2271    =back
2272    
2273    The parameters act as a filter for the desired data. Any non-null parameter will
2274    automatically match all the tuples returned. So, specifying just the I<$fid> will
2275    return all the properties of the specified feature; similarly, specifying the I<$key>
2276    and I<$value> parameters will return all the features having the specified property
2277    value.
2278    
2279    A single property key can have many values, representing different ideas about the
2280    feature in question. For example, one paper may declare that a feature C<fig|83333.1.peg.10> is
2281    virulent, and another may declare that it is not virulent. A query about the virulence of
2282    C<fig|83333.1.peg.10> would be coded as
2283    
2284        my @list = $sprout->GetProperties('fig|83333.1.peg.10', 'virulence', '', '');
2285    
2286    Here the I<$value> and I<$url> fields are left blank, indicating that those fields are
2287    not to be filtered. The tuples returned would be
2288    
2289        ('fig|83333.1.peg.10', 'virulence', 'yes', 'http://www.somewhere.edu/first.paper.pdf')
2290        ('fig|83333.1.peg.10', 'virulence', 'no', 'http://www.somewhere.edu/second.paper.pdf')
2291    
2292    =cut
2293    #: Return Type @@;
2294    sub GetProperties {
2295        # Get the parameters.
2296        my ($self, @parms) = @_;
2297        # Declare the return variable.
2298        my @retVal = ();
2299        # Now we need to create a WHERE clause that will get us the data we want. First,
2300        # we create a list of the columns containing the data for each parameter.
2301        my @colNames = ('HasProperty(from-link)', 'Property(property-name)',
2302                        'Property(property-value)', 'HasProperty(evidence)');
2303        # Now we build the WHERE clause and the list of parameter values.
2304        my @where = ();
2305        my @values = ();
2306        for (my $i = 0; $i <= $#colNames; $i++) {
2307            my $parm = $parms[$i];
2308            if (defined $parm && ($parm ne '')) {
2309                push @where, "$colNames[$i] = ?";
2310                push @values, $parm;
2311            }
2312        }
2313        # Format the WHERE clause.
2314        my $filter = (@values > 0 ? (join " AND ", @where) : undef);
2315        # Ask for all the propertie values with the desired characteristics.
2316        my $query = $self->Get(['HasProperty', 'Property'], $filter, \@values);
2317        while (my $valueObject = $query->Fetch()) {
2318            my @tuple = $valueObject->Values(\@colNames);
2319            push @retVal, \@tuple;
2320        }
2321        # Return the result.
2322        return @retVal;
2323    }
2324    
2325  =head3 FeatureProperties  =head3 FeatureProperties
2326    
2327  C<< my @properties = $sprout->FeatureProperties($featureID); >>  C<< my @properties = $sprout->FeatureProperties($featureID); >>
# Line 2164  Line 2516 
2516  C<< my %subsystems = $sprout->SubsystemsOf($featureID); >>  C<< my %subsystems = $sprout->SubsystemsOf($featureID); >>
2517    
2518  Return a hash describing all the subsystems in which a feature participates. Each subsystem is mapped  Return a hash describing all the subsystems in which a feature participates. Each subsystem is mapped
2519  to the role the feature performs.  to the roles the feature performs.
2520    
2521  =over 4  =over 4
2522    
# Line 2174  Line 2526 
2526    
2527  =item RETURN  =item RETURN
2528    
2529  Returns a hash mapping all the feature's subsystems to the feature's role.  Returns a hash mapping all the feature's subsystems to a list of the feature's roles.
2530    
2531  =back  =back
2532    
2533  =cut  =cut
2534  #: Return Type %;  #: Return Type %@;
2535  sub SubsystemsOf {  sub SubsystemsOf {
2536          # Get the parameters.          # Get the parameters.
2537          my ($self, $featureID) = @_;          my ($self, $featureID) = @_;
2538          # Use the SSCell to connect features to subsystems.      # Get the subsystem list.
2539          my @subsystems = $self->GetAll(['ContainsFeature', 'HasSSCell', 'IsRoleOf'],          my @subsystems = $self->GetAll(['ContainsFeature', 'HasSSCell', 'IsRoleOf'],
2540                                                                          "ContainsFeature(to-link) = ?", [$featureID],                                                                          "ContainsFeature(to-link) = ?", [$featureID],
2541                                                                          ['HasSSCell(from-link)', 'IsRoleOf(from-link)']);                                                                          ['HasSSCell(from-link)', 'IsRoleOf(from-link)']);
# Line 2191  Line 2543 
2543          my %retVal = ();          my %retVal = ();
2544          # Loop through the results, adding them to the hash.          # Loop through the results, adding them to the hash.
2545          for my $record (@subsystems) {          for my $record (@subsystems) {
2546                  $retVal{$record->[0]} = $record->[1];          my ($subsys, $role) = @{$record};
2547            if (exists $retVal{$subsys}) {
2548                push @{$retVal{$subsys}}, $role;
2549            } else {
2550                $retVal{$subsys} = [$role];
2551            }
2552          }          }
2553          # Return the hash.          # Return the hash.
2554          return %retVal;          return %retVal;
2555  }  }
2556    
2557    =head3 SubsystemList
2558    
2559    C<< my @subsystems = $sprout->SubsystemList($featureID); >>
2560    
2561    Return a list containing the names of the subsystems in which the specified
2562    feature participates. Unlike L</SubsystemsOf>, this method only returns the
2563    subsystem names, not the roles.
2564    
2565    =over 4
2566    
2567    =item featureID
2568    
2569    ID of the feature whose subsystem names are desired.
2570    
2571    =item RETURN
2572    
2573    Returns a list of the names of the subsystems in which the feature participates.
2574    
2575    =back
2576    
2577    =cut
2578    #: Return Type @;
2579    sub SubsystemList {
2580        # Get the parameters.
2581        my ($self, $featureID) = @_;
2582        # Get the list of names.
2583        my @retVal = $self->GetFlat(['ContainsFeature', 'HasSSCell'], "ContainsFeature(to-link) = ?",
2584                                    [$featureID], 'HasSSCell(from-link)');
2585        # Return the result.
2586        return @retVal;
2587    }
2588    
2589  =head3 RelatedFeatures  =head3 RelatedFeatures
2590    
2591  C<< my @relatedList = $sprout->RelatedFeatures($featureID, $function, $userID); >>  C<< my @relatedList = $sprout->RelatedFeatures($featureID, $function, $userID); >>
# Line 2615  Line 3004 
3004      return %retVal;      return %retVal;
3005  }  }
3006    
3007    =head3 MyGenomes
3008    
3009    C<< my @genomes = Sprout::MyGenomes($dataDir); >>
3010    
3011    Return a list of the genomes to be included in the Sprout.
3012    
3013    This method is provided for use during the Sprout load. It presumes the Genome load file has
3014    already been created. (It will be in the Sprout data directory and called either C<Genome>
3015    or C<Genome.dtx>.) Essentially, it reads in the Genome load file and strips out the genome
3016    IDs.
3017    
3018    =over 4
3019    
3020    =item dataDir
3021    
3022    Directory containing the Sprout load files.
3023    
3024    =back
3025    
3026    =cut
3027    #: Return Type @;
3028    sub MyGenomes {
3029        # Get the parameters.
3030        my ($dataDir) = @_;
3031        # Compute the genome file name.
3032        my $genomeFileName = LoadFileName($dataDir, "Genome");
3033        # Extract the genome IDs from the files.
3034        my @retVal = map { $_ =~ /^(\S+)/; $1 } Tracer::GetFile($genomeFileName);
3035        # Return the result.
3036        return @retVal;
3037    }
3038    
3039    =head3 LoadFileName
3040    
3041    C<< my $fileName = Sprout::LoadFileName($dataDir, $tableName); >>
3042    
3043    Return the name of the load file for the specified table in the specified data
3044    directory.
3045    
3046    =over 4
3047    
3048    =item dataDir
3049    
3050    Directory containing the Sprout load files.
3051    
3052    =item tableName
3053    
3054    Name of the table whose load file is desired.
3055    
3056    =item RETURN
3057    
3058    Returns the name of the file containing the load data for the specified table, or
3059    C<undef> if no load file is present.
3060    
3061    =back
3062    
3063    =cut
3064    #: Return Type $;
3065    sub LoadFileName {
3066        # Get the parameters.
3067        my ($dataDir, $tableName) = @_;
3068        # Declare the return variable.
3069        my $retVal;
3070        # Check for the various file names.
3071        if (-e "$dataDir/$tableName") {
3072            $retVal = "$dataDir/$tableName";
3073        } elsif (-e "$dataDir/$tableName.dtx") {
3074            $retVal = "$dataDir/$tableName.dtx";
3075        }
3076        # Return the result.
3077        return $retVal;
3078    }
3079    
3080  =head2 Internal Utility Methods  =head2 Internal Utility Methods
3081    
3082  =head3 ParseAssignment  =head3 ParseAssignment
# Line 2690  Line 3152 
3152      return $retVal;      return $retVal;
3153  }  }
3154    
3155    =head3 AddProperty
3156    
3157    C<< my  = $sprout->AddProperty($featureID, $key, $value, $url); >>
3158    
3159    Add a new attribute value (Property) to a feature. In the SEED system, attributes can
3160    be added to almost any object. In Sprout, they can only be added to features. In
3161    Sprout, attributes are implemented using I<properties>. A property represents a key/value
3162    pair. If the particular key/value pair coming in is not already in the database, a new
3163    B<Property> record is created to hold it.
3164    
3165    =over 4
3166    
3167    =item peg
3168    
3169    ID of the feature to which the attribute is to be replied.
3170    
3171    =item key
3172    
3173    Name of the attribute (key).
3174    
3175    =item value
3176    
3177    Value of the attribute.
3178    
3179    =item url
3180    
3181    URL or text citation from which the property was obtained.
3182    
3183    =back
3184    
3185    =cut
3186    #: Return Type ;
3187    sub AddProperty {
3188        # Get the parameters.
3189        my ($self, $featureID, $key, $value, $url) = @_;
3190        # Declare the variable to hold the desired property ID.
3191        my $propID;
3192        # Attempt to find a property record for this key/value pair.
3193        my @properties = $self->GetFlat(['Property'],
3194                                       "Property(property-name) = ? AND Property(property-value) = ?",
3195                                       [$key, $value], 'Property(id)');
3196        if (@properties) {
3197            # Here the property is already in the database. We save its ID.
3198            $propID = $properties[0];
3199            # Here the property value does not exist. We need to generate an ID. It will be set
3200            # to a number one greater than the maximum value in the database. This call to
3201            # GetAll will stop after one record.
3202            my @maxProperty = $self->GetAll(['Property'], "ORDER BY Property(id) DESC", [], ['Property(id)'],
3203                                            1);
3204            $propID = $maxProperty[0]->[0] + 1;
3205            # Insert the new property value.
3206            $self->Insert('Property', { 'property-name' => $key, 'property-value' => $value, id => $propID });
3207        }
3208        # Now we connect the incoming feature to the property.
3209        $self->Insert('HasProperty', { 'from-link' => $featureID, 'to-link' => $propID, evidence => $url });
3210    }
3211    
3212    
3213    
3214  1;  1;

Legend:
Removed from v.1.14  
changed lines
  Added in v.1.25

MCS Webmaster
ViewVC Help
Powered by ViewVC 1.0.3