Shuffle vs. Select Mode

[MCBoarder289]

As a larger feature, I'd like to make a workflow that instead of randomly selecting a few, you're able to pick from a list after initially fetching.

This way you can get those results and check if particular items are available.

[MCBoarder289]

This will require a pretty significant refactor of certain things, so I'll outline key areas that need to be adjusted to make this happen:

Routing I'm thinking we may want to introduce routing or a new page. It may be possible to keep this all a single page, but it might end up a little too complicated to switch up the behavior of buttons. This will be a decision to make: new search page or some dynamic toggle.

• Counterpoint: It could be simple enough to hide/show the search bar w/ results based on a toggle, and then determine a different path for the Results components.

Shelf Data Refactor Need to update the cached data from a shelf from a List into a typed dictionary to ensure we have a O(1) search vs. O(n).

• Thinking the datastore will be a dictionary, where the key is the "Title - Author", and the value is the Book object
• When in Shuffle mode, it will randomly select from the dictionary's values
• When in Select mode, you will pick from the dropdown, and the list that you've selected will be displayed.

App Considerations

• Return all of the results to the browser for search mode? Or query BE given a list of values when selecting each?

Analytics Considerations

• New column on "shelf_searches" to represent what "mode" the search was done in
• In the above app considerations, may want to keep things in the BE so the FE doesn't need to send an event.
  • Don't want to expose analytics topics or creds
  • Keeps the emission of events from the BE and not the client/browser
• How to track books in the database - Likely want to only track those that are "selected" by the UI, which might necessitate calling the BE with the list