Closed dustymc closed 8 months ago
Do we have documentation to explain to people how to search on attributes? Will this prevent people from requesting attributes via an Async Request? How to you request values to be downloaded if they don't appear in a visible table to select from? Do we need a basic search template for attributes or "traits"?
Currently it is almost impossible to find and download the rich amount of attribute data that we have in Arctos. I'm not saying to not remove non-cached values, but we need clear, usable alternate tools, and I don't have any idea what those are or how to direct people to use them. I would rather have those tools in place before we continue to reduce discoverability.
A couple of things that would help would be to have an attribute dropdown part of the default search template. Another would be to add "Attribute summary" to the results in the same way we have a parts summary and parts detail. I believe this was previously requested but never acted upon.
See error logs btime=2023-11-08%2016:55&etime=2023-11-08%2018:00
someone is having a very bad day because they've turned everything on, @mkoo thoughts on proceeding or discussing or whatever it takes to not get stuck?
Testing https://github.com/ArctosDB/arctos/issues/6201 is causing timeouts in the logs. I feel like we have to act on this, but I don't want to cut "us" off from important data (which might not be cached). HELP!!!!
Turn uncached attributes off in the results. this is about expectations-- these data are available through many other tools. thanks!
Pre-update stash:
Is your feature request related to a problem? Please describe.
Attributes are expensive, people like clicking all the buttons, that plugs up the toobs.
Describe what you're trying to accomplish
Less-frustrating user experience
Describe the solution you'd like
Remove non-cached attributes from search result options. They're still available as
Attribute Detail
and via the tools menu.Describe alternatives you've considered
Maybe we could somehow throw an error when more than some number of uncached attributes are selected or something of the sort, seems like lots of confusion and complexity for something that's probably not actually wanted and is readily available in other forms.
Additional context
See also https://github.com/ArctosDB/arctos/discussions/6179, this isn't unexpected.
From the logs - a limit of 3 records is still timing out.
Priority
High, this must be frustrating UX and I believe may be causing some instability.