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
When editing or modifying an event, it would be useful to limit the list of available features.
For example, the OVPF only uses the 'measure' and 'data_collection' features for discipline NODES events (seismology, geodesy, etc.). But these NODES have an additional 'sensor' feature (for calibration file and PROC association).
To prevent users from entering 'sensor' as a feature in the event form, it might be useful to hide it.
One could then imagine a blacklist or a whitelist in a configuration file for this.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When editing or modifying an event, it would be useful to limit the list of available features.
For example, the OVPF only uses the 'measure' and 'data_collection' features for discipline NODES events (seismology, geodesy, etc.). But these NODES have an additional 'sensor' feature (for calibration file and PROC association).
To prevent users from entering 'sensor' as a feature in the event form, it might be useful to hide it.
One could then imagine a blacklist or a whitelist in a configuration file for this.
Beta Was this translation helpful? Give feedback.
All reactions