Skip to content

Commit fb874c9

Browse files
committed
Replace master branch with page content via GitHub
1 parent 0280a4b commit fb874c9

File tree

5 files changed

+864
-0
lines changed

5 files changed

+864
-0
lines changed

index.html

+78
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,78 @@
1+
<!DOCTYPE html>
2+
<html lang="en-us">
3+
<head>
4+
<meta charset="UTF-8">
5+
<title>Mirtop.GitHub.io by miRTop</title>
6+
<meta name="viewport" content="width=device-width, initial-scale=1">
7+
<link rel="stylesheet" type="text/css" href="stylesheets/normalize.css" media="screen">
8+
<link href='https://fonts.googleapis.com/css?family=Open+Sans:400,700' rel='stylesheet' type='text/css'>
9+
<link rel="stylesheet" type="text/css" href="stylesheets/stylesheet.css" media="screen">
10+
<link rel="stylesheet" type="text/css" href="stylesheets/github-light.css" media="screen">
11+
</head>
12+
<body>
13+
<section class="page-header">
14+
<h1 class="project-name">Mirtop.GitHub.io</h1>
15+
<h2 class="project-tagline">project for small RNA standard annotations</h2>
16+
</section>
17+
18+
<section class="main-content">
19+
<h2>
20+
<a id="mirna-transcriptomic-open-project-mirtop" class="anchor" href="#mirna-transcriptomic-open-project-mirtop" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>miRNA-Transcriptomic Open Project (miRTOP)</h2>
21+
22+
<p>The main goal of this project is to create a reflection group on metazoan miRNAs, open to all interested researchers, to identify blockages and develop standards and guidelines to improve miRNA research, resources and communication. This can go through the use of standardized file formats, gene and variants nomenclature guidelines, and advancements in miRNA biology understanding.
23+
The group will eventually also aim at expanding its breadth to the development of novel tools, data resources, and best-practices guidelines to benefit the scientific community by providing high confidence validated research and analysis strategies, regardless the expertise in this field.</p>
24+
25+
<p>The motivation and emergence of this group came from the simultaneous publication of two articles from two independent groups and addressing the question of miRNA diversity, origins, evolution, and annotation:</p>
26+
27+
<ul>
28+
<li>Desvignes, T., Batzel, P., Berezikov, E., Eilbeck, K., Eppig, J. T., McAndrews, M. S., Singer, A., Postlethwait, J. H. (2015). miRNA Nomenclature: A View Incorporating Genetic Origins, Biosynthetic Pathways, and Sequence Variants. Trends in Genetics : TIG, 31(11), 613–626. <a href="http://doi.org/10.1016/j.tig.2015.09.002">http://doi.org/10.1016/j.tig.2015.09.002</a>
29+
</li>
30+
<li>Fromm, B., Billipp, T., Peck, L. E., Johansen, M., Tarver, J. E., King, B. L., Newcomb J., Sempere L. F., Flatmark K., Hovig E., Peterson, K. J. (2015). A Uniform System for the Annotation of Vertebrate microRNA Genes and the Evolution of the Human microRNAome. Annual Review of Genetics. <a href="http://doi.org/10.1146/annurev-genet-120213-092023">http://doi.org/10.1146/annurev-genet-120213-092023</a> (<a href="http://mirgenedb.org">http://mirgenedb.org</a>)</li>
31+
</ul>
32+
33+
<p>In addition, plants miRNA research is facing the same problems. The different origin of plant and metazoan miRNA systems, however, make the creation of a unified “plant &amp; metazoan” pattern hazardous. Nevertheless, tentative standardization on specific aspects is a future goal of the group.</p>
34+
35+
<ul>
36+
<li>Budak, H., Bulut, R., Kantar, M., &amp; Alptekin, B. (2015). MicroRNA nomenclature and the need for a revised naming prescription. Briefings in Functional Genomics, elv026–. <a href="http://doi.org/10.1093/bfgp/elv026">http://doi.org/10.1093/bfgp/elv026</a>
37+
</li>
38+
</ul>
39+
40+
<p>If you work in relation with the miRNA field, and want to take part in this reflection group, please <a href="https://github.com/miRTop/miRTOP.github.io/issues/1">join us</a> and share your ideas in order to create a large community working together to improve the study and analysis of miRNA data.</p>
41+
42+
<p>Current projects:</p>
43+
44+
<ul>
45+
<li><p>Establishment of a unified Nomenclature system:
46+
Two novel miRNA nomenclature systems have been simultaneously proposed by independent teams, in addition to the schemes proposed by previous groups. One focused on evolutionary conservation and clear orthology establishment to provide phylogenetically informative names based on Human annotation (Fromm and Peterson’s group), while the other envisioned a system for sequence variation analysis following nomenclature guidelines in use for coding-genes (Desvignes and Postlethwait group). The aim of this project is thus to establish a convergent framework, incorporating the strengths of each proposed system, to finalize a unified and persistent nomenclature system.</p></li>
47+
<li><p>IsomiRs nomenclature:
48+
IsomiRs have proven to be bona fide variants of miRNA expression and could in some cases be functionally important and having different target sets than the reference miRNA they vary from. Because of functional importance of isomiRs, it appears crucial to be able to refer to a given one in a non-ambiguous way. The aim of this project is thus to formulate a standardized format for isomiR referencing and offer tools to apply them in an easy and general way.</p></li>
49+
</ul>
50+
51+
<p>Future projects and discussions:</p>
52+
53+
<ul>
54+
<li>What is the biological relevance of moRNAs? How to detect and annotate them?</li>
55+
<li>Any other ideas or problems?</li>
56+
</ul>
57+
58+
<p>Citation: zenodo citation link.</p>
59+
60+
<p>Contributors:</p>
61+
62+
<ul>
63+
<li>Lorena Pantano. Harvard TH Chan School of Public Health, Boston, USA</li>
64+
<li>Thomas Desvignes, Institute of Neuroscience, University of Oregon, Eugene, OR, USA</li>
65+
<li>John H. Postlethwait, Institute of Neuroscience, University of Oregon, Eugene, OR, USA</li>
66+
<li>Karen EIlbeck. University of Utah, Biomedical Informatics.</li>
67+
</ul>
68+
69+
<footer class="site-footer">
70+
71+
<span class="site-footer-credits">This page was generated by <a href="https://pages.github.com">GitHub Pages</a> using the <a href="https://github.com/jasonlong/cayman-theme">Cayman theme</a> by <a href="https://twitter.com/jasonlong">Jason Long</a>.</span>
72+
</footer>
73+
74+
</section>
75+
76+
77+
</body>
78+
</html>

