Closed magicalmary closed 1 month ago
The DD-MM-YYYY
date format can be confusing based on where the view is located. We use MM-DD-YYYY
in the US but most other countries use DD-MM-YYYY so 06-07-2024
can be confusing.
Did the user specify a reason why they think we should change it? In the JSON version (that would be used to communicate with other systems) we use the ISO8601 standard for date formatting. E.g. YYYY-MM-DDThh:mm:ss+hh:mm
.
We've decided to leave the date format so we do not confuse European users.
@magicalmary the width of the content in "Planned outputs" is different from the "Project description", because the content under "Planned outputs" is actually in an HTML list (i.e., using <ul><ul/>
tag), whereas the content under "Project description" is in a normal <p>
paragraph tag.
I believe the narrower width will make it more readable when there are multiple items in the list.
Consulted with Juliet, and we noted the 'Planned Outputs' landing page descriptions are included and can take up a lot of space (depending on the text entry). Can this be removed, and replaced with the table of outputs as displayed in a downloaded DMP, @briri ? (see attachment)
@mariapraetzellis, I know you are busy, but when you get the chance, can you weigh in on what you think about displaying Planned Research Outputs in a table format?
For now, I am going to mark this as blocked
@mariapraetzellis Will review this and comment with a final decision on implementation.
For now let's leave the Planned Outputs section formatted as is. The current format works well with newly created DMPs (not uploaded) & I think will work with most uploaded plans as well. However, if we see that its a problem we will reopen this issue and transform the Planned Outputs section into a table.
One of the pilot team members noted some formatting issues on the 'landing pages' for projects registered using DMP Tool: