You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Legal historians generally don't need all the linguisticky stuff of buzzword. So we need to figure out how to handle simple/advanced modes.
I've found it's hard to have these as toggles always available to users. If simple mode turns off regex, internals need to change and so on.
The first solution (for law-hist) will be hopefully to set simple mode at corpus level. Then we filter out very linguisticky columns from view, no ability to search by them, etc.
Later, the ideal solution would be a per-user setting (in their preferences, they can toggle advanced mode).
Things to do include:
adding simple_mode to Corpus object
determine which features are to be hidden/disabled in simple mode
getting this into django-plotly-dash and use to turn off/hide these various complex features
Then later, simple_mode becomes a feature of User, not Corpus
The text was updated successfully, but these errors were encountered:
Legal historians generally don't need all the linguisticky stuff of buzzword. So we need to figure out how to handle simple/advanced modes.
I've found it's hard to have these as toggles always available to users. If simple mode turns off regex, internals need to change and so on.
The first solution (for law-hist) will be hopefully to set simple mode at corpus level. Then we filter out very linguisticky columns from view, no ability to search by them, etc.
Later, the ideal solution would be a per-user setting (in their preferences, they can toggle advanced mode).
Things to do include:
simple_mode
to Corpus objectThen later,
simple_mode
becomes a feature ofUser
, notCorpus
The text was updated successfully, but these errors were encountered: