Difference between revisions of "Malverso Week 14"

From LMU BioDB 2015
Jump to: navigation, search
(completed milestone 3)
(Milestone 4: Species Export Customization: committed to github)
Line 42: Line 42:
  
 
==Milestone 4: Species Export Customization==
 
==Milestone 4: Species Export Customization==
Based on observations from the GenMAPP User and QA, determine and document (as thoroughly as possible) any other modified export behavior that GenMAPP Builder will have to manifest for this species.
+
*I uploaded my dist file to the wiki and gave it to Josh so that he could test it out using Microsoft Access and TallyEngine and GenMapp.  
Implement this export behavior.
+
===Comitting My Code===
As needed, commit and push your work to your GitHub branch.
+
*# I right-clicked on the ''gmbuilder'' project folder and chose '''Team > Synchronize Workspace''' from the menu that appeared.
Additional milestones will depend on how the rest of the project goes, and the bugs/features generated by that work.
+
# I was switched to the ''Team Synchronization'' perspective.
Document/log all work done, problems encountered, and how they were resolved.
+
# I saw a ''Synchronize'' tab. I commited the right-pointing gray-arrowed files by right-clicking on them and choosing ''Commit...''.
When your work is complete, issue a GitHub pull request to merge your branch into the main development line.
+
# I verified that the files I wanted to commit were checked in the ensuing ''Commit Changes'' dialog.
 
+
# I added a quick description to what I was committing.  
 
+
# I chose ''Commit and Push''.
 
+
#* This will both save a version of my files ''and'' send the latest changes to GitHub.
 
{{Template:Malverso}}
 
{{Template:Malverso}}

Revision as of 23:23, 3 December 2015

Milestone 3: Species Profile Creation

Creating the Species Profile

  1. I exposed the contents of the src folder, right-clicked on the edu.lmu.xmlpipedb.gmbuilder.databasetoolkit.profiles package and chose New > Class from the popup menu.
  2. In the dialog that appeared, I entered the following:
    • Name: ShewanellaOneidensisUniProtSpeciesProfile
    • Superclass: edu.lmu.xmlpipedb.gmbuilder.databasetoolkit.profiles.UniProtSpeciesProfile
  3. I clicked Finish. There was a new .java file within the edu.lmu.xmlpipedb.gmbuilder.databasetoolkit.profiles package.

Customizing the Species Profile

  • I opened the file that I have just created.
  • I found the Taxonomy ID from this link.
  • I added the following constructor block right below the public class line in the file:
public ShewanellaOneidensisUniProtSpeciesProfile() {
    super("Shewanella oneidensis",
        211586,
        "This profile customizes the GenMAPP Builder export for " +
            "Shewanella oneidensis" +
            " data loaded from a UniProt XML file.");
}
  • The species specific database link I found by searching for a gene on our MOD and then replacing the gene identification in the link with a '~'.
  • To customize the species profile with the species name in the OrderedLocusNames record of the Systems table as well as a link query for that same record, I added the following method block right below the constructor block that I added above:
@Override
public TableManager getSystemsTableManagerCustomizations(TableManager tableManager, DatabaseProfile dbProfile) {
    super.getSystemsTableManagerCustomizations(tableManager, dbProfile);
    tableManager.submit("Systems", QueryType.update, new String[][] {
        { "SystemCode", "N" },
        { "Species", "|" + getSpeciesName() + "|" }
    });

    tableManager.submit("Systems", QueryType.update, new String[][] {
        { "SystemCode", "N" },
        { "Link", "http://bacteria.ensembl.org/shewanella_oneidensis_mr_1/Search/Results?species=Shewanella%20oneidensis%20MR-1;idx=;q=~;site=ensemblthis" }
    });

    return tableManager;
}
  • My code had a red error badge at this point, and I fixed this by choosing Organize Imports from the Source menu, which imported necessary classes.


Milestone 4: Species Export Customization

  • I uploaded my dist file to the wiki and gave it to Josh so that he could test it out using Microsoft Access and TallyEngine and GenMapp.

Comitting My Code

    1. I right-clicked on the gmbuilder project folder and chose Team > Synchronize Workspace from the menu that appeared.
  1. I was switched to the Team Synchronization perspective.
  2. I saw a Synchronize tab. I commited the right-pointing gray-arrowed files by right-clicking on them and choosing Commit....
  3. I verified that the files I wanted to commit were checked in the ensuing Commit Changes dialog.
  4. I added a quick description to what I was committing.
  5. I chose Commit and Push.
    • This will both save a version of my files and send the latest changes to GitHub.

Team Page

Heavy Metal HaterZ

Assignments

Individual Journal Entries

Shared Journal Entries