the nucleolus is a highly conserved nuclear organelle whose main function is to coordinate the synthesis and assembly of ribosome subunits ( 1 ) .
previously we described a nucleolar proteome database ( nopdb2.0 : http://www.lamondlab.com/nopdb ) that archived data on > 700 proteins that were identified by multiple mass spectrometry ( ms ) analyses from highly purified preparations of human nucleoli ( 2 ) .
each protein entry was annotated with information about its corresponding gene , its domain structures and relevant protein homologues across species , as well as documenting its ms identification history , including all the peptides sequenced by tandem ms / ms .
moreover , data showing the quantitative changes in the relative levels of approximately 500 nucleolar proteins were compared at different time points upon transcriptional inhibition ( 3 ) .
the data presented by the previous nopdb , version 2.0 , was held in a flat file database . due to the aggregated nature of the data ,
the peptide data for a single protein were merged within this database rather than stored separately .
these scripts were able to extract the relevant data from the flat file database to create static html pages .
after running the scripts , a page was created on the server for each protein .
each time data were updated in the flat files , the perl scripts had to be run again in order to reproduce the static html pages .
this process of having to reproduce the static html protein pages after each database update was highly inefficient and time consuming .
furthermore , the capabilities of the version 2.0 nopdb database were limited with respect to security , ease of use , accessibility , maintainability and expandability .
for example , a number of security concerns arose regarding the perl scripts , which with limited documentation , proved very difficult to resolve .
the new version of the nopdb3.0 ( http://www.lamondlab.com/nopdb3.0/ ) consists of a unique , secure , extendable content management system , holding advanced nucleolar proteomics data .
the created application includes a dynamic relational database , which is kept up to date by members of the lamond group .
it also allows the query of protein data hosted within the database by external users , either using the custom built interface provided by the lamond group , or by building custom web tools that access data via the application programming interface ( api ) .
in addition to the dynamic interfaces provided by the new content management system , the data included in the nucleolar proteome are also dynamically updated with proteins identified from several different cell lines , using various instruments by members of the laboratory . from the initial 700 proteins identified in the previous iteration of the nopdb , we have now identified over 50 000 peptides contained in over 4500 human proteins from purified nucleoli , providing significantly enhanced coverage of the nucleolar proteome .
we have established the new version of the nucleolar proteome database ( nopdb3.0 ) , which archives all the human nucleolar proteins identified to date by the lamond group and their collaborators using ms analyses ( 13 ) .
this current version 3.0 of the database is available at http://www.lamondlab.com/nopdb3.0/ and is searchable either by protein name , protein sequence , motif ( 46 ) , gene ontology ( go ) ( 7 ) terms or by setting the range of the predicted isoelectric point and/or molecular weight ( figure 1 ) . to date , nopdb3.0 archives over 4500 human nucleolar proteins verified by multiple ms analyses in different cell lines .
the nopdb3.0 provides information on multiple parameters , including protein name , accession number , gene symbol , gene name , sequence , molecular weight , isoelectric point ( pi ) , peptides identified , experiments in which the protein was identified , motifs and go annotation .
the previous version of the database ( 2 ) will still be available through our website at http://www.lamondlab.com / nopdb/. 
 figure 1.snapshots of the nopdb3.0 ( http://www.lamondlab.com/nopdb3.0/ ) . for illustration ,
the database was searched to identify a protein phosphatase 1 ( pp1 ) isoform and here we show an overview page for this protein documenting its sequence , peptides identified , etc .
the database was searched to identify a protein phosphatase 1 ( pp1 ) isoform and here we show an overview page for this protein documenting its sequence , peptides identified , etc .
the new nopdb3.0 application consists of a multi - tier architecture , where the data storage , business logic and client interface are separate components .
the database is structured ( figure 2 ) to allow easy extendibility and maintenance in the future . in order to extract useful data
the purpose of the business logic layer is to act as an interface between the client - side application and database .
the business logic and client interface can both reside on any apache web server capable of serving php classes and the client interface , which is built in adobe flex .
adobe flex was chosen as it allows rich internet applications ( rias ) to be prototyped and developed rapidly , with the end product running across a wide range of client browsers . 

figure 2.entity relationship ( er ) diagram depicting the relationships between the tables present in the mysql database implemented for the nopdb3.0 content management system . entity relationship ( er ) diagram depicting the relationships between the tables present in the mysql database implemented for the nopdb3.0 content management system .
version 3.0 of the nopdb is an entirely new implementation using a fully relational design with major improvements over previous versions and additional functionality .
the newly created database holds data of higher granularity , storing data at the peptide level as opposed to collated data on proteins .
this higher granularity also means that results from new experiments can be directly uploaded to the database without prior processing , as the direct output from ms - based proteomics analyses is peptide data .
the application has the ability to interpret data and therefore aggregate it to provide metadata for proteins on a usable , graphical interface .
the structure of the application has been designed using the model view controller design pattern ( 8) , thus meaning that the functionality is separated from the overall look and feel of the application to ensure a more customisable solution .
all communication between the database and application has been implemented to pass through the custom made api ( 9 ) .
furthermore , in this new version 3.0 application , the graphical user interface to the database is able to create data pages  on the fly using the custom api rather than serving static data pages , as in previous versions .
this api not only acts as a security blanket around the database , it also provides the ability for users to create their own websites and/or applications that represent the data being stored in the proteomics database .
external users can make use of the api through the rest ( representational state transfer ) ( 10 ) approach .
hence , external programmers can retrieve content in xml ( extensible markup language ) format , from the database , by accessing well - documented uniform resource locators ( urls ) .
the application also facilitates mining of stored data , with data being stored in a relational structure that is well documented
. thus tools can be built to search , analyse , read and understand the data .
this mining capability is evident within the application , with the database being searchable by multiple parameters , including gene names , amino acid or nucleotide sequences , sequence motifs , or by limiting the range for isoelectric points and/or molecular weights .
the database is also searchable by interpro motif numbers ( database of protein families , domains and functional sites ) ( 46 ) and by go terms ( describe gene products in terms of their associated biological processes , cellular components and molecular functions in a species - independent manner ) ( 7 ) .
furthermore , the nopdb3.0 application uses the api to create dynamically generated graphs , allowing the users to visualise the data produced from experiments and enabling cross analysis between experiments .
the application itself is designed with three levels of access , to facilitate management and to prevent unauthorised use of the system .
users are provided with different levels of access according to their needs , which are seamlessly enforced by the application .
this security ensures that the data remain accurate and the quality of the data is not compromised .
furthermore , this application creates a platform for the lamond group to share their data with the wider cell biology community .
the database has been populated with different sets of experiments , performed in the lamond laboratory , that identify proteins in purified preparations of human nucleoli .
the increased coverage of the human nucleolus proteome is illustrated by the fact that nopdb3.0 now includes over 80% of ribosomal proteins , as opposed to the 28% described in nopdb version 2.0 .
we estimate that nopdb3.0 contains over 80% of the main human nucleolus proteins . the proteins in the database will be regularly updated as more experiments are performed in the lamond laboratory .
this work was supported by a wellcome trust programme grant ( 073980/z/03/z ) and by an interdisciplinary rasor ( radical solutions for researching the proteome ) initiative , which is supported by the biotechnology and biological sciences research council , engineering and physical sciences research council , scottish higher education funding council and medical research council .
 an experimental data handling system has been created as an update to the previous nucleolar proteome database ( nopdb3.0 : http://www.lamondlab.com/nopdb3.0/ ) . 
 this updated system is able to manage large data sets identified by multiple mass spectrometry and has been used to analyse highly purified preparations of human nucleoli from different cell lines . 
 the newly created application includes a dynamic relational database , which is kept up to date by laboratory staff . 
 the data are further annotated with information from specific external sources on the web , including the ipi and gene ontology databases . 
 in addition , an application programming interface provides external users with a portal to link into the nucleolar proteome database and hence , gain access to continually updated results . from the initial 700 human proteins identified in the previous iteration of the nopdb , we have now identified over 50 000 peptides contained in over 4500 human proteins from purified nucleoli , providing enhanced coverage of the nucleolar proteome . 
INTRODUCTION
DATABASE ACCESS
DATABASE IMPLEMENTATION
DATABASE CONTENT
FUNDING