Detailed Documentation of Form and Scripts

Currently, on mangolassi the ccc.cgi and other scripts and files are here:

azurebrd/public_html/cgi-bin/forms/ccc

• accession
  • This is a file that maps WB WBPaper IDs to PMIDs.
  • For WB, this file is generated each time the search is performed.
• ccc_celegans_2013only
  • I believe these are old test files that can be deleted.
• ccc.cgi
  • This is the code for the curation form.
  • ccc.cgi Documentation
• ccc.js
  • This is the ccc form javascript code.
  • If we want to change the number of characters needed to begin autocomplete, we can do that here.
• c_elegans.WS234.xrefs.txt and c_elegans.WS236.xrefs.txt
  • These are files generated with each WB build that were used to create the WB gpi file.
• generate_gpi.pl
  • This is the script that will be used to manually generate a new gpi file for WB.
• jquery
  • This directory contains...
• notes
  • This file contains a short bit about mapping WBGene IDs to UniProtKB accessions for the gpi file.
• scripts
  • This directory contains:
    • accession file - This is a mapping file that contains the mappings between WBPaper IDs and PMIDs as well as TAIR doc IDs and PMIDs. Note that we need PMIDs to send annotations to Protein2GO.
    • create_ccc_pgcuration.pl - This perl script creates two postgres tables:

creates these two tables:

ccc_sentenceclassification
  ccc_mod
  ccc_file 
  ccc_paper 
  ccc_section 
  ccc_sentnum 
  ccc_sentenceclassification
  ccc_comment 
  ccc_curator 
  ccc_timestamp

ccc_sentenceannotation
  ccc_mod text,
  ccc_file text,
  ccc_paper text,
  ccc_section text,
  ccc_sentnum text,
  ccc_geneproduct text,
  ccc_component text,
  ccc_goterm text,
  ccc_evidencecode text,
  ccc_with text,
  ccc_alreadycurated text,
  ccc_comment text,
  ccc_valid text,
  ccc_ptgoid text,
  ccc_curator text,
  ccc_timestamp

Back to WormBase