Name

[odscjen]

From the scoping document:

"A name that reflects the purpose of the tool."

What should the tool be named? Similar tools for other data standards are named ‘Data Review Tool’, ‘Data Quality Tool’ and ‘Convert, Validate, Explore Tool (CoVE)’.

[odscjen]

"Risk Data Library metadata toolkit" agreed in the doc

[stufraser1]

@pzwsk are you also happy with "Risk Data Library Standard metadata toolkit"? as used currently:

We should agree today if possible.

[duncandewhurst]

Contrary to my comment in the scoping document, if you think that you'll likely add other tools to the toolkit in the future, I suggest that we choose a different name for CoVE so that we don't then have to rename it or redesign the landing page once other tools exist.

[stufraser1]

I had a niggling concern about that too...so how about, since conversion and validation is too much for a name, and it creates JSON files a number of ways, and I don't think cove describes enough what it does:
RDLS JSON creator
RDLS JSON writer
RDLS JSON convertor

[odscjen]

CoVE does two things primarily, validation and conversion. If this is too long a name then I'd recommend picking the element that you think your users are most likely to be using it for. In previous conversations you've indicated that most users will want to use the spreadsheet template to create their RDLS so I think "RDLS JSON convertor" is the better option as it emphasises the element of the tool that most users will be looking for.

[stufraser1]

@pzwsk and I spoke and confirmed we would like to go ahead with:
RDLS Convertor

With a subtitle or main heading in the tool of "Convert and validate RDLS metdata"

[radix0000]

This is now done. Should I go through the text on the front page and make it more in line with the idea that most users will be primarily thinking about converting their metadata to JSON and the validation is secondary e.g.
"Use one of the links below to check that your data complies ..." -> "Use one of the links below to convert
your metadata and check that it complies ..."?

[duncandewhurst]

@radix0000 yep, good spot. I've done that in the updates suggested in #21 (comment).

There is a typo in the header (metdata -> metadata), but in any case I would update the header as follows to reduce repetition:

[duncandewhurst]

From today's check-in call:

Above the line: Risk Data Library Standard Convertor
Below the line: Convert and validate your RDLS metadata

Remove 'Convert and validate your RDLS metadata' heading from the first box.

[radix0000]

Fix header

[radix0000]

Done.

[duncandewhurst]

The below the line text is missing 'RDLS' before 'metadata':

[stufraser1]

This now looks good. Can close I think

[radix0000]

Current minimalist header has "Risk Data Library Standard", "RDLS" and "Convert and validate ..." tagline once each. Can easily add more words if needed, though.

Closing as done but reopen if you disagree.