PBot Explore: OTU search

[ecurrano]

Here is how we would like the PBot Explore OTUSearch to look. Note this one is more complicated as there will be accordions, and cross-searches are also required (e.g., we want to be able to search for all OTUs assigned to an Collection). A star indicates the accordion header, and a dash indicates the searches in that accordion. Anything in brackets indicates where the particular search field exists or additional clarifications and should not be seen by users.

Search by OTU Name [fuzzy search]

*Search by Taxonomy

• Major taxon group
• PBDB parent taxon
• Family
• Genus

*Search by Fossil Characteristics

• Parts preserved
• Notable features preserved
• Quality index

*Search by Description

• Schema used to describe
• • Character
• • • State

*Search by Time

• Timescale -- Maximum Interval [Collection] -- Minimum interval [Collection]
• Ma range [numerical range, if this is possible currently; Collection node]

*Search by Location

• Latitude & Longitude [Collection node; separate entry fields for each, fuzzy search- like what PBDB does]
• Country [Collection] -- State/Province [Collection]

*Search by Stratigraphy

• Group [Collection]
• Formation [Collection]
• Member [Collection]
• Bed [Collection]

*Search by Metadata

• Collection name [Collection]
• Enterer [no idea where this is held]
• Reference
• Groups

[NoisyFlowers]

Are we sure we don't want to keep search by specimen and search by synonym?

Also, I think we should keep PBot ID (currently OTU ID). Just move it to Search by Metadata.

[ecurrano]

Yes on PBot ID under Search by Metadata.

Yes on specimen- I can see that folks might have a specimen and want to know what OTU it has been assigned to. Not sure where to put this.

I forgot that synonyms exist. :) This would be a handy feature. @doricon : would it be appropriate to put search by synonym under the "Search by Taxonomy" header?

[ecurrano]

Also note: We should discuss whether we want to keep the "Include synonyms" and "include comments" checkboxes. I believe that the vision for the OTU results page will handle the holotype descriptions and merged description features.

[NoisyFlowers]

Some of this is in paleobot/pbot-client@7b26dbb3108dfd9086e60c350549b48515480df6

merged to master and running on dev.

Complex queries are stubbed. I've retained some things I thought could be valuable.

[ecurrano]

What does stubbed mean?

So cool to see this coming up. We should decide whether we want "Search by taxonomy" or just "Taxonomy" as the accordion options. See OTU vs. Collection and pick preference tomorrow. Slight preference for eliminating "Search by" and keeping things streamlined and minimalistic.

[clairecleveland]

Search by Description/Character: Would it be "easy" to remove all states from this list? Or use bold or italics to indicate which options are characters vs states? Right now it's not immediately obvious which is which.

[doricon]

Back to "search by specimen" - that is handled explicitly by the Specimen search correct? if you pull up results for a specimen, you see if it was assigned to an OTU and can click on the OTU to pull up the OTU page.

For search by synonym - wouldn't you simply put the synonym name in the search field for Name, and it pulls up everything with that name and whatever it has been synonymized with?

[aazaff]

@NoisyFlowers will look into the ability to filter on multiple character:states

[ecurrano]

Can we search by multiple characters?

[NoisyFlowers]

Time interval search is in paleobot/pbot-client@a4a0f9db55db870defa6c951372e71030b7e1246

Location and stratigraphic search are in paleobot/pbot-client@43fd5c5c44e799a39c9eedc7607eb7b5b2d99d96 paleobot/pbot-client@a0f7eee6dd9489817bb45efbfb2ca9a4ffc86f7f

Collection and Entered By search are in paleobot/pbot-client@92b63e7094445c9d7e88a1dae28fa6a7fce521e2

merged to master and running on dev

Note: Implementing Collection and Entered By search nudge OTU over whatever twisted line leads to paleobot/pbot-client#37, so I've moved the filter logic into a separate OTUFilterHelper.js.

[NoisyFlowers]

Implementing multi-character search would be difficult. I'm not sure the usability payoff warrants the time investment right now.

If we want this new feature, we'll want to track it on a separate issue. It will require discussion as to how we would want such a feature to behave.