params.json

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
{"name":"Mirtop.GitHub.io","tagline":"project for small RNA standard annotations","body":"## miRNA-Transcriptomic Open Project (miRTOP) \r\n\r\nThe main goal of this project is to create a reflection group on metazoan miRNAs, open to all interested researchers, to identify blockages and develop standards and guidelines to improve miRNA research, resources and communication. This can go through the use of standardized file formats, gene and variants nomenclature guidelines, and advancements in miRNA biology understanding. \r\nThe group will eventually also aim at expanding its breadth to the development of novel tools, data resources, and best-practices guidelines to benefit the scientific community by providing high confidence validated research and analysis strategies, regardless the expertise in this field.\r\n\r\nThe motivation and emergence of this group came from the simultaneous publication of two articles from two independent groups and addressing the question of miRNA diversity, origins, evolution, and annotation:\r\n\r\n* Desvignes, T., Batzel, P., Berezikov, E., Eilbeck, K., Eppig, J. T., McAndrews, M. S., Singer, A., Postlethwait, J. H. (2015). miRNA Nomenclature: A View Incorporating Genetic Origins, Biosynthetic Pathways, and Sequence Variants. Trends in Genetics : TIG, 31(11), 613–626. http://doi.org/10.1016/j.tig.2015.09.002\r\n* Fromm, B., Billipp, T., Peck, L. E., Johansen, M., Tarver, J. E., King, B. L., Newcomb J., Sempere L. F., Flatmark K., Hovig E., Peterson, K. J. (2015). A Uniform System for the Annotation of Vertebrate microRNA Genes and the Evolution of the Human microRNAome. Annual Review of Genetics. http://doi.org/10.1146/annurev-genet-120213-092023 (http://mirgenedb.org)\r\n\r\nIn addition, plants miRNA research is facing the same problems. The different origin of plant and metazoan miRNA systems, however, make the creation of a unified “plant & metazoan” pattern hazardous. Nevertheless, tentative standardization on specific aspects is a future goal of the group.\r\n\r\n* Budak, H., Bulut, R., Kantar, M., & Alptekin, B. (2015). MicroRNA nomenclature and the need for a revised naming prescription. Briefings in Functional Genomics, elv026–. http://doi.org/10.1093/bfgp/elv026\r\n\r\nIf you work in relation with the miRNA field, and want to take part in this reflection group, please [join us](https://github.com/miRTop/miRTOP.github.io/issues/1) and share your ideas in order to create a large community working together to improve the study and analysis of miRNA data.\r\n\r\nCurrent projects:\r\n\r\n* Establishment of a unified Nomenclature system:\r\n\tTwo novel miRNA nomenclature systems have been simultaneously proposed by independent teams, in addition to the schemes proposed by previous groups. One focused on evolutionary conservation and clear orthology establishment to provide phylogenetically informative names based on Human annotation (Fromm and Peterson’s group), while the other envisioned a system for sequence variation analysis following nomenclature guidelines in use for coding-genes (Desvignes and Postlethwait group). The aim of this project is thus to establish a convergent framework, incorporating the strengths of each proposed system, to finalize a unified and persistent nomenclature system.\r\n\r\n* IsomiRs nomenclature: \r\n IsomiRs have proven to be bona fide variants of miRNA expression and could in some cases be functionally important and having different target sets than the reference miRNA they vary from. Because of functional importance of isomiRs, it appears crucial to be able to refer to a given one in a non-ambiguous way. The aim of this project is thus to formulate a standardized format for isomiR referencing and offer tools to apply them in an easy and general way.\r\n\r\nFuture projects and discussions:\r\n\r\n* What is the biological relevance of moRNAs? How to detect and annotate them?\r\n* Any other ideas or problems?\r\n\r\nCitation: zenodo citation link.\r\n\r\nContributors:\r\n\r\n* Lorena Pantano. Harvard TH Chan School of Public Health, Boston, USA\r\n* Thomas Desvignes, Institute of Neuroscience, University of Oregon, Eugene, OR, USA\r\n* John H. Postlethwait, Institute of Neuroscience, University of Oregon, Eugene, OR, USA\r\n* Karen EIlbeck. University of Utah, Biomedical Informatics.\r\n","google":"","note":"Don't delete this file! It's used internally to help with page regeneration."}

