tbx organization

[nickrsan]

Original report by AndyB (Bitbucket: AndyB, GitHub: AndyB).

---

It might make sense to re-organize the toolbox categories with the addition of the new tools.

Proposed structure:

Input:

• Add HUC12 Attributes
• Add Unique Field Values as Alt Codes
• Import Dataset
• Retry Import

Modification

• Manually Add or Modify Data
• Look Up Records

Output

• Generate Layer from Query
• Generate Map
• Generate Species Matrix
• Summary Stats

[nickrsan]

Original comment by Nicholas Santos (Bitbucket: nickrsan, GitHub: nickrsan).

---

I think this would be fine. Where do you think that the Add Species Data to Collection should go? I think I like Look Up Records being in the Output toolset though

[nickrsan]

Original comment by AndyB (Bitbucket: AndyB, GitHub: AndyB).

---

Let's put Add Species Data to Collection into Modification. I think that logically you would use Add Species Data to Collection right after the Add or Modify tool.

I'm ok with leaving Look up record records in output. I was originally thinking that the toolbox structure should group tools according workflow (ie tools to get data into PISCES, tools used for QC, and tools used to export data to other formats). I imagined that the look up records tool would be used mostly to verify records during the QC process but I could also see it being used as a quick way to export records for a selected area.

[nickrsan]

Original comment by Nicholas Santos (Bitbucket: nickrsan, GitHub: nickrsan).

---

OK, I agree - I like the group by workflow idea in general and have made all the other edits.