<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas",serif;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Hi Saulius<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Thank you for the very informative reply.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Yes, I have just checked and notice the “Added full bibliography…” records. So I think you have things largely covered. As you suggest,
there may be the danger for updates on entries to “fall through the cracks”. <o:p>
</o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">I will check through the details in your email try to think of sensible ways we might work together on this. It is certainly better
to avoid making local “corrections” specifically for the CrystalWorks implementation. It does make sense to make updates centrally!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Best Regards<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Bob<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Saulius Gražulis <grazulis@ibt.lt>
<br>
<b>Sent:</b> 29 March 2023 07:04<br>
<b>To:</b> McMeeking, Robert (STFC,DL,SC) <robert.mcmeeking@stfc.ac.uk><br>
<b>Cc:</b> cod-bugs@lists.crystallography.net<br>
<b>Subject:</b> Re: Accepted Manuscripts Entries<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Hi, Bob,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">many thanks for your e-mail!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">On 2023-03-28 19:26, Robert McMeeking - STFC UKRI wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">I have noticed that there are now quite a lot of “Accepted Manuscripts” entries making their way into Crystallography Open Database – especially from Royal Society of Chemistry.
It is good to get the structures as soon as possible, but there is information such as Volume/page numbers which needs updating. I have been thinking about ways of setting up a system to update this information for the CrystalWorks implementation at Daresbury.
I can see ways of doing this this using the DOI for the articles using various CrossRef web services.
<o:p></o:p></p>
</blockquote>
<p>Currently, the following procedure is implemented in our Web crawlers:<o:p></o:p></p>
<p>step 1: every day we scan RSS feeds of multiple publishers to learn what new papers are published. This is done not so much to get the structures as early as possible (although this is a positive outcome as well, IMHO), but to have machine readable list
of published papers (RSS feeds are much more amenable to automatic processing than web pages), and to have additional source of publication information.<o:p></o:p></p>
<p>Since pages are not assigned at this point, and RSS feed differ in the amount of bibliographic information they provide, we take only DOI from the RSS feed, which is always present and os sufficient to get the full bibliography later;<o:p></o:p></p>
<p>step 2: once a month we scan the published papers published in the current year by the publishers we monitor, and we check if full bibliographic information is already available. If that is the case, we update the COD record with complete bibliography. This
is indicated in the COD SVN logs with the "Adding full bibliography for ..." log entries. Paper lists (DOIs) are obtained from CrossRef, and bibliographies are fetched from various sources, including PubMed, CrossRef, and publishers' publicly available information
from their Web sites.<o:p></o:p></p>
<p>An example of how the complete process looks can be found in the COD entry 1568124 [1-3]. There are over 11000 such bibliography update events recorded currently in the COD SVN logs.<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Do you have plans to automatically check for updated bibliographic information as it becomes available. If you do that is great! If not I would be happy to pass on any information
I am able to generate at our end. I am currently working on understanding the technical details.<o:p></o:p></p>
</blockquote>
<p>As said, we do check for the updated bibliographies and we update them when we find new data. Our process, however, is not perfect. The Web crawlers suffer from intense "bit rot" as the publishers' Web sites become more "modern". Our process might miss some
bibliographies, and in several cases, I have noticed, we got garbled data (like in the old record of 7131035, see [4-5]). Moreover, recently IURr complained that we are sending too many requests to their server's bibliography endpoint, so I had to stop fetching
IURr data temporarily, and this needs to be resolved.<o:p></o:p></p>
<p>Thus, if you have a process that would allow to complete the bibliographies or correct other metadata (and data :), we would be grateful for your contribution. COD is meant to be collaborative project, we we all pool information for our mutual benefit :).
We are ready to accept verified COD changes into the upstream, so that you do not need to re-apply your patches as you fetch a new COD revision.<o:p></o:p></p>
<p>Please let me know what your plans are if you are about to implement information fetches, let's discuss how can integrate our data.<o:p></o:p></p>
<p>Sincerely yours,<br>
Saulius<o:p></o:p></p>
<p>Refs.:<o:p></o:p></p>
<p>[1] Yu, Gang; Liu, Huanyu; Yan, Wenchao; Guo, Ruoyao; Wu, Aoben; Zhao, Zifeng; Liu, Zhiwei; Bian, Zuqiang. 4f → 3d sensitization: a luminescent Eu<sup>II</sup>-Mn<sup>II</sup> heteronuclear complex with a near-unity quantum yield. (2023) COD Entry 1568124.
URL: <a href="http://www.crystallography.net/cod/1568124.html">http://www.crystallography.net/cod/1568124.html</a> [accessed 2023-03-29T08:32+03:00].<o:p></o:p></p>
<p>[2] The COD Advisory Board. COD Entry 1568124, rev. 282108. Subversion record. URL: svn://www.crystallography.net/cod/cif/1/56/81/1568124.cif [accessed 2023-03-29T08:34+03:00].<o:p></o:p></p>
<p>[3] The COD Entry 1568124 bibliography change revision, difference log:<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="font-family:"Courier New"">saulius@tasmanijos-velnias ~/ $ svn log -c281623 --diff $(codid2file 1568124)<br>
------------------------------------------------------------------------<br>
r281623 | coder | 2023-03-04 20:51:18 +0200 (Sat, 04 Mar 2023) | 4 lines<br>
<br>
cif/<br>
Updating files of 1568124, 1568125, 1568126, 1568127<br>
Original log message:<br>
Adding full bibliography for 1568124--1568127.cif.<br>
<br>
Index: /home/saulius/struct/cod/current/cif/1/56/81/1568124.cif<br>
===================================================================<br>
--- /home/saulius/struct/cod/current/cif/1/56/81/1568124.cif (revision 281622)<br>
+++ /home/saulius/struct/cod/current/cif/1/56/81/1568124.cif (revision 281623)<br>
@@ -23,11 +23,16 @@<br>
'Bian, Zuqiang'<br>
_publ_section_title<br>
;<br>
- 4f <a href="file://rightarrow">\\rightarrow</a> 3d sensitization: a luminescent EuII--MnII heteronuclear<br>
- complex with a near-unity quantum yield<br>
+ 4f → 3d sensitization: a luminescent<br>
+ Eu<sup>II</sup>-Mn<sup>II</sup> heteronuclear complex with a near-unity<br>
+ quantum yield.<br>
;<br>
-_journal_name_full 'Materials Horizons'<br>
-_journal_paper_doi 10.1039/D2MH01123A<br>
+_journal_issue 2<br>
+_journal_name_full 'Materials horizons'<br>
+_journal_page_first 625<br>
+_journal_page_last 631<br>
+_journal_paper_doi 10.1039/d2mh01123a<br>
+_journal_volume 10<br>
_journal_year 2023<br>
_chemical_absolute_configuration ad<br>
_chemical_formula_sum 'C18 H36 Br2 Eu N2 O6'<br>
@@ -138,6 +143,8 @@<br>
_reflns_threshold_expression 'I > 2\s(I)'<br>
_cod_data_source_file d2mh01123a2.cif<br>
_cod_data_source_block 3<br>
+_cod_depositor_comments<br>
+'Adding full bibliography for 1568124--1568127.cif.'<br>
_cod_database_code 1568124<br>
_shelx_shelxl_version_number 2014/7<br>
_shelx_space_group_comment</span><o:p></o:p></p>
</blockquote>
<p>[4] The current 7131035 COD Entry (2023). URL: <a href="http://www.crystallography.net/cod/7131035.html">
http://www.crystallography.net/cod/7131035.html</a>; CIF URL: <a href="http://www.crystallography.net/cod/7131035.cif">
http://www.crystallography.net/cod/7131035.cif</a> [accessed 2023-03-29T08:45+03:00].<o:p></o:p></p>
<p>[5] The old 7131035 COD Entry with gabled author names (2022) CIF URL: <a href="http://www.crystallography.net/cod/7131035.cif@279571">
http://www.crystallography.net/cod/7131035.cif@279571</a> [accessed 2023-03-29T08:47+03:00].<o:p></o:p></p>
<pre>-- <o:p></o:p></pre>
<pre>Dr. Saulius Gražulis<o:p></o:p></pre>
<pre>Vilnius University, Life Science Center, Institute of Biotechnology<o:p></o:p></pre>
<pre>Saulėtekio al. 7, LT-10257 Vilnius, Lietuva (Lithuania)<o:p></o:p></pre>
<pre>phone (office): (+370-5)-2234353, mobile: (+370-684)-49802, (+370-614)-36366<o:p></o:p></pre>
<p class="MsoNormal"><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. <o:p></o:p></p>
</div>
</body>
</html>