Possible usability improvements

[lilimelgar]

These are some possible aspects that could improve the usability of the editor, giving more support for editing tasks:

• Sort items in the record list (mostly per name, per creation date)
• In the record editing page, add collapsible levels (not only all/none but for example Level2, Level3)
• In the record editing page, notify the user confirming when the data was saved

[menzowindhouwer]

regarding the first: sorting. If the column is marked as sortable, e.g. like https://github.com/CLARIAH/vocab-registry-editor/blob/main/data/apps/vocabs/config.toml#L15, you can click on the header to sort the rows on that column.

[lilimelgar]

One more improvement:

• In the current service editor, each record is stored as a new version, add the option to configure which date is shown in the editor? see: Test if these are possible bugs in the editor CLARIAH/vocab-registry-editor#5 (comment)

[lilimelgar]

One more possible improvement:

• If possible, the XML content should also be ready to be read in any generic editor in a hierarchical way. See: Test if these are possible bugs in the editor CLARIAH/vocab-registry-editor#5 (comment)

[menzowindhouwer]

Using <xsl:output method="xml" indent="yes"/> we could add the indentation to make a raw record human readible on disk. As this is a top level directive in the XSLT it is tricky to make this an option that can be switched on via the configuration ...

[menzowindhouwer]

Indeed the CMDI header is called MdCreationDate, while we use it as the modification date. We should straighten that out. The actual modification epoch is stored in a foreign attribute, so we could keep the MdCreationDate constant ...