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
The CSV export format is designed to mimic the summary table we show the user, but it would be good for downstream applications to have this format documented on the website or docs somewhere.
The text was updated successfully, but these errors were encountered:
This should go into the Klados wiki, with a link to it from the application.
This won't be archived. Let's put it into a docs/ folder and then link directly to the Markdown file.
- Added note that definition should include qualifiers (closes#168)
- Documented the CSV export format (related to #257, but I won't close that until I like to it from somewhere in the interface) as [a Markdown file](https://github.com/phyloref/klados/blob/bfae34e42e954920191e3e473f31ee2ae49ffdde/docs/ExportFormats.md).
- Fixed a bug in which we were providing all the expected resolutions before all the actual resolution in the CSV file, despite the header saying that they should be interleaved (i.e. `expected 1, actual 1, expected 2, actual 2`).
- The Open Tree of Life lookup code was previously recording the provenance of the phylogeny in the phylogeny description field, but since this field is no longer used, I've moved it into the phylogeny curator notes field (see example below).
- I accidentally turned on "reformat file on save", and so my IDE changed a bunch of file formatting without me noticing. That shouldn't change any functionality and should be easier to read/maintain in the future, but it's still annoying.
This PR also closes#300 by modifying the summary table to make it clear that the final columns refer to phylogenies and replacing phylogeny descriptions (which are no longer displayed in Klados) with phylogeny curator notes.
The CSV export format is designed to mimic the summary table we show the user, but it would be good for downstream applications to have this format documented on the website or docs somewhere.
The text was updated successfully, but these errors were encountered: