Create request metadata and you will be able to search requests by these fields (using the advanced search or filters) to better organize yourself.
The system allows any user to enter metadata (key/value pairs) freely during the creation of a request (within the options that are displayed when clicking on “Advanced writing”). However, this can lead to denormalization when exploiting the metadata, since two different users could give a different name, for example, to the key “file code”. Sometimes it is detected that for an instance, there is some common metadata that is interesting to fill in when creating a request, so it can be registered as global metadata, and its value can be set (optionally) by the creator of the request.
In this menu option we can create global metadata for our instance, which will be displayed in the Advanced Redaction of the requests.
By clicking on the “Metadata Requests” menu option, we are redirected to a screen where the existing global metadata for our instance are listed:
In this list we have the typical options of editing (pencil), deleting (X) and creating a new metadata. Clicking on the “Add” button opens the metadata creation/editing window:
As can be seen, to create metadata at a global level, it is enough to fill in its key, being able to assign it an informative description and a default value, as well as its mandatory nature.
Caution should be exercised in the use of the default value, since by default, any request created will have the associated metadata with the default value assigned to it. If the user does not go into Advanced Compose to change it, the metadata will have that value. Therefore, we should only use the default value if it really is the default value (for example, a metadata “Year of the request” could have the current year as the default value, but it would force us to edit the metadata on January 1st of the following year to avoid possible errors in new requests).