Skip to content

Customize fields labels #986

@nitrosx

Description

@nitrosx

Summary

Currently the labels associated with each information shown on the GUI are fixed. In same cases, to provide a better user experience or because of site specific workflow and naming, a specific information is more meaningful if renamed.

Steps to Reproduce

n/a

Current Behaviour

At DESY, for example, they do not use Proposal Id for each Dataset, but they use a different id which is more meaningful for their management flow. On the dataset page, the information is statically labelled Proposal Id and cannot be changed on the GUI.

Expected Behaviour

Define for the frontend a dictionary that provide the labels associated with each field/information. If a site has specific needs, they can change the label associated.
Continuing with the DESY example, if they use an information named Project Id instead of Proposal Id, they could still save the Project Id in the proposal id field, but renamed "Project Id" in the frontend, so users do not get confused and the user experience improves.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions