DH-Center-Tuebingen/Spacialist

Store user & project preferences in the DB

Closed this issue · 4 comments

derntl commented

Personal prefs should be persisted in the DB, including:

  • when a user changes the GUI langauge
  • when a user changes the column layouts

Project wide prefs should also be configurable and persisted in the DB:

  • the concept URL in thesaurus which is used as the root concept for tagging files in Spacialist
  • whether or not the geo map (or other part of the UI) shall be displayed.
  • whether or not a link/button to the ThesauRex instance should be displayed
  • whether or not tooltips should be shall be displayed
  • Project name (displayed in the upper left corner and in ThesauRex URIs)
v1r0x commented

We should discuss a proper format/layout for the user data. And we should think about what prefs we want to save and how we could extend it in the future.

derntl commented

We store the prefs as a JSONB object in the DB for each user. 💯

derntl commented

Table with all possible settings: preferences (id, label, default_value, allow_override)

Table linking user-specific values to a setting (only where allow_override is true) user_preferences (pref_id, user_id, value)

Oder so ähnlich 🎱

v1r0x commented

Project name (displayed in the upper left corner and in ThesauRex URIs)

The ThesauRex part obviously has to be done in ThesauRex. Will open an issue for it.