The items' "created" attribute shouldn't be set as 0000:00:00 00:00:00

[DariaSegalard]

Description

What is the valuable outcome that cannot be achieved because of this bug?

For the moment, all the existing vases have the attribute "created" set to "0000:00:00 00:00:00" (it may be an issue due to the change of tool). This bug can be disturbing for the user who doesn't understand if there is an issue with the item's creation.

For which stakeholder (people, role, project, domain) is it important?

Every user looking at the date attribute of the vases.

Reproduction scenario

Steps to reproduce the behavior:

1. Go to 'https://vases.porphyry.org/'
2. Select the item '017'
3. See the attribute "created" set as 0000:00:00 00:00:00

Expected behavior

A clear and concise description of what you expected to happen. The creation date shouldn't be '0000:00:00 00:00:00'. It would be relevant to automatically set this attribute to the creation date of the item, or to let the user define it manually and hide it or delete it if the values is set to "0000:00:00 00:00:00".

Environment

• OS: Windows 11
• Browser: Edge 99

Workaround

Solution you found to avoid the problem.

• Hide the attribute "created" when it is equal to '0000:00:00 00:00:00'.
• Automatically set this attribute to the creation date of the item, or let the user set this date.
• Remove this attribute.

Deliverables status

Phase 1

• [ ] Scenarios (Gherkin)
• [ ] Implementation strategy

Phase 2

• [ ] Acceptance tests (Capybara)
• [ ] Implementation