expoweb/svxvalid.html

31 lines
1.5 KiB
HTML

<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Expo Systems - Data Validation</title>
<link rel="stylesheet" type="text/css" href="../css/main2.css" />
</head>
<body>
<h1>Expo Systems - Data Validation</h1>
<h2>SVX files referring to wallets and vice-versa</h2>
<!-- you can edit this by any normal methois, either Edit This Page or using version contron pull/edit/commit/push
because the actual updated data is pulled in through the iframe -->
<p>
"json" is the survex filename stated in the <code>2018#03/content.json</code> file in surveyscans/2018/ .
<p>
"svx" means that the survex file has a *ref field which states that the wallet folder holding the original notes is <code>2018#03</code>
<iframe name="erriframe" width="90%" height="45%"
src="svx-refs.err.html" frameborder="1" ></iframe>
<p>These validation concerns are generated by scripts check-svx.sh, check-refs.sh, check-refs.awk in the ::loser:: repository.
See <a href="handbook/troggle/otherscripts.html">handbook "other scripts"</a> for further documentaiotn.
<p>These scripts and checks could all be done as internal troggle-generated pages as the data used
is (mostly) present in the tables after importing the wallet images and the survex files.
But doing it outside troggle means that we get feedback on errors before going through the import procedure, so gives us some earlier warning.</p>
<iframe name="okiframe" width="90%" height="20%"
src="svx-refs.ok.html" frameborder="1" ></iframe>
<hr />
</body></html>