You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/Interim-taxonomy-file-format.md
+19-4Lines changed: 19 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,7 +43,7 @@ Example (from NCBI):
43
43
*_uniqueName_: a human-readable string that is unique to this taxon, typically the taxon name if it is unique, or taxon name followed by "([rank] in [ancestor])" where rank is the taxon's rank and ancestor is an ancestor that is unique to this taxon (among the taxa that have the same name).
44
44
*_flags_: a comma-separated list of flags or markers. Usually these are generated by taxonomy synthesis and are used to decide whether a taxon is 'hidden' or not. For example, if there's an 'extinct' flag then it may be desirable to suppress the taxon in an application. See [here](https://github.com/OpenTreeOfLife/taxomachine/blob/master/src/main/java/org/opentree/taxonomy/OTTFlag.java).
45
45
46
-
### Synonyms
46
+
### File `synonyms.tsv`
47
47
48
48
Usually there are synonyms. These go into a second file, `synonyms.tsv`. This file must have a header row
49
49
@@ -60,11 +60,26 @@ Example from NCBI:
60
60
61
61
89373 | Flexibacteraceae | synonym | |
62
62
63
-
### Metadata
63
+
### File `forwards.tsv`
64
64
65
-
Overall metadata for the taxonomy is placed in a separate file. The metadata format is currently under development. `Smasher` generates this in JSON format as `about.json`, but this file is currently not used programmatically, and is in the process of being overhauled. When generating a taxonomy according to this format in external tools, for now it is best to simply write a markdown or plain text file called `about.md` (in the same directory as `taxonomy.tsv` and `synonyms.tsv`).
65
+
This file provides aliases, resulting from a situation where one taxon
66
+
id has been discovered to be equivalent to another. This can be due
67
+
to changes in the the way the taxonomy is processed, discovery of new
68
+
synonyms, or due to merge events ("lumping"). For example:
66
69
67
-
The metadata provided in the file should include the source of the taxonomy (article or database) as a URL and any other descriptive information that's available. The purpose of the metadata is not just explanatory but also to explain how to check the correctness of the taxonomy against its source and make corrections and other improvements should the source be updated. When using information from changing sources (databases) the date or dates of retrieval should be recorded.
70
+
id replacement
71
+
3434315 3434301
72
+
5255304 828663
73
+
74
+
The second line says that older id 3434315 (occurring in one or more
75
+
previous versions) should be replaced by newer 3434301 (defined in
76
+
this version).
77
+
78
+
79
+
### File `version.txt`
80
+
81
+
When OTT is generated, the version number is placed in this file,
0 commit comments