<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 2024-04-23 12:33,
<a class="moz-txt-link-abbreviated" href="mailto:sakurabayashi26@sanken.osaka-u.ac.jp">sakurabayashi26@sanken.osaka-u.ac.jp</a> wrote:<br>
</div>
<blockquote type="cite"
cite="mid:002b01da9561$41ee8d10$c5cba730$@sanken.osaka-u.ac.jp">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif"
lang="EN-US">I commented out the line with </span><span
style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif">“<span
lang="EN-US">;</span>”<span lang="EN-US">, but it doesn't
seem to work (errors still occur).</span></span></p>
</blockquote>
<p>The semicolon (';') is <i>not</i> a comment symbol, it starts a
text field that continues till the next semicolon at the beginning
of the line!</p>
<p>The comment symbol is a hash sign ('#').</p>
<p>So you can prepend the excluded lines with the <span
style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif">“<span
lang="EN-US">#</span>” or, for that matter, remove them
altogether.</span></p>
<blockquote type="cite"
cite="mid:002b01da9561$41ee8d10$c5cba730$@sanken.osaka-u.ac.jp">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif"><span
lang="EN-US"><o:p></o:p></span></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif"
lang="EN-US">Then, I replaced it with an arbitrary number to
meet the criteria shown in the red errors.</span></p>
</blockquote>
<p>From the data management perspective, it is better to have no
data than to have incorrect data, and the arbitrary values you
mention are apparently not correct.</p>
<p>Alternatively, you can replace the values by a single dot ('.');
this means the value is irrelevant. Such tokens are permitted by
the CIF and are interpreted as "the value is not relevant", which
approximately reflects your situation.<br>
</p>
<blockquote type="cite"
cite="mid:002b01da9561$41ee8d10$c5cba730$@sanken.osaka-u.ac.jp">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif"
lang="EN-US">Now, I can see no errors (two yellow warnings),
but the deposit button is not active yet (screenshot is
attached). <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif"
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif"
lang="EN-US">Sorry for bothering you, but I would appreciate
if you could tell me how to handle this problem.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif"
lang="EN-US"><o:p></o:p></span></p>
</blockquote>
<p>I would suggest removing the lines containing <span lang="EN-US">'_refine_ls_R_factor_gt'
and the '_refine_ls_wR_factor_ref', or prepend the, with the
comment sign "#". The structure should be then ready for
deposition. This procedure assumes that the numeric values for </span><span
lang="EN-US">the '_refine_ls_R_factor_gt' and the
'_refine_ls_wR_factor_ref' data items are on the same line as
the data names (</span><span lang="EN-US">'_refine_ls_R_factor_gt'
and the '_refine_ls_wR_factor_ref') themselves.<br>
</span></p>
<p><span lang="EN-US">After the deposition, please send us the newly
obtained COD ID and the two commented (or removed) lines with
the </span><span lang="EN-US">'_refine_ls_R_factor_gt' and the
'_refine_ls_wR_factor_ref' data items.</span></p>
<p><span lang="EN-US">Sorry for this hassle, but we need to have the
CIF syntax strictly correct for the COD, for the benefit of
future automatic processing by you and others :)<br>
</span></p>
<p><span lang="EN-US">HTH,</span></p>
<p><span lang="EN-US">Saulius<br>
</span></p>
<pre class="moz-signature" cols="72">--
Dr. Saulius Gražulis
Vilnius University Institute of Biotechnology, Saulėtekio al. 7
LT-10257 Vilnius, Lietuva (Lithuania)
mobile: (+370-684)-49802, (+370-614)-36366
</pre>
<br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.
</body>
</html>