Paper organization

[jstonge]

Note:

We're organizing paper (#14 ) thoughts here (edit this issue directly) and having discussion below.

Purpose/thesis

• Describe allotaxonometer ecosystem
• enhance accessibility for researchers in this ecosystem

Working outline

• Intro
  • Para: Brief intro to study of allometric scaling
  • Para: studying these systems needs an instrument
  • Fig: allotax plot example
  • AIM: enhance accessibility to study allotaxonometry
    • lay out rest of paper: web app, JS package, py-allotax
• Allotaxonometry
  • Description of this area of work
• Tools
  • JSO ecosystem fig.
• Use cases: software design versus accessibility
  • Table to summarize these?
    • rows of: broad class of use case, tools, user type, design considerations for accessibility, design trade-off?
  • broad use case 1
  • broad use case 2
  • broad use case 3
• Concluding remarks
  • lessons learned from enhancing the accessibility of allotaxonometry
    • Sometimes maintainability (strict adherence to best practices in modularizing code and setting up extensibility) can complicate using the tool. Further, setting up code for extensibility is not requisite to maintainability, at least in the case of this ecosystem and seemed to pull away from the primary goal of getting users a tangible tool they could use within 10 minutes.

[amafehr]

@jstonge @carterwward I've begun. Let's flesh out here as much as possible before moving to paper. I think it's easier.