stylesheets/github-light.css

+116
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,116 @@
1+
/*
2+
Copyright 2014 GitHub Inc.
3+
4+
Licensed under the Apache License, Version 2.0 (the "License");
5+
you may not use this file except in compliance with the License.
6+
You may obtain a copy of the License at
7+
8+
http://www.apache.org/licenses/LICENSE-2.0
9+
10+
Unless required by applicable law or agreed to in writing, software
11+
distributed under the License is distributed on an "AS IS" BASIS,
12+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
13+
See the License for the specific language governing permissions and
14+
limitations under the License.
15+
16+
*/
17+
18+
.pl-c /* comment */ {
19+
color: #969896;
20+
}
21+
22+
.pl-c1 /* constant, markup.raw, meta.diff.header, meta.module-reference, meta.property-name, support, support.constant, support.variable, variable.other.constant */,
23+
.pl-s .pl-v /* string variable */ {
24+
color: #0086b3;
25+
}
26+
27+
.pl-e /* entity */,
28+
.pl-en /* entity.name */ {
29+
color: #795da3;
30+
}
31+
32+
.pl-s .pl-s1 /* string source */,
33+
.pl-smi /* storage.modifier.import, storage.modifier.package, storage.type.java, variable.other, variable.parameter.function */ {
34+
color: #333;
35+
}
36+
37+
.pl-ent /* entity.name.tag */ {
38+
color: #63a35c;
39+
}
40+
41+
.pl-k /* keyword, storage, storage.type */ {
42+
color: #a71d5d;
43+
}
44+
45+
.pl-pds /* punctuation.definition.string, string.regexp.character-class */,
46+
.pl-s /* string */,
47+
.pl-s .pl-pse .pl-s1 /* string punctuation.section.embedded source */,
48+
.pl-sr /* string.regexp */,
49+
.pl-sr .pl-cce /* string.regexp constant.character.escape */,
50+
.pl-sr .pl-sra /* string.regexp string.regexp.arbitrary-repitition */,
51+
.pl-sr .pl-sre /* string.regexp source.ruby.embedded */ {
52+
color: #183691;
53+
}
54+
55+
.pl-v /* variable */ {
56+
color: #ed6a43;
57+
}
58+
59+
.pl-id /* invalid.deprecated */ {
60+
color: #b52a1d;
61+
}
62+
63+
.pl-ii /* invalid.illegal */ {
64+
background-color: #b52a1d;
65+
color: #f8f8f8;
66+
}
67+
68+
.pl-sr .pl-cce /* string.regexp constant.character.escape */ {
69+
color: #63a35c;
70+
font-weight: bold;
71+
}
72+
73+
.pl-ml /* markup.list */ {
74+
color: #693a17;
75+
}
76+
77+
.pl-mh /* markup.heading */,
78+
.pl-mh .pl-en /* markup.heading entity.name */,
79+
.pl-ms /* meta.separator */ {
80+
color: #1d3e81;
81+
font-weight: bold;
82+
}
83+
84+
.pl-mq /* markup.quote */ {
85+
color: #008080;
86+
}
87+
88+
.pl-mi /* markup.italic */ {
89+
color: #333;
90+
font-style: italic;
91+
}
92+
93+
.pl-mb /* markup.bold */ {
94+
color: #333;
95+
font-weight: bold;
96+
}
97+
98+
.pl-md /* markup.deleted, meta.diff.header.from-file */ {
99+
background-color: #ffecec;
100+
color: #bd2c00;
101+
}
102+
103+
.pl-mi1 /* markup.inserted, meta.diff.header.to-file */ {
104+
background-color: #eaffea;
105+
color: #55a532;
106+
}
107+
108+
.pl-mdr /* meta.diff.range */ {
109+
color: #795da3;
110+
font-weight: bold;
111+
}
112+
113+
.pl-mo /* meta.output */ {
114+
color: #1d3e81;
115+
}
116+

0 commit comments

Comments
 (0)