Re: gsoc2008 - wikipathways required skills question

[Martijn van Iersel]

Hi Pigno

Experience with the Mediawiki code base is not really a requirement.
You'll have to learn about it during your project of course. The
mediawiki code base is indeed large but it is well structured and easy
to grasp if you are reasonably confident with php.

If you're going for idea 2, you probably will need to study the
mediawiki structure in detail before you can start on the
implementation. Idea 4 could be developed as a mediawiki extension, so
that you only need to look at the mediawiki extension hooks.

regards,
Martijn van Iersel

P.S. I added the wikipathways-user mailinglist to the Cc, so we can
continue this thread over there.

Alexander Pico wrote:
> Hi Pigno,
>
> Thank you for your interest in our projects. You'll want to direct
> WikiPathways-related questions to a different mailing list where those
> developers live:
>
> http://groups.google.com/group/wikipathways-user
>
> Repost there and the right people will be able to reply.
> -Alex
>
>
> On 3/27/08 3:54 PM, "pigno" <pig...@gmail.com> wrote:
>
>
>> Hello,
>>
>> I'm interested in 2nd et 4th idea, related to the wikipathways
>> project. I'm student in Master of Biotechnology and Biochemistry with
>> some Perl and PHP experience. I don't understand what the wikimedia
>> skill implies. would you please discribe it in more detail. wikimedia
>> is a huge project with very large code base and the only experience I
>> have is as a simple user.
>>
>> Thank you in advance,
>>
>> pigno
>>
>>
>
>
>
> >
>
>

[pigno]

Hi Martjin,

thanks for your answer. I agree that Mediawiki code base is well-
structured. I am thinking about the 4th idea. I will try to come with
something this WE. Are you cheking the groups posts this weekend?

regards,

p.

On 28 mar, 09:53, Martijn van Iersel <mvanier...@gmail.com> wrote:
> Hi Pigno
>
> Experience with the Mediawiki code base is not really a requirement.
> You'll have to learn about it during your project of course. The
> mediawiki code base is indeed large but it is well structured and easy
> to grasp if you are reasonably confident with php.
>
> If you're going for idea 2, you probably will need to study the
> mediawiki structure in detail before you can start on the
> implementation. Idea 4 could be developed as a mediawiki extension, so
> that you only need to look at the mediawiki extension hooks.
>
> regards,
> Martijn van Iersel
>
> P.S. I added the wikipathways-user mailinglist to the Cc, so we can
> continue this thread over there.
>
> Alexander Pico wrote:
> > Hi Pigno,
>
> > Thank you for your interest in our projects. You'll want to direct
> > WikiPathways-related questions to a different mailing list where those
> > developers live:
>
> >http://groups.google.com/group/wikipathways-user
>
> > Repost there and the right people will be able to reply.
> > -Alex
>

[Alexander Pico]

Hi Pigno,

I'll be on this weekend. Also keep an eye out for extensions to the
deadline. Google likes to do this... But, be ready to submit by the 31st
just in case.

For IDEA 4, it is critical that you understand the perspective of a
potential curator. I would recommend going through the tutorial
(http://wikipathways.org/index.php/Help:Tutorial) to get a sense of what is
involved in editing, the investment in time, etc.

Your proposal should include a clear vision of what the Curator's Dashboard
could look like and what functions it would have to help make it easier for
an individual to keep track of pathways they are interested in and to make
certain types of edits easy (such as deriving and applying diffs on other
pathways, and for other species). Adding new ideas for the dashboard would
help your application stand out as well.

Best of luck,
-Alex

[pigno]

hello, i came with some insights about idea #4:

draft of idea #4 wikipathways - Curator's Dashboard

The goal is to create a curator's dashboard page. This page will
contain the his curation history of the current pathway in table
format with several editable categories ( pathway image, description,
comments, bibliography, etc.). Clicking on each category will permit
the curator to see the original item, edit, add or delete it. Each
modification to the pathway will be represented as a entry in this
table. The already existing actions in the "History" pathway table
will be also available. New changes can then be applied to other
pathways, using difficult and gpmlpatch tools if appropriate. For
visualization of the modifications in the graphical representation, I
can use the already existing methods to highlight the changes. It
would be helpful for current curator to have in mind previous changes
submitted by other users, so edits made by other curators/users can be
represented in a different table with similar features. To facilitate
communications between scientist, editing the same pathway a
discussion box can be added. In this way, author and curators could
communicate in a simple manner, rather than using email.

The final version of the pathway, as well as it's categories, should
be tagged as "approved" by the curator. If multiple curantions exist,
the approved tag will be showed for each author. This tag will be
displayed in each manually curated pathway with a link to the
curator's email and/or a brief display of the curator's activity for
this pathway.

I appeciate any comments, toughts or simples remarks.

Thank you in advance.

PS : I will try post my final proposal tomorrow...

[pigno]

I would like to add that for this idea, i will be developing a
MediaWiki extension using the existing entry points and hooks...

[pigno]

I've posted my proposal on :



http://curatorsdashboard.weebly.com/


any feedback will be appreciated

thanks,

p.