Sharing a validation test URL(two things that CoVE does, that the IATI Validator doesnt)

[stevieflow]

It isn't possible to successfully share the validation results from a test on data in someone's workspace (I think)

I can share the URL of a test, but the other person will see:

It is possible to share URLs to public data that has been tested

With CoVE, we did some work (eg OpenDataServices/cove#1368) on two user needs:

1. I have uploaded some data, and want to share the test results with someone else, by sending them the URL

and

2. I have just uploaded a dataset I've recently (within the sever delete parameters) tested, can CoVE load the results from cache (to save me waiting for the results)?

This persistence and cache is useful, especially when working remotely with others

I don't know if this was a design choice, or just not in the design of the IATI Validator, but it would be useful to understand whether either of these are possible

cc/ @Bjwebb @robredpath @simon-20

[robredpath]

I have uploaded some data, and want to share the test results with someone else, by sending them the URL

On the IATI Validator, you do this by sharing your workspace rather than an individual file's results. The recipient is able to delete files from the workspace or add more, so you do need to make sure that the workspace only has things that are relevant to the recipient and that you trust them!

You can create a new workspace by opening https://validator.iatistandard.org/validate in a private browsing window, and going through the flow to validate a file.

I have just uploaded a dataset I've recently (within the sever delete parameters) tested, can CoVE load the results from cache (to save me waiting for the results)?

Once generated, a validation results page in the IATI Validator works like this.

Is that a suitable workflow @stevieflow ? It's not quite as neat as just copying the link out of your browser window like in CoVE but does a comparable job. The workspace link is on the results page as "Return to your workspace". The faff is maintaining a workspace per-client or per-job.

The proper fix is probably to add IATI Account support to the Validator, so that we can support sharing more sensibly.

[stevieflow]

Thanks @robredpath

The proper fix is probably to add IATI Account support to the Validator, so that we can support sharing more sensibly.

Yes, it does point to that

How about the cache issue? That was/is a real boon with CoVE, as the other person doesn't have to wait for the results to load (particularly relevant if validating a large file)

[robredpath]

How about the cache issue?

That's basically the same for IATI Validator. If you share a workspace link with someone, they can click through to files and see the validation results without waiting for the file to process again. Are you seeing issues with that?