Serveur d'exploration Cyberinfrastructure

Attention, ce site est en cours de développement !
Attention, site généré par des moyens informatiques à partir de corpus bruts.
Les informations ne sont donc pas validées.
***** Acces problem to record *****\

Identifieur interne : 000574 ( Pmc/Corpus ); précédent : 0005739; suivant : 0005750 ***** probable Xml problem with record *****

Links to Exploration step


Le document en format XML

<record>
<TEI>
<teiHeader>
<fileDesc>
<titleStmt>
<title xml:lang="en">BioLit: integrating biological literature with databases</title>
<author>
<name sortKey="Fink, J Lynn" sort="Fink, J Lynn" uniqKey="Fink J" first="J. Lynn" last="Fink">J. Lynn Fink</name>
</author>
<author>
<name sortKey="Kushch, Sergey" sort="Kushch, Sergey" uniqKey="Kushch S" first="Sergey" last="Kushch">Sergey Kushch</name>
</author>
<author>
<name sortKey="Williams, Parker R" sort="Williams, Parker R" uniqKey="Williams P" first="Parker R." last="Williams">Parker R. Williams</name>
</author>
<author>
<name sortKey="Bourne, Philip E" sort="Bourne, Philip E" uniqKey="Bourne P" first="Philip E." last="Bourne">Philip E. Bourne</name>
</author>
</titleStmt>
<publicationStmt>
<idno type="wicri:source">PMC</idno>
<idno type="pmid">18515836</idno>
<idno type="pmc">2447735</idno>
<idno type="url">http://www.ncbi.nlm.nih.gov/pmc/articles/PMC2447735</idno>
<idno type="RBID">PMC:2447735</idno>
<idno type="doi">10.1093/nar/gkn317</idno>
<date when="2008">2008</date>
<idno type="wicri:Area/Pmc/Corpus">000574</idno>
</publicationStmt>
<sourceDesc>
<biblStruct>
<analytic>
<title xml:lang="en" level="a" type="main">BioLit: integrating biological literature with databases</title>
<author>
<name sortKey="Fink, J Lynn" sort="Fink, J Lynn" uniqKey="Fink J" first="J. Lynn" last="Fink">J. Lynn Fink</name>
</author>
<author>
<name sortKey="Kushch, Sergey" sort="Kushch, Sergey" uniqKey="Kushch S" first="Sergey" last="Kushch">Sergey Kushch</name>
</author>
<author>
<name sortKey="Williams, Parker R" sort="Williams, Parker R" uniqKey="Williams P" first="Parker R." last="Williams">Parker R. Williams</name>
</author>
<author>
<name sortKey="Bourne, Philip E" sort="Bourne, Philip E" uniqKey="Bourne P" first="Philip E." last="Bourne">Philip E. Bourne</name>
</author>
</analytic>
<series>
<title level="j">Nucleic Acids Research</title>
<idno type="ISSN">0305-1048</idno>
<idno type="eISSN">1362-4962</idno>
<imprint>
<date when="2008">2008</date>
</imprint>
</series>
</biblStruct>
</sourceDesc>
</fileDesc>
<profileDesc>
<textClass></textClass>
</profileDesc>
</teiHeader>
<front>
<div type="abstract" xml:lang="en">
<p>BioLit is a web server which provides metadata describing the semantic content of all open access, peer-reviewed articles which describe research from the major life sciences literature archive, PubMed Central. Specifically, these metadata include database identifiers and ontology terms found within the full text of the article. BioLit delivers these metadata in the form of XML-based article files and as a custom web-based article viewer that provides context-specific functionality to the metadata. This resource aims to integrate the traditional scientific publication directly into existing biological databases, thus obviating the need for a user to search in multiple locations for information relating to a specific item of interest, for example published experimental results associated with a particular biological database entry. As an example of a possible use of BioLit, we also present an instance of the Protein Data Bank fully integrated with BioLit data. We expect that the community of life scientists in general will be the primary end-users of the web-based viewer, while biocurators will make use of the metadata-containing XML files and the BioLit database of article data. BioLit is available at
<ext-link ext-link-type="uri" xlink:href="http://biolit.ucsd.edu">http://biolit.ucsd.edu</ext-link>
.</p>
</div>
</front>
<back>
<div1 type="bibliography">
<listBibl>
<biblStruct>
<analytic>
<author>
<name sortKey="Brown, Po" uniqKey="Brown P">PO Brown</name>
</author>
<author>
<name sortKey="Eisen, Mb" uniqKey="Eisen M">MB Eisen</name>
</author>
<author>
<name sortKey="Varmus, He" uniqKey="Varmus H">HE Varmus</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Wheeler, Dl" uniqKey="Wheeler D">DL Wheeler</name>
</author>
<author>
<name sortKey="Barrett, T" uniqKey="Barrett T">T Barrett</name>
</author>
<author>
<name sortKey="Benson, Da" uniqKey="Benson D">DA Benson</name>
</author>
<author>
<name sortKey="Bryant, Sh" uniqKey="Bryant S">SH Bryant</name>
</author>
<author>
<name sortKey="Canese, K" uniqKey="Canese K">K Canese</name>
</author>
<author>
<name sortKey="Chetvernin, V" uniqKey="Chetvernin V">V Chetvernin</name>
</author>
<author>
<name sortKey="Church, Dm" uniqKey="Church D">DM Church</name>
</author>
<author>
<name sortKey="Dicuccio, M" uniqKey="Dicuccio M">M Dicuccio</name>
</author>
<author>
<name sortKey="Edgar, R" uniqKey="Edgar R">R Edgar</name>
</author>
<author>
<name sortKey="Federhen, S" uniqKey="Federhen S">S Federhen</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Douglas, Sm" uniqKey="Douglas S">SM Douglas</name>
</author>
<author>
<name sortKey="Montelione, Gt" uniqKey="Montelione G">GT Montelione</name>
</author>
<author>
<name sortKey="Gerstein, M" uniqKey="Gerstein M">M Gerstein</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Fink, L" uniqKey="Fink L">L Fink</name>
</author>
<author>
<name sortKey="Bourne, P" uniqKey="Bourne P">P Bourne</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Bourne, P" uniqKey="Bourne P">P Bourne</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Maccallum, Cj" uniqKey="Maccallum C">CJ MacCallum</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Seringhaus, Mr" uniqKey="Seringhaus M">MR Seringhaus</name>
</author>
<author>
<name sortKey="Gerstein, Mb" uniqKey="Gerstein M">MB Gerstein</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Eysenbach, G" uniqKey="Eysenbach G">G Eysenbach</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Eysenbach, G" uniqKey="Eysenbach G">G Eysenbach</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Watson, R" uniqKey="Watson R">R Watson</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Kouranov, A" uniqKey="Kouranov A">A Kouranov</name>
</author>
<author>
<name sortKey="Xie, L" uniqKey="Xie L">L Xie</name>
</author>
<author>
<name sortKey="De La Cruz, J" uniqKey="De La Cruz J">J de la Cruz</name>
</author>
<author>
<name sortKey="Chen, L" uniqKey="Chen L">L Chen</name>
</author>
<author>
<name sortKey="Westbrook, J" uniqKey="Westbrook J">J Westbrook</name>
</author>
<author>
<name sortKey="Bourne, Pe" uniqKey="Bourne P">PE Bourne</name>
</author>
<author>
<name sortKey="Berman, Hm" uniqKey="Berman H">HM Berman</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Ashburner, M" uniqKey="Ashburner M">M Ashburner</name>
</author>
<author>
<name sortKey="Ball, Ca" uniqKey="Ball C">CA Ball</name>
</author>
<author>
<name sortKey="Blake, Ja" uniqKey="Blake J">JA Blake</name>
</author>
<author>
<name sortKey="Botstein, D" uniqKey="Botstein D">D Botstein</name>
</author>
<author>
<name sortKey="Butler, H" uniqKey="Butler H">H Butler</name>
</author>
<author>
<name sortKey="Cherry, Jm" uniqKey="Cherry J">JM Cherry</name>
</author>
<author>
<name sortKey="Davis, Ap" uniqKey="Davis A">AP Davis</name>
</author>
<author>
<name sortKey="Dolinski, K" uniqKey="Dolinski K">K Dolinski</name>
</author>
<author>
<name sortKey="Dwight, Ss" uniqKey="Dwight S">SS Dwight</name>
</author>
<author>
<name sortKey="Eppig, Jt" uniqKey="Eppig J">JT Eppig</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Hirschman, L" uniqKey="Hirschman L">L Hirschman</name>
</author>
<author>
<name sortKey="Yeh, A" uniqKey="Yeh A">A Yeh</name>
</author>
<author>
<name sortKey="Blaschke, C" uniqKey="Blaschke C">C Blaschke</name>
</author>
<author>
<name sortKey="Valencia, A" uniqKey="Valencia A">A Valencia</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Doms, A" uniqKey="Doms A">A Doms</name>
</author>
<author>
<name sortKey="Schroeder, M" uniqKey="Schroeder M">M Schroeder</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Vanteru, Bc" uniqKey="Vanteru B">BC Vanteru</name>
</author>
<author>
<name sortKey="Shaik, Js" uniqKey="Shaik J">JS Shaik</name>
</author>
<author>
<name sortKey="Yeasin, M" uniqKey="Yeasin M">M Yeasin</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Chen, D" uniqKey="Chen D">D Chen</name>
</author>
<author>
<name sortKey="Muller, Hm" uniqKey="Muller H">HM Muller</name>
</author>
<author>
<name sortKey="Sternberg, Pw" uniqKey="Sternberg P">PW Sternberg</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Muller, Hm" uniqKey="Muller H">HM Muller</name>
</author>
<author>
<name sortKey="Kenny, Ee" uniqKey="Kenny E">EE Kenny</name>
</author>
<author>
<name sortKey="Sternberg, Pw" uniqKey="Sternberg P">PW Sternberg</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Rubin, Dl" uniqKey="Rubin D">DL Rubin</name>
</author>
<author>
<name sortKey="Lewis, Se" uniqKey="Lewis S">SE Lewis</name>
</author>
<author>
<name sortKey="Mungall, Cj" uniqKey="Mungall C">CJ Mungall</name>
</author>
<author>
<name sortKey="Misra, S" uniqKey="Misra S">S Misra</name>
</author>
<author>
<name sortKey="Westerfield, M" uniqKey="Westerfield M">M Westerfield</name>
</author>
<author>
<name sortKey="Ashburner, M" uniqKey="Ashburner M">M Ashburner</name>
</author>
<author>
<name sortKey="Sim, I" uniqKey="Sim I">I Sim</name>
</author>
<author>
<name sortKey="Chute, Cg" uniqKey="Chute C">CG Chute</name>
</author>
<author>
<name sortKey="Solbrig, H" uniqKey="Solbrig H">H Solbrig</name>
</author>
<author>
<name sortKey="Storey, Ma" uniqKey="Storey M">MA Storey</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Yesilada, Y" uniqKey="Yesilada Y">Y Yesilada</name>
</author>
<author>
<name sortKey="Bechhofer, S" uniqKey="Bechhofer S">S Bechhofer</name>
</author>
<author>
<name sortKey="Horan, B" uniqKey="Horan B">B Horan</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Smith, B" uniqKey="Smith B">B Smith</name>
</author>
<author>
<name sortKey="Ashburner, M" uniqKey="Ashburner M">M Ashburner</name>
</author>
<author>
<name sortKey="Rosse, C" uniqKey="Rosse C">C Rosse</name>
</author>
<author>
<name sortKey="Bard, J" uniqKey="Bard J">J Bard</name>
</author>
<author>
<name sortKey="Bug, W" uniqKey="Bug W">W Bug</name>
</author>
<author>
<name sortKey="Ceusters, W" uniqKey="Ceusters W">W Ceusters</name>
</author>
<author>
<name sortKey="Goldberg, Lj" uniqKey="Goldberg L">LJ Goldberg</name>
</author>
<author>
<name sortKey="Eilbeck, K" uniqKey="Eilbeck K">K Eilbeck</name>
</author>
<author>
<name sortKey="Ireland, A" uniqKey="Ireland A">A Ireland</name>
</author>
<author>
<name sortKey="Mungall, Cj" uniqKey="Mungall C">CJ Mungall</name>
</author>
</analytic>
</biblStruct>
</listBibl>
</div1>
</back>
</TEI>
<pmc article-type="research-article">
<pmc-dir>properties open_access</pmc-dir>
<front>
<journal-meta>
<journal-id journal-id-type="nlm-ta">Nucleic Acids Res</journal-id>
<journal-id journal-id-type="iso-abbrev">Nucleic Acids Res</journal-id>
<journal-id journal-id-type="publisher-id">nar</journal-id>
<journal-id journal-id-type="hwp">nar</journal-id>
<journal-title-group>
<journal-title>Nucleic Acids Research</journal-title>
</journal-title-group>
<issn pub-type="ppub">0305-1048</issn>
<issn pub-type="epub">1362-4962</issn>
<publisher>
<publisher-name>Oxford University Press</publisher-name>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="pmid">18515836</article-id>
<article-id pub-id-type="pmc">2447735</article-id>
<article-id pub-id-type="doi">10.1093/nar/gkn317</article-id>
<article-id pub-id-type="publisher-id">gkn317</article-id>
<article-categories>
<subj-group subj-group-type="heading">
<subject>Articles</subject>
</subj-group>
</article-categories>
<title-group>
<article-title>BioLit: integrating biological literature with databases</article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author">
<name>
<surname>Fink</surname>
<given-names>J. Lynn</given-names>
</name>
<xref ref-type="corresp" rid="COR1">*</xref>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Kushch</surname>
<given-names>Sergey</given-names>
</name>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Williams</surname>
<given-names>Parker R.</given-names>
</name>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Bourne</surname>
<given-names>Philip E.</given-names>
</name>
</contrib>
</contrib-group>
<aff>Skaggs School of Pharmacy and Pharmaceutical Sciences, University of California, San Diego, CA, 92093-0444, USA</aff>
<author-notes>
<corresp id="COR1">*To whom correspondence should be addressed.
<phone>+1 858 822 1897</phone>
<fax>+ 1 858 822 3610</fax>
<email>jlfink@ucsd.edu</email>
</corresp>
</author-notes>
<pub-date pub-type="ppub">
<day>1</day>
<month>7</month>
<year>2008</year>
</pub-date>
<pub-date pub-type="epub">
<day>31</day>
<month>5</month>
<year>2008</year>
</pub-date>
<pub-date pub-type="pmc-release">
<day>31</day>
<month>5</month>
<year>2008</year>
</pub-date>
<pmc-comment> PMC Release delay is 0 months and 0 days and was based on the . </pmc-comment>
<volume>36</volume>
<issue>Web Server issue</issue>
<fpage>W385</fpage>
<lpage>W389</lpage>
<history>
<date date-type="received">
<day>30</day>
<month>1</month>
<year>2008</year>
</date>
<date date-type="rev-recd">
<day>22</day>
<month>4</month>
<year>2008</year>
</date>
<date date-type="accepted">
<day>7</day>
<month>5</month>
<year>2008</year>
</date>
</history>
<permissions>
<copyright-statement>© 2008 The Author(s)</copyright-statement>
<copyright-year>2008</copyright-year>
<license license-type="creative-commons" xlink:href="http://creativecommons.org/licenses/by-nc/2.0/uk/">
<license-p>
<pmc-comment>CREATIVE COMMONS</pmc-comment>
This is an Open Access article distributed under the terms of the Creative Commons Attribution Non-Commercial License (
<ext-link ext-link-type="uri" xlink:href="http://creativecommons.org/licenses/by-nc/2.0/uk/">http://creativecommons.org/licenses/by-nc/2.0/uk/</ext-link>
) which permits unrestricted non-commercial use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
</license>
</permissions>
<abstract>
<p>BioLit is a web server which provides metadata describing the semantic content of all open access, peer-reviewed articles which describe research from the major life sciences literature archive, PubMed Central. Specifically, these metadata include database identifiers and ontology terms found within the full text of the article. BioLit delivers these metadata in the form of XML-based article files and as a custom web-based article viewer that provides context-specific functionality to the metadata. This resource aims to integrate the traditional scientific publication directly into existing biological databases, thus obviating the need for a user to search in multiple locations for information relating to a specific item of interest, for example published experimental results associated with a particular biological database entry. As an example of a possible use of BioLit, we also present an instance of the Protein Data Bank fully integrated with BioLit data. We expect that the community of life scientists in general will be the primary end-users of the web-based viewer, while biocurators will make use of the metadata-containing XML files and the BioLit database of article data. BioLit is available at
<ext-link ext-link-type="uri" xlink:href="http://biolit.ucsd.edu">http://biolit.ucsd.edu</ext-link>
.</p>
</abstract>
</article-meta>
</front>
<body>
<sec>
<title>INTRODUCTION</title>
<p>Prior to the advent and subsequent popularity of the internet, biological databases and scientific publications were necessarily separate entities. However, now that scientists rely on cyberinfrastructure in the course of their daily research, it is startling that databases and publications are still so distinct from each other. While databases have matured and grown in complexity in the digital age, publications have fared poorly; the traditional concept of an article as a static, independent unit of information persists, albeit in an electronic version. There are myriad ways in which the content of an electronic version of an article can be used in a computational manner and the technology and infrastructure to make this happen already exists; this is demonstrated by, among other things, the existence of biological databases and related data mining tools. Indeed, one hallmark of a successful biological database is integration via data mining with other related databases or resources. Yet integration with literature, which is unquestionably the primary medium through which scientists communicate their research, is conspicuously lacking.</p>
<p>Significant progress in taking advantage of article content is finally being made, perhaps most notably as a result of the open access literature movement pioneered by, among others, the Public Library of Science (PLoS) (
<xref ref-type="bibr" rid="B1">1</xref>
). Articles that are published under an open access license are available for download
<italic>in toto</italic>
immediately upon publication and can be distributed freely providing that the original citation is maintained. The deposition of open access life sciences articles has been centralized with the creation of PubMed Central (
<xref ref-type="bibr" rid="B2">2</xref>
) and it is especially important to note that PubMed Central stores many of these articles in a standardized and machine-readable format, which conforms to the National Library of Medicine (NLM) DTD (
<ext-link ext-link-type="uri" xlink:href="http://dtd.nlm.nih.gov/">http://dtd.nlm.nih.gov/</ext-link>
). All PubMed Central articles deposited as a result of this movement are thus freely available as XML files, which contain the full-text of the article and some semantic mark-up of the content.</p>
<p>Though a major advantage to both authors and readers, a large segment of the life sciences community remains unaware of the opportunities that are now available due to the existence of PubMed Central as a digital repository, or even of the existence of open access literature altogether. Hopefully, this will change with the recent NIH directive, which mandates the deposition of all findings of NIH-funded research in PubMed Central (
<ext-link ext-link-type="uri" xlink:href="http://publicaccess.nih.gov/">http://publicaccess.nih.gov/</ext-link>
) and with novel open access-driven applications such as PubNet (
<xref ref-type="bibr" rid="B3">3</xref>
) and SciVee (
<xref ref-type="bibr" rid="B4">4</xref>
). Admittedly, challenges do present themselves when considering the use of open access literature beyond that of a reader or distributor—they have been described elsewhere (
<xref ref-type="bibr" rid="B4 B5 B6 B7">4–7</xref>
)—but opportunities abound and the tenor of current scientific policy and inquiry suggests that the open access corpus will continue to grow significantly (
<xref ref-type="bibr" rid="B8 B9 B10">8–10</xref>
).</p>
<p>BioLit aims to take advantage of the opportunities offered by open access literature by making it possible to include full text or excerpts of these articles directly within existing biological databases and to add newly generated metadata to the articles in order to increase their informative value, tasks which are both made possible by having free access to the full text of the article. These tasks are accomplished by mining the full article text for terms of interest, indexing the terms found, and then including these terms in both machine-readable and human-readable forms that are an enhancement of the original article XML file. The machine-readable form can be incorporated directly into a database or resource. We have prototyped this particular aspect of the effort using a clone of the RCSB Protein Data Bank (PDB) (
<xref ref-type="bibr" rid="B11">11</xref>
), a database of macromolecular structures, and have consequently focused on finding PDB identifiers and Gene Ontology (
<xref ref-type="bibr" rid="B12">12</xref>
) terms as these are both major resources in the structural biology community and the life sciences community as a whole.</p>
<p>Several groups have made significant contributions in applying ontologies to both open- and closed-access biomedical literature. For example, the BioCreAtIvE initiative has spawned a number of tools with the aim of annotating genes and proteins in articles using ontologies and other vocabularies (
<xref ref-type="bibr" rid="B13">13</xref>
). GoPubMed (
<xref ref-type="bibr" rid="B14">14</xref>
) and the more recent SEGOPubmed (
<xref ref-type="bibr" rid="B15">15</xref>
) both aim to add Gene Ontology-based semantic data to PubMed abstracts in order to improve literature searches. The Textpresso team has also focused on improving the classification and searchability of articles by inferring semantic relationships in articles using customized ontologies (
<xref ref-type="bibr" rid="B16">16</xref>
,
<xref ref-type="bibr" rid="B17">17</xref>
). Unlike GoPubMed and SEGOPubmed, they use the full text of the article. Another excellent resource is the National Center for Biomedical Ontology (NCBO) whose overarching aim is to render biomedical information into machine-readable data (
<xref ref-type="bibr" rid="B18">18</xref>
). One of their major contributions is the unification and integration of biomedical ontologies into a single resource, the OBO Foundry, which makes projects such as these and BioLit feasible. The NCBO consortium is also developing a number of web-based tools, in order to make the machine-readable biomedical information available and useful to the community. Finally, The Conceptual Open Hypermedia Service (COHSE), perhaps the most broadly applicable semantic mark-up project, runs as a portlet and adds hyperlinks to existing web pages by allowing a user to select an ontology with terms that can be matched to the page to create links to other pages (
<xref ref-type="bibr" rid="B19">19</xref>
).</p>
<p>Several of the aforementioned tools allow manual curation of the marked-up result in order to increase the accuracy of the mark-up, and hence, the literature search results. This is the ideal approach towards semantic mark-up since the author, or at least an expert human, is providing input. However, the uptake of such an approach in the community has been fairly unsuccessful owing to time limitations on the part of the putative curators and, presumably, lack of demonstrable value to justify the time and effort.</p>
<p>BioLit shares many attributes with these projects but is unique in that it offers a searchable web database of the
<italic>full text</italic>
of
<italic>all PubMed Central research articles</italic>
with automated mark-up from
<italic>multiple</italic>
biomedical ontologies and identifiers from
<italic>multiple</italic>
biological databases.
<italic>No downloading</italic>
of software is required and all searchable terms belong to established biomedical resources. The focus of this resource is specific to life sciences literature but broad within that realm. Machine-readable files are freely available and distributable via automated means.</p>
</sec>
<sec>
<title>BIOLIT DATABASE</title>
<p>The database supporting the BioLit web server contains data from a subset of the PubMed Central holdings. Article archives, including full-text XML files and figures, were retrieved via the PubMed Central FTP site (ftp://ftp.ncbi.nlm.nih.gov/pub/pmc). The articles were first filtered to remove articles that were not labeled as ‘review-article’, ‘case-report’, ‘research-article’, ‘brief-report’, ‘retraction’ and ‘article-commentary’, and documents which contained only scanned content since these are generally advertisements. The remaining articles were stored in a local MySQL database both in the original and parsed formats. When possible, data included in the MEDLINE record for an article were retrieved from PubMed using NCBI's E-Utilities (
<xref ref-type="bibr" rid="B2">2</xref>
). The full text of each article was then parsed to find PDB IDs and Gene ontology terms. These metadata were also stored in the local database. Currently, 51 667 articles exist in the database. The database is updated weekly.</p>
</sec>
<sec>
<title>BIOLIT ARTICLE VIEWER</title>
<p>BioLit uses a customized viewer for the articles in order to display the original text inline with the added metadata. This viewer uses a custom XML stylesheet based on the NLM DTD. The full text of the paper can be displayed in a tabbed format or the traditional linear article format and the metadata are highlighted with color and a menu of options when the user clicks on a term. In the case of PDB IDs, an image of the 3D structure identified by the PDB ID is displayed along with links to the macromolecular sequence, the PDB record and other related features. Clicking on an ontology term shows a definition of the term and related links. We also generate statistics describing ontology term usage across all articles and these terms can be used for searching or finding related articles.
<xref ref-type="fig" rid="F1">Figure 1</xref>
shows an excerpt of BioLit-enhanced text.
<fig id="F1" position="float">
<label>Figure 1.</label>
<caption>
<p>A screenshot of the BioLit article viewer. This customized viewer not only displays the full text of an article as it was originally published but also displays integrated metadata from the BioLit database. PDB IDs can be seen highlighted in yellow and Gene Ontology terms are highlighted in lavender. Clicking on a highlighted terms brings up information, a list of options or links associated with each term. Article shown is in
<italic>PLoS Comput. Biol</italic>
., 2006,
<bold>2</bold>
, e90.</p>
</caption>
<graphic xlink:href="gkn317f1"></graphic>
</fig>
</p>
<p>In order to use the BioLit article viewer, the user enters a search term on the BioLit homepage. This term can be an author name, title, keyword, etc. The web server then returns a list of matching articles; clicking on an article invokes the customized viewer. Alternatively, a user could bypass the web-based viewer and retrieve BioLit XML files using a script by appending a PubMed Central ID (PMCID), PubMed ID (PMID) or article digital object identifier (DOI) to the following URL template:
<ext-link ext-link-type="uri" xlink:href="http://biolit.ucsd.edu/biolit/getbiolitxml?SOURCE=ID">http://biolit.ucsd.edu/biolit/getbiolitxml?SOURCE=ID</ext-link>
where, SOURCE is ‘pmcid’, ‘pmid’ or ‘doi’ and ID is the corresponding identifier for that resource.</p>
<p>The machine-readable version of an article is available as an XML file through the viewer and via a POST HTTP query. The XML markup enrichment performed by BioLit consists of inserting metadata into the original XML file. The <
<italic>biolit</italic>
> tag appears as the top-level child node of <
<italic>article</italic>
>, a tag in the NLM namespace. The additional metadata includes markup revision data (<
<italic>markup-version</italic>
> and <
<italic>markup-date</italic>
>) as well as derived identification content <
<italic>ident</italic>
>, which specifies the DOI and PubMed Central ID of the article. Throughout the text of the article, <
<italic>biolit-term</italic>
> marks semantic content that has been discovered during the data mining process where attributes type, id identify the content. The complete BioLit XML specification can be found at
<ext-link ext-link-type="uri" xlink:href="http://biolit.ucsd.edu">http://biolit.ucsd.edu</ext-link>
.</p>
</sec>
<sec>
<title>BIOLIT-INTEGRATED PROTEIN DATA BANK CLONE</title>
<p>One example of how the BioLit data might be used in an existing biological web resource is illustrated by the BioLit PDB clone, a stand-alone clone of the Protein Data Bank which runs independently from the PDB and has direct access to the BioLit database (
<ext-link ext-link-type="uri" xlink:href="http://biolit.ucsd.edu/pdb">http://biolit.ucsd.edu/pdb</ext-link>
). The clone maintains much of the original functionality, including access to the latest release of the PDB database, while providing access to features unique to BioLit. The PDB structure explorer page now shows related articles as identified by BioLit. A simple browser has been integrated to display data excerpts from the article as well as structure IDs and ontology terms identified in the article. Thus, when an entry in the PDB is displayed, all articles in the BioLit database that mention that entry are included as citations in the PDB record. In contrast, the PDB currently only displays the citation associated with the entry in which the solved structure is reported.
<xref ref-type="fig" rid="F2">Figure 2</xref>
shows an entry from the BioLit PDB clone which has citations in the BioLit database. Because we find all mentions of PDB IDs in an article, we can also report which PDB IDs are mentioned in the same article. This can direct the user to other PDB entries which might be of interest. The user can also access the BioLit article viewer via the PDB record.
<fig id="F2" position="float">
<label>Figure 2.</label>
<caption>
<p>Entry from the BioLit PDB clone that has citations inthe BioLit database.</p>
</caption>
<graphic xlink:href="gkn317f2"></graphic>
</fig>
</p>
</sec>
<sec>
<title>ONTOLOGY PARSING</title>
<p>All ontology terms are parsed from an OBO file (
<ext-link ext-link-type="uri" xlink:href="http://obofoundry.org/ro/ro.obo">http://obofoundry.org/ro/ro.obo</ext-link>
) and loaded into a tree structure such that each letter in any given term links to the letter succeeding it. The full-text of the XML article is then read beginning with the abstract and ending with the end of the article body. The parser jumps to the beginning of every word in the article text, reading character by character. This structure is advantageous as it allows a search for all words in a single read of the document and it allows the reading to stop as soon as a word fails to have a character in the tree. The longest parse time that we have observed of parsing an article through a large ontology, such as the Gene Ontology, are about 30 s, although most articles are processed in under 1 s.</p>
</sec>
<sec>
<title>HARDWARE AND SOFTWARE DESIGN</title>
<p>The BioLit web server is staged from a single Dell PowerEdge SC145, which is hosted at the Skaggs School of Pharmacy and Pharmaceutical Sciences at UCSD. The machine is a dual-Opteron 2216 (Dual Core at 2.4 GHz) with 8 GB of RAM and 750 GB of RAIDed storage, which runs RedHat Enterprise Linux 5. At the present time, this machine is responsible for data mining, markup, front-end functionality, as well as serving a modified clone of the PDB web application.</p>
<p>In an effort to maximize performance and scalability of the software, the three main units of the project operate as discrete applications. The data mining portion is handled by a suite of in-house parsing scripts. The BioLit markup process is performed by a separate script. The front-end searching and visualization functionality is delivered by a J2EE web application running on Apache Tomcat 6. Much of the web-based, event-driven functionality is structured upon the YUI API. The dynamic data storage and sharing is handled by MySQL, while large static data are locally archived.</p>
</sec>
<sec>
<title>FUTURE DIRECTIONS</title>
<p>The value of the BioLit web server resides in the amount of metadata it can provide and in the ease in which those metadata can be retrieved. To increase the value of BioLit, we plan to parse the articles through all ontologies in the Open Biomedical Ontologies Foundry (
<xref ref-type="bibr" rid="B20">20</xref>
) and allow the user to specify the inclusion or exclusion of metadata by ontology. We also plan to expand our search for database identifiers to other major biological databases. In order to make these data more accessible to biocurators and text miners, we are implementing web services-based protocols that allow fetching of articles or metadata by source (database, ontology) and by term or ID.</p>
<p>We recognize that we are not experts in natural language processing and that the markup we provide is not truly semantic in nature (e.g. we do not infer relationships between terms and identifiers). We are open to collaboration in order to include this information in future versions.</p>
</sec>
<sec sec-type="conclusions">
<title>CONCLUSIONS</title>
<p>We hope that the BioLit web server will establish an informative, yet transparent, connection between the data and the article describing the data and that effective use of this resource will provide new perspectives on both traditional literature and biological databases. We expect that literature will simply become another interface to biological data in a database and the database will recall appropriate literature—not in abstract or complete paper size chunks, but knowledge objects that annotate the data being examined. As authors become more aware of the possibilities offered by open access literature and by tools that can be used to standardize and highlight semantic content, we hope this awareness will manifest itself in the writing process and contribute to the accessibility of literature-based knowledge.</p>
</sec>
</body>
<back>
<ack>
<title>ACKNOWLEDGEMENTS</title>
<p>Special thanks go to Tim Beck, Bojan Beran, D. Jeff Milton, and Joe Mulvaney for assistance with system administration and installation of the PDB clone. Project funding was provided by National Science Foundation Award # 0544575. Funding to pay the Open Access publication charges for this article was provided by National Science Foundation Award #0544575.</p>
<p>
<italic>Conflict of interest statement</italic>
. None declared.</p>
</ack>
<ref-list>
<title>REFERENCES</title>
<ref id="B1">
<label>1</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Brown</surname>
<given-names>PO</given-names>
</name>
<name>
<surname>Eisen</surname>
<given-names>MB</given-names>
</name>
<name>
<surname>Varmus</surname>
<given-names>HE</given-names>
</name>
</person-group>
<article-title>Why PLoS became a publisher</article-title>
<source>PLoS Biol.</source>
<year>2003</year>
<volume>1</volume>
<fpage>E36</fpage>
<pub-id pub-id-type="pmid">14551926</pub-id>
</element-citation>
</ref>
<ref id="B2">
<label>2</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Wheeler</surname>
<given-names>DL</given-names>
</name>
<name>
<surname>Barrett</surname>
<given-names>T</given-names>
</name>
<name>
<surname>Benson</surname>
<given-names>DA</given-names>
</name>
<name>
<surname>Bryant</surname>
<given-names>SH</given-names>
</name>
<name>
<surname>Canese</surname>
<given-names>K</given-names>
</name>
<name>
<surname>Chetvernin</surname>
<given-names>V</given-names>
</name>
<name>
<surname>Church</surname>
<given-names>DM</given-names>
</name>
<name>
<surname>Dicuccio</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Edgar</surname>
<given-names>R</given-names>
</name>
<name>
<surname>Federhen</surname>
<given-names>S</given-names>
</name>
<etal></etal>
</person-group>
<article-title>Database resources of the National Center for Biotechnology Information</article-title>
<source>Nucleic acids research</source>
<year>2008</year>
<volume>36</volume>
<fpage>D13</fpage>
<lpage>D21</lpage>
<pub-id pub-id-type="pmid">18045790</pub-id>
</element-citation>
</ref>
<ref id="B3">
<label>3</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Douglas</surname>
<given-names>SM</given-names>
</name>
<name>
<surname>Montelione</surname>
<given-names>GT</given-names>
</name>
<name>
<surname>Gerstein</surname>
<given-names>M</given-names>
</name>
</person-group>
<article-title>PubNet: a flexible system for visualizing literature derived networks</article-title>
<source>Genome Biol.</source>
<year>2005</year>
<volume>6</volume>
<fpage>R80</fpage>
<pub-id pub-id-type="pmid">16168087</pub-id>
</element-citation>
</ref>
<ref id="B4">
<label>4</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Fink</surname>
<given-names>L</given-names>
</name>
<name>
<surname>Bourne</surname>
<given-names>P</given-names>
</name>
</person-group>
<article-title>Reinventing scholarly communication for the electronic age</article-title>
<source>CTWatch Quarterly</source>
<year>2007</year>
<volume>3</volume>
<fpage>26</fpage>
<lpage>31</lpage>
</element-citation>
</ref>
<ref id="B5">
<label>5</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Bourne</surname>
<given-names>P</given-names>
</name>
</person-group>
<article-title>Will a biological database be different from a biological journal?</article-title>
<source>PLoS Comput. Biol.</source>
<year>2005</year>
<volume>1</volume>
<fpage>179</fpage>
<lpage>181</lpage>
<pub-id pub-id-type="pmid">16158097</pub-id>
</element-citation>
</ref>
<ref id="B6">
<label>6</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>MacCallum</surname>
<given-names>CJ</given-names>
</name>
</person-group>
<article-title>When is open access not open access?</article-title>
<source>PLoS Biol.</source>
<year>2007</year>
<volume>5</volume>
<fpage>2095</fpage>
<lpage>2097</lpage>
<pub-id pub-id-type="pmid">17941723</pub-id>
</element-citation>
</ref>
<ref id="B7">
<label>7</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Seringhaus</surname>
<given-names>MR</given-names>
</name>
<name>
<surname>Gerstein</surname>
<given-names>MB</given-names>
</name>
</person-group>
<article-title>Publishing perishing? Towards tomorrow's information architecture</article-title>
<source>BMC Bioinform.</source>
<year>2007</year>
<volume>8</volume>
<fpage>17</fpage>
</element-citation>
</ref>
<ref id="B8">
<label>8</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Eysenbach</surname>
<given-names>G</given-names>
</name>
</person-group>
<article-title>The open access advantage</article-title>
<source>J. Med. Int. Res.</source>
<year>2006</year>
<volume>8</volume>
<fpage>e8</fpage>
</element-citation>
</ref>
<ref id="B9">
<label>9</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Eysenbach</surname>
<given-names>G</given-names>
</name>
</person-group>
<article-title>Citation advantage of open access articles</article-title>
<source>PLoS Biol.</source>
<year>2006</year>
<volume>4</volume>
<fpage>e157</fpage>
<pub-id pub-id-type="pmid">16683865</pub-id>
</element-citation>
</ref>
<ref id="B10">
<label>10</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Watson</surname>
<given-names>R</given-names>
</name>
</person-group>
<article-title>EC to promote open access publishing</article-title>
<source>Br. Med. J.</source>
<year>2007</year>
<volume>334</volume>
<fpage>389</fpage>
<pub-id pub-id-type="pmid">17322242</pub-id>
</element-citation>
</ref>
<ref id="B11">
<label>11</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Kouranov</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Xie</surname>
<given-names>L</given-names>
</name>
<name>
<surname>de la Cruz</surname>
<given-names>J</given-names>
</name>
<name>
<surname>Chen</surname>
<given-names>L</given-names>
</name>
<name>
<surname>Westbrook</surname>
<given-names>J</given-names>
</name>
<name>
<surname>Bourne</surname>
<given-names>PE</given-names>
</name>
<name>
<surname>Berman</surname>
<given-names>HM</given-names>
</name>
</person-group>
<article-title>The RCSB PDB information portal for structural genomics</article-title>
<source>Nucleic Acids Res.</source>
<year>2006</year>
<volume>34</volume>
<fpage>D302</fpage>
<lpage>D305</lpage>
<pub-id pub-id-type="pmid">16381872</pub-id>
</element-citation>
</ref>
<ref id="B12">
<label>12</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Ashburner</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Ball</surname>
<given-names>CA</given-names>
</name>
<name>
<surname>Blake</surname>
<given-names>JA</given-names>
</name>
<name>
<surname>Botstein</surname>
<given-names>D</given-names>
</name>
<name>
<surname>Butler</surname>
<given-names>H</given-names>
</name>
<name>
<surname>Cherry</surname>
<given-names>JM</given-names>
</name>
<name>
<surname>Davis</surname>
<given-names>AP</given-names>
</name>
<name>
<surname>Dolinski</surname>
<given-names>K</given-names>
</name>
<name>
<surname>Dwight</surname>
<given-names>SS</given-names>
</name>
<name>
<surname>Eppig</surname>
<given-names>JT</given-names>
</name>
<etal></etal>
</person-group>
<article-title>Gene ontology: tool for the unification of biology. The Gene Ontology Consortium</article-title>
<source>Nat. Genet.</source>
<year>2000</year>
<volume>25</volume>
<fpage>25</fpage>
<lpage>29</lpage>
<pub-id pub-id-type="pmid">10802651</pub-id>
</element-citation>
</ref>
<ref id="B13">
<label>13</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Hirschman</surname>
<given-names>L</given-names>
</name>
<name>
<surname>Yeh</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Blaschke</surname>
<given-names>C</given-names>
</name>
<name>
<surname>Valencia</surname>
<given-names>A</given-names>
</name>
</person-group>
<article-title>Overview of BioCreAtIvE: critical assessment of information extraction for biology</article-title>
<source>BMC Bioinform.</source>
<year>2005</year>
<volume>6</volume>
<issue>Suppl. 1</issue>
<fpage>S1</fpage>
</element-citation>
</ref>
<ref id="B14">
<label>14</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Doms</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Schroeder</surname>
<given-names>M</given-names>
</name>
</person-group>
<article-title>GoPubMed: exploring PubMed with the Gene Ontology</article-title>
<source>Nucleic Acids Res.</source>
<year>2005</year>
<volume>33</volume>
<fpage>W783</fpage>
<lpage>W786</lpage>
<pub-id pub-id-type="pmid">15980585</pub-id>
</element-citation>
</ref>
<ref id="B15">
<label>15</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Vanteru</surname>
<given-names>BC</given-names>
</name>
<name>
<surname>Shaik</surname>
<given-names>JS</given-names>
</name>
<name>
<surname>Yeasin</surname>
<given-names>M</given-names>
</name>
</person-group>
<article-title>Semantically linking and browsing PubMed abstracts with gene ontology</article-title>
<source>BMC Genomics</source>
<year>2008</year>
<volume>9</volume>
<issue>Suppl. 1</issue>
<fpage>S10</fpage>
<pub-id pub-id-type="pmid">18366599</pub-id>
</element-citation>
</ref>
<ref id="B16">
<label>16</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Chen</surname>
<given-names>D</given-names>
</name>
<name>
<surname>Muller</surname>
<given-names>HM</given-names>
</name>
<name>
<surname>Sternberg</surname>
<given-names>PW</given-names>
</name>
</person-group>
<article-title>Automatic document classification of biological literature</article-title>
<source>BMC Bioinform.</source>
<year>2006</year>
<volume>7</volume>
<fpage>370</fpage>
</element-citation>
</ref>
<ref id="B17">
<label>17</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Muller</surname>
<given-names>HM</given-names>
</name>
<name>
<surname>Kenny</surname>
<given-names>EE</given-names>
</name>
<name>
<surname>Sternberg</surname>
<given-names>PW</given-names>
</name>
</person-group>
<article-title>Textpresso: an ontology-based information retrieval and extraction system for biological literature</article-title>
<source>PLoS Biol.</source>
<year>2004</year>
<volume>2</volume>
<fpage>e309</fpage>
<pub-id pub-id-type="pmid">15383839</pub-id>
</element-citation>
</ref>
<ref id="B18">
<label>18</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Rubin</surname>
<given-names>DL</given-names>
</name>
<name>
<surname>Lewis</surname>
<given-names>SE</given-names>
</name>
<name>
<surname>Mungall</surname>
<given-names>CJ</given-names>
</name>
<name>
<surname>Misra</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Westerfield</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Ashburner</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Sim</surname>
<given-names>I</given-names>
</name>
<name>
<surname>Chute</surname>
<given-names>CG</given-names>
</name>
<name>
<surname>Solbrig</surname>
<given-names>H</given-names>
</name>
<name>
<surname>Storey</surname>
<given-names>MA</given-names>
</name>
<etal></etal>
</person-group>
<article-title>National Center for Biomedical Ontology: advancing biomedicine through structured organization of scientific knowledge</article-title>
<source>OMICS</source>
<year>2006</year>
<volume>10</volume>
<fpage>185</fpage>
<lpage>198</lpage>
<pub-id pub-id-type="pmid">16901225</pub-id>
</element-citation>
</ref>
<ref id="B19">
<label>19</label>
<element-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Yesilada</surname>
<given-names>Y</given-names>
</name>
<name>
<surname>Bechhofer</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Horan</surname>
<given-names>B</given-names>
</name>
</person-group>
<article-title>COHSE: dynamic linking of web resources</article-title>
<source>Sun Microsystems TR-2007-167</source>
<year>2007</year>
</element-citation>
</ref>
<ref id="B20">
<label>20</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Smith</surname>
<given-names>B</given-names>
</name>
<name>
<surname>Ashburner</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Rosse</surname>
<given-names>C</given-names>
</name>
<name>
<surname>Bard</surname>
<given-names>J</given-names>
</name>
<name>
<surname>Bug</surname>
<given-names>W</given-names>
</name>
<name>
<surname>Ceusters</surname>
<given-names>W</given-names>
</name>
<name>
<surname>Goldberg</surname>
<given-names>LJ</given-names>
</name>
<name>
<surname>Eilbeck</surname>
<given-names>K</given-names>
</name>
<name>
<surname>Ireland</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Mungall</surname>
<given-names>CJ</given-names>
</name>
<etal></etal>
</person-group>
<article-title>The OBO Foundry: coordinated evolution of ontologies to support biomedical data integration</article-title>
<source>Nat. Biotechnol.</source>
<year>2007</year>
<volume>25</volume>
<fpage>1251</fpage>
<lpage>1255</lpage>
<pub-id pub-id-type="pmid">17989687</pub-id>
</element-citation>
</ref>
</ref-list>
</back>
</pmc>
</record>

Pour manipuler ce document sous Unix (Dilib)

EXPLOR_STEP=$WICRI_ROOT/Ticri/CIDE/explor/CyberinfraV1/Data/Pmc/Corpus
HfdSelect -h $EXPLOR_STEP/biblio.hfd -nk 000574  | SxmlIndent | more

Ou

HfdSelect -h $EXPLOR_AREA/Data/Pmc/Corpus/biblio.hfd -nk 000574  | SxmlIndent | more

Pour mettre un lien sur cette page dans le réseau Wicri

{{Explor lien
   |wiki=    Ticri/CIDE
   |area=    CyberinfraV1
   |flux=    Pmc
   |étape=   Corpus
   |type=    RBID
   |clé=     
   |texte=   
}}

Wicri

This area was generated with Dilib version V0.6.25.
Data generation: Thu Oct 27 09:30:58 2016. Site generation: Sun Mar 10 23:08:40 2024