NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin
Wiki Markup
{scrollbar:icons=false}

h1. A Step-by-Step Guide to Create a MAGE-TAB Template Specific to RPLA Project

*Topic*: caArray Installation and Upgrade

*Release*: caArray 2.4.0

*Date entered*: 04/20/2011

{panel:title=Contents of this Page}
{toc:minLevel=2}
{panel}

h2. Introduction

Developed by Leandro Hermida, this step-by-step guide will help RPLA project user to create a RPLA specific MAGE-TAB template.

h2. Create new provider(s)

Create RPLA providers in the contact table as for other array providers:
{code}insert into contact (discriminator, provider, name) values ('O', 1,'Zeptosens');{code}

After the insert, use the statement below to find the ID for the contact just created:
{code}Select ID from contact where name ='Zeptosens';{code}

h2. Create new Assay Type

Create a new RPLA assay type in the database in the assay_type table:
{code}insert into assay_type (name) values ('RPLA');{code}

h2. Check if caArray is a valid Term Source

Since a new technical term: *reverse_phase_protein_array_features* would be inserted into term_source table under the source of caArray, it is necessary to check if the source of \*caArray*has already been added in term_source table. During the normal caArray installation, caArray should have been added to the term_source table with a default ID =4. To verify, apply the select statement below:
{code}select * from term_source where name='caArray'{code}

If *caArray* is not a valid source in the term_source table, it should be added with the insert statement below:
{code}insert into term_source (name, version, url) values ('caArray','2.0','https://array.nci.nih.gov'){code}

h2. Add a new terminology term

After the source *caArray* has been added, use the SELECT statement above to find the ID for the source *caArray* just created in the *term_source* table. The id will be used in the insert statement below to add the new terminology *reverse_phase_protein_array_features* to the term table:
{code}insert into term (value, source) values('reverse_phase_protein_array_features', <id of term_source inserted above>);{code}

Use the SELECT statement below to find the ID for the term just created:
{code}SELECT ID from term where value = 'reverse_phase_protein_array_features';{code}

Use this ID in the INSERT statement below:
{code}insert into term_categories (term_id, category_id) values (<id of term inserted above>, 224);{code}

h2. Create a dummy Array Design File for RPLA

Create MAGE-TAB ADF dummy array design files (.ADF files) for the array provider *Zeptosens*, created in Step 1. The dummy file can be a empty file with a simple header.

h2. Upload the Dummy Array Design file in caArray

Upload new array designs for each ADF using the caArray web application (For more details, please refer to [Using caArray: Uploading Array Design File|caArray Demos^Array-design-file.ppt]). The new file will have the final status of "Imported no Parsed".

h2. Update Array_Design Table

After uploading dummy array designs into caArray, update their array_design table entries in the database to lsid_authority to be Zeptosens.com, lsid_namespace to be PhysicalArrayDesign. This SQL statement will work only after the array design file is added to caArray.

{code}update array_design set lsid_authority = 'Zeptosens.com',
 lsid_namespace = 'PhysicalArrayDesign' where provider = <id of contact inserted above>;{code}

h2. Create New File Types for RPLA data files

The next step is to create new file types for the RPLA data file formats you have. This modification is not at the database level, but file level. The file is:

{code}caarray_src_2_3_1_1/caarray.war/src/main/java/ApplicationResources.properties{code}

Following is an example the RPLA data file in text format:

{code}experiment.files.filetype.Zeptosens_TXT = Zeptosens TXT{code}

After the properties is edited, caArray must be rebuilt and redeployed.

h2. Have a comment?

Please leave your comment in the [caArray End User Forum|https://cabig-kc.nci.nih.gov/Molecular/forums/viewtopic.php?f=6&t=577].

{scrollbar:icons=false}