[GeneX-dev] Re: Matrix update

[Harry M. <hj...@ta...>]

OK - then let's follow Jason's rec to let him have the 2 days to tidy up the 
schema and Mason stuff - meanwhile we write and tidy the docs for GeneX and the 
Web site.  On Wednesday, I'll refresh matrix and we can start loading data in anger.

hjm



jw...@gm... wrote:
> Hi Harry,
>    I would like matrix to be refreshed; I agree that the changes Jason suggests below add some clarity to the installation process so should be incorporated. I would especially like to be sure that the interface bugs Jason has been batting away at have been fixed on matrix- I ran into a bunch of them on Saturday and I don't want to re-document what has already been fixed.
>    Cheers,
>    Jennifer
> 
> 
> 
> ----- Original Message -----
> From: Harry Mangalam <hj...@ta...>
> Date: Sunday, May 2, 2004 1:18 pm
> Subject: Re: [GeneX-dev] make configure
> 
> 
>>This sounds good - I was going to suggest that we 
>>consolidate/clean up the 
>>recon/configure divergence anyway.
>>
>>And making things clearly genex-related is a good idea for all 
>>kinds of reasons.
>>
>>Jennifer, what's the status of matrix re: data loading?  DO you 
>>want me to 
>>refresh it to get these things incorporated or should we leave it 
>>alone - these 
>>changes are administrative and won't change any 
>>db/schema/interface details.
>>
>>hjm
>>
>>
>>Jason E. Stewart wrote:
>>
>>>Hey all,
>>>
>>>It looks like a change I made to the 'Configure' script on 3/23/2004
>>>got lost when recon.pl was split off - I had renamed the 'readonly'
>>>user to 'sessions' because that is the name of the only table that
>>>user has access to. This wasn't obvious because I never use the
>>>hard-coded name of any user in the API - I always use the Perl
>>>Config.pm variable, e.g. $Bio::Genex::Config->{GENEX_TEST_USER}.
>>>
>>>But it showed up when I was helping Durga debug her installer 
>>
>>problem.> 
>>
>>>I'm proposing the following changes:
>>>1) Rename recon.pl to Configure - make it the 'official' 
>>
>>configuration>    tool. It's had enough testing now, I think it's 
>>stable.> 
>>
>>>2) Make the genex administrative user names clearly genex
>>>   specific. This is in keeping with the role names, e.g. 
>>
>>genex_admin,>    genex_user, etc. So instead of 'sessions' make it 
>>'genex_sessions',>    etc. This way our administrative users don't 
>>conflict with other
>>
>>>   potential users.
>>>
>>>3) Instead of only a test user that has only USER level priveleges,
>>>   add a second user that has CURATOR priveleges as well. This 
>>
>>came up
>>
>>>   when I was adding the sample data set - I needed a user with
>>>   curator priveleges, so I had to give them to the 'test' user.
>>>
>>>These changes are relatively minor, but I believe they will make 
>>
>>long> term maintenance simpler.
>>
>>>I'm asking this to the list, because it will require a 'make
>>>uninstall' for every installation (the old users will need to be
>>>deleted from the DB).
>>>
>>>Cheers,
>>>jas.
>>>
>>>
>>>-------------------------------------------------------
>>>This SF.Net email is sponsored by: Oracle 10g
>>>Get certified on the hottest thing ever to hit the market... 
>>
>>Oracle 10g. 
>>
>>>Take an Oracle 10g class now, and we'll give you the exam FREE.
>>>http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
>>>_______________________________________________
>>>Genex-dev mailing list
>>>Gen...@li...
>>>https://lists.sourceforge.net/lists/listinfo/genex-dev
>>>
>>
>>-- 
>>Cheers, Harry
>>Harry J Mangalam - 949 856 2847 (v&f) - hj...@ta...
>>            <<plain text preferred>>
>>
>>

-- 
Cheers, Harry
Harry J Mangalam - 949 856 2847 (v&f) - hj...@ta...
             <<plain text preferred>>