Refactor Community Reviews (Observations) to use Tags

[mekarpeles]

Proposal

If one clicks to add a review...

A modified modal should open that shows some examples and allows the patron to search (and/or suggest new tags); something like:

The observations table should be modified to use a single value, which is the Tag key rather than the existing label and value pairs:
https://github.com/internetarchive/openlibrary/blob/master/openlibrary/core/schema.sql#L76-L77

The community reviews form should also open after the patrons adds a star rating, asking them if they want to add any tags to help other patrons evaluate whether the book is right for them.

Justification

1. Community Review Tags aren't in the search engine (and are useful)
2. The "Observations" naming is confusing Document what the Observation Form does #10319
3. Community reviews are currently their own system (maintainability)
4. Community reviews form currently require multiple levels of categories and clicking, which should be collapsed into single tags (e.g. instead of hypothetical cases like "pace" -> "fast", it should appear as "Fast Paced" and use the Tag "community: fast paced"

Breakdown

Requirements Checklist

• Switch observations db schema to
• Update observations UI to search for tags by name (drop "community:" from tag prefix)
• Open review form automatically after patron star rates book
• Add documentation re: Document what the Observation Form does #10319

Related files

[techy4shri]

Is this issue supposed to be tackled by one assignees or multiple people?

[mekarpeles]

This is an epic, i.e. A tracking issue for a larger project. Epics are owned by individuals who project manage them to completion and almost always this is limited to staff, leads, or fellows w/ their mentors. A part of the process of leading an epic is breaking it down into sub issues that then get coordinated with the rest of the community