|
@@ -163,9 +163,8 @@ View::show_header('Uploading Rules', 'rules');
|
163
|
163
|
<strong>Compression.</strong>
|
164
|
164
|
"10 GiB or 10,000 files."
|
165
|
165
|
Compression is required if your torrent is > 10 GiB or if it contains > 10,000 files.
|
166
|
|
- Otherwise, please compress text files if it reduces the torrent size by > 30%.
|
167
|
|
- Never compress torrents < 2 GiB or binary files < 10 GiB. Multipart archives are only allowed for torrents > 10
|
168
|
|
- GiB.
|
|
166
|
+ Otherwise, please compress text files only if it reduces the torrent size by > 30% and avoid compressing binary files.
|
|
167
|
+ Multipart archives are only allowed for torrents > 10 GiB.
|
169
|
168
|
</li>
|
170
|
169
|
|
171
|
170
|
<li id="r1.10"><a href="#h1"><strong>↑</strong></a> <a href="#r1.10">1.10</a>
|
|
@@ -183,11 +182,9 @@ View::show_header('Uploading Rules', 'rules');
|
183
|
182
|
<strong>Supplemental Packs.</strong>
|
184
|
183
|
I strongly recommend <a href="https://semver.org/" target="_blank">Semantic Versioning</a> for your original
|
185
|
184
|
data.
|
186
|
|
- Supplemental packs may include a collection of documents, utilities, protocols, metadata, etc., specifically
|
187
|
|
- prepared for release.
|
|
185
|
+ Supplemental packs may include a collection of citations, documents, utilities, protocols, metadata, disk images, etc., specifically prepared for release.
|
188
|
186
|
The collection should be a separate torrent if the collection constitutes a project in its own right.
|
189
|
|
- But if you have, e.g., 100 MiB of XML and no other metadata for 5 GB of photos, please include it in the main
|
190
|
|
- torrent.
|
|
187
|
+ If you only have metadata generated in the data processing workflow, please include it in the main torrent.
|
191
|
188
|
</li>
|
192
|
189
|
</ul>
|
193
|
190
|
</div>
|
|
@@ -197,7 +194,7 @@ View::show_header('Uploading Rules', 'rules');
|
197
|
194
|
<ul>
|
198
|
195
|
<li id="r2.1"><a href="#h2"><strong>↑</strong></a> <a href="#r2.1">2.1</a>
|
199
|
196
|
<strong>Multiple Formats Allowed.</strong>
|
200
|
|
- It's fine if there's an EMBL and a FASTA of the same data. If you need to convert a dataset for your analysis,
|
|
197
|
+ It's fine if there's an EMBL and a FASTA of the same data. If you need to convert a dataset for your own analysis,
|
201
|
198
|
please upload a quality conversion with supplemetal info.
|
202
|
199
|
Remember that small, one-shot metadata are better included with the data, and collections of docs and utils
|
203
|
200
|
are better separate from it.
|
|
@@ -213,6 +210,7 @@ View::show_header('Uploading Rules', 'rules');
|
213
|
210
|
Please add a link in the old data's Torrent Group Description to the new data.
|
214
|
211
|
Git repos can be trumped at the commit and patch levels.
|
215
|
212
|
Then normal SemVer rules take effect for properly tagged releases.
|
|
213
|
+ In an ideal world, only releases tagged with a specific version number would be allowed because this is BitTorrent's main strength.
|
216
|
214
|
</li>
|
217
|
215
|
|
218
|
216
|
<li id="r2.3"><a href="#h2"><strong>↑</strong></a> <a href="#r2.3">2.3</a>
|
|
@@ -225,10 +223,12 @@ View::show_header('Uploading Rules', 'rules');
|
225
|
223
|
</li>
|
226
|
224
|
|
227
|
225
|
<li id="r2.4"><a href="#h2"><strong>↑</strong></a> <a href="#r2.4">2.4</a>
|
228
|
|
- <strong>Two Weeks Unseeded.</strong>
|
229
|
|
- If you have the original torrent files for the inactive torrent, reseed those original files instead of
|
230
|
|
- uploading a new torrent.
|
231
|
|
- Uploading a replacement torrent should be done only when the original files are unavailable.
|
|
226
|
+ <strong>One Month Unseeded.</strong>
|
|
227
|
+ Please try requesting a reseed before anything.
|
|
228
|
+ This sends a mass PM to all snatchers asking them to resume seeding the files.
|
|
229
|
+ If you have the original torrent files for the inactive torrent, reseed those instead of uploading a new torrent.
|
|
230
|
+ Uploading a replacement torrent should be done only when the original files are unavailable and/or the torrent hasn't been seeded for a month.
|
|
231
|
+ The site automatically deletes dead torrents after 6 months.
|
232
|
232
|
</li>
|
233
|
233
|
|
234
|
234
|
<li id="r2.5"><a href="#h2"><strong>↑</strong></a> <a href="#r2.5">2.5</a>
|
|
@@ -245,6 +245,8 @@ View::show_header('Uploading Rules', 'rules');
|
245
|
245
|
Add the announce URL as the only item on the tracker list and click the checkbox marked private.
|
246
|
246
|
Please don't share <code>.torrent</code> files because they have your passkey embedded in them.
|
247
|
247
|
This passkey lets the tracker know who's uploading and downloading, and leaking it will nuke your ratio.
|
|
248
|
+ It's okay to share the files themselves any way you see fit.
|
|
249
|
+ Automatic mirroring to OpenBitTorrent is in development.
|
248
|
250
|
<br /><br />
|
249
|
251
|
</li>
|
250
|
252
|
|
|
@@ -253,15 +255,15 @@ View::show_header('Uploading Rules', 'rules');
|
253
|
255
|
The categories loosely follow the central dogma.
|
254
|
256
|
It depends on what alphabet the sequence uses, e.g., ACGT vs. ACGU.
|
255
|
257
|
All medical imaging data goes in the Imaging category.
|
256
|
|
- All extra documentation, custom scripts, etc., goes in Documents.
|
257
|
|
- Plasmids and things that don't quite fit go in Other.
|
|
258
|
+ <!-- All extra documentation, custom scripts, etc., goes in Documents. -->
|
|
259
|
+ Toolkits and other things that aren't strictly biology data go in Extras.
|
258
|
260
|
<br /><br />
|
259
|
261
|
</li>
|
260
|
262
|
|
261
|
263
|
<li id="r3.3"><a href="#h3"><strong>↑</strong></a> <a href="#r3.3">3.3</a>
|
262
|
264
|
<strong>Accession Number.</strong>
|
263
|
|
- Please add accession numbers when the data source issued them.
|
264
|
|
- The number can be any format but it must correspond to the actual torrent data.
|
|
265
|
+ Please add accession numbers if they come with the data or if you acquired them for your own data.
|
|
266
|
+ The number can be any format but it must correspond to the actual nucleotide or amino acid sequences represented on disk.
|
265
|
267
|
Don't add accession numbers just because the metadata matches.
|
266
|
268
|
RefSeq and UniProt integration is in development.
|
267
|
269
|
<br /><br />
|
|
@@ -269,7 +271,7 @@ View::show_header('Uploading Rules', 'rules');
|
269
|
271
|
|
270
|
272
|
<li id="r3.4"><a href="#h3"><strong>↑</strong></a> <a href="#r3.4">3.4</a>
|
271
|
273
|
<strong>Torrent Title.</strong>
|
272
|
|
- A short description of the torrent contents.
|
|
274
|
+ A short description of the torrent contents such as a FASTA definition line.
|
273
|
275
|
It doesn't need to match the folders but it should tell you what the data is at a glance.
|
274
|
276
|
Please avoid adding other metadata such as Strain, Platform, etc., with a dedicated field.
|
275
|
277
|
<br /><br />
|
|
@@ -278,22 +280,24 @@ View::show_header('Uploading Rules', 'rules');
|
278
|
280
|
<li id="r3.5"><a href="#h3"><strong>↑</strong></a> <a href="#r3.5">3.5</a>
|
279
|
281
|
<strong>Organism.</strong>
|
280
|
282
|
The relevant organism's binomial name and optional subspecies.
|
281
|
|
- Please use <em>Genus species subspecies</em> and no terms such as var. and subsp.
|
282
|
|
- Multiple organisms and a FASTA/GenBank parser are both in development.
|
|
283
|
+ Please use <em>Genus species subspecies</em> and not terms such as var. and subsp.
|
|
284
|
+ Multiple organisms and a way to autofill from FASTA/GenBank headers are both in development.
|
283
|
285
|
<br /><br />
|
284
|
286
|
</li>
|
285
|
287
|
|
286
|
288
|
<li id="r3.6"><a href="#h3"><strong>↑</strong></a> <a href="#r3.6">3.6</a>
|
287
|
289
|
<strong>Strain/Variety.</strong>
|
288
|
290
|
The strain's name if known.
|
289
|
|
- This should correspond to a specific cell line or breed.
|
|
291
|
+ This should correspond to a specific cell line, cultivar, or breed.
|
|
292
|
+ If the species is <em>H. sapiens</em> and the subject's race is known and relevant, e.g., as in a torrent of gene sequences related to sickle cell anemia, please add it here.
|
290
|
293
|
Otherwise, please omit it.
|
|
294
|
+ Do not put any identifying patient data here or anywhere else.
|
291
|
295
|
<br /><br />
|
292
|
296
|
</li>
|
293
|
297
|
|
294
|
298
|
<li id="r3.7"><a href="#h3"><strong>↑</strong></a> <a href="#r3.7">3.7</a>
|
295
|
299
|
<strong>Authors(s).</strong>
|
296
|
|
- The Author field should contain only the author name.
|
|
300
|
+ The Author field should contain only the author name and no titles.
|
297
|
301
|
The upload form supports multiple authors.
|
298
|
302
|
Do a search before uploading to get their names right.
|
299
|
303
|
Consistent author naming makes browsing easier because it groups torrents on a common page.
|
|
@@ -348,7 +352,7 @@ View::show_header('Uploading Rules', 'rules');
|
348
|
352
|
href="forums.php?action=viewforum&forumid=<?= SUGGESTIONS_FORUM_ID ?>">Please
|
349
|
353
|
post in the suggestions forum</a>
|
350
|
354
|
if you'd like to request a new format.
|
351
|
|
- Note that the formats change for the Imaging category.
|
|
355
|
+ Note that the formats change for the Protein and Imaging categories.
|
352
|
356
|
A file extension parser is in development.
|
353
|
357
|
<br /><br />
|
354
|
358
|
</li>
|
|
@@ -360,7 +364,7 @@ View::show_header('Uploading Rules', 'rules');
|
360
|
364
|
The options correspond in higher conceptual language to:
|
361
|
365
|
a single piece of information, structural information, especially deep or broad information, and an exhaustive
|
362
|
366
|
source.
|
363
|
|
- Please use the Other option if you'd like to enter a resolution such as "420 subjects."
|
|
367
|
+ Please use the Other option if you'd like to enter a specific resolution such as "420 subjects from Boston."
|
364
|
368
|
<br /><br />
|
365
|
369
|
</li>
|
366
|
370
|
|
|
@@ -397,7 +401,7 @@ View::show_header('Uploading Rules', 'rules');
|
397
|
401
|
DOI numbers should be well-formed, one per line.
|
398
|
402
|
The system currently discards malformed DOI numbers instead of extracting them from arbitrary strings.
|
399
|
403
|
An auto-extract feature is in development.
|
400
|
|
- If your research is a URI, please use the Torrent Group Description field.
|
|
404
|
+ If your research is a URI, please use the Torrent Group Description field for now.
|
401
|
405
|
<br /><br />
|
402
|
406
|
</li>
|
403
|
407
|
|
|
@@ -413,14 +417,14 @@ View::show_header('Uploading Rules', 'rules');
|
413
|
417
|
<strong>Torrent Description.</strong>
|
414
|
418
|
Specific info about the protocols and equipment relevant to <em>this</em> data.
|
415
|
419
|
This text is hidden by default.
|
416
|
|
- It displays when you click the Torrent Title next to [ DL | ... | PL ].
|
|
420
|
+ It displays when you click the Torrent Title next to [ DL | PL ].
|
417
|
421
|
Please discuss materials and methods here.
|
418
|
422
|
<br /><br />
|
419
|
423
|
</li>
|
420
|
424
|
|
421
|
425
|
<li id="r3.20"><a href="#h3"><strong>↑</strong></a> <a href="#r3.20">3.20</a>
|
422
|
426
|
<strong>Aligned Sequence.</strong>
|
423
|
|
- Does the data come with any metadata of an analytical nature, such as alignment data (mandatory)?
|
|
427
|
+ Does the data come with any metadata of an analytical nature, such as alignment data (mandatory if checked)?
|
424
|
428
|
If so, does the torrent folder contain the scripts used to generate the metadata (optional)?
|
425
|
429
|
<br /><br />
|
426
|
430
|
</li>
|