Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

Unless you do this only as a learning exercise, I think that the main question you should answer for yourself: is it not unnecessary? I am not quite sure, but I think EnsEMBL, UniProt, Entrez between them already have a lot, perhaps even all of the things that that PyCon quote mentions. EBI, EMBL, NCBI, they all have large teams working on both data, website, and interfaces. Make sure you find a useful addition/niche before even starting to work on it.

You also omit to mention what this would be used for. What is the audience? What kind of queries do you want to answer? How fast, how many, how reliably.

In general, I think the size of the source-databases involved (chebi, GO, human and perhaps other genomes) would make a database necessary, unless you envisage a system that makes use their respective API's.

I don't think an ORM (or which ORM) should be your first concern. Such things are pretty much downstream of the above questions.

A last consideration: have you contacted the poster presenters? Most people love it when others show interest in their work, and they are possibly quite willing to share their work. Even if you don't use it it may give you good ideas.


In reply to Re: Using Perl in a personalized medicine application. by erix
in thread Using Perl in a personalized medicine application. by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others chanting in the Monastery: (3)
As of 2024-04-19 15:32 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found