Metadata should be editable through a structured form

[nathanncrt]

As a user, I want to edit metadata through a structured form instead of a raw text area, so that I can easily understand and modify metadata without needing to learn a specific syntax.

Context / Problem

Currently, metadata is edited using a simple text area with the YAML format, for example:

dc_creator: Autor
dc_title: Title
dc_issued: 2025-12-03T17:25:22.455Z
dc_isPartOf: GloseName
dc_license: null

This approach leads to:

• Poor readability
• High risk of formatting errors
• Difficulties for non-technical users
• Lack of guidance on expected values

Proposed Solution

Replace the text area with a structured form:

• Each metadata field is represented by a dedicated input
• Use appropriate input types:
  • Text input (e.g., title, creator)
  • Date picker (e.g., issued date)
  • Dropdown/select (e.g., language, license)
• Display labels instead of raw keys (e.g., "Title" instead of "dc_title")
• Optionally group fields into sections
• Some fields may have single or multiple values, such as dc_creator and dc_translator.

[benel]

Thank you for your suggestion.

Please rephrase the title of your ticket to comply with the rules given in your course:

• A verb should not be used for a developper's action but for user's action,
• An IMPROVEMENT title should include should.

[benel]

Please add to your requirements that several fields can have either single or multiple values: dc_creator, dc_translator.

[benel]

Currently, metadata is edited using a simple text area with a custom syntax

Please note that it is not a "custom syntax", but a well known RFC: YAML (see Wikipedia).

[benel]

Thank you @magdalenakhiat for rephrasing the ticket. Your new phrasing is fine.

However it seems that another feature team has found a correct title earlier:

• Metadata should be editable in a form rather than in a free text field #375.

Therefore I suggest you to close your ticket and to assign ticket 375 to your project.