<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=iso-8859-1">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New";}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:947392337;
mso-list-type:hybrid;
mso-list-template-ids:-969505240 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:72.0pt;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:108.0pt;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:144.0pt;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:180.0pt;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:216.0pt;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:252.0pt;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:288.0pt;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:324.0pt;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:360.0pt;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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 bgcolor="white" lang="DE" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">Dear Florian,
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">thank you for the extensive feedback also from my side.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">Davor already answered some of the issues.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">I would like to comment on the major issue of the hierarchical setup<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">This is indeed a very good point and there has been some great deal of discussion to this over the last years.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">This was (or still is) an issue also in the VLO itself – even though now the hierarchy is being represented meanwhile within the detail view, in the flat structure of the
facetted browser “all records sit next to each other”.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">As Davor said, this is nothing that can be solved easily/quickly,
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">but we (Davor) would raise the issue in Utrecht, to at least discuss the possibilities to solve it.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">Best,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">Matej<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></a></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="color:windowtext">From:</span></b><span lang="EN-US" style="color:windowtext"> Ostojic, Davor
<br>
<b>Sent:</b> Friday, April 29, 2016 12:21 PM<br>
<b>To:</b> Florian Schiel <schiel@phonetik.uni-muenchen.de>; Durco, Matej <Matej.Durco@oeaw.ac.at><br>
<b>Cc:</b> Draxler Christoph <draxler@phonetik.uni-muenchen.de>; Nina Pörner <nina.poerner@gmail.com><br>
<b>Subject:</b> RE: [Tf-curation] TF Curation - meeting in Utrecht<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Dear Florian,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Thank you for your feedback. We are trying to improve the application and we are really appreciate it.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Regarding minor things part of your email:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:4.8pt"><span lang="EN-US">>>The module report a missing facet 'rightsHolder' on instances of profile 'media-corpus-profile', but the profile (and the instances I tested) contains the element <Owner> which is linked to
concept <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:4.8pt">
<span lang="EN-US" style="color:#1F497D">>> </span><a href="http://hdl.handle.net/11459/CCR_C-2956_519a4aab-2f76-0fd3-090e-f0d6b81a7dbb"><span lang="EN-US">http://hdl.handle.net/11459/CCR_C-2956_519a4aab-2f76-0fd3-090e-f0d6b81a7dbb</span></a><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:4.8pt"><span lang="EN-US" style="color:#1F497D">Facet “rightsHolder” is currently mapped only to the following concepts:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level1 lfo2">
<![if !supportLists]><span lang="EN-US" style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-US"> </span><a href="http://www.isocat.org/datcat/DC-6709"><span lang="EN-US">http://www.isocat.org/datcat/DC-6709</span></a><span lang="EN-US" style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level1 lfo2">
<![if !supportLists]><span lang="EN-US" style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><a href="http://hdl.handle.net/11459/CCR_C-6709_cb3572ed-ffd3-04f1-c145-b9c1f26bfc82"><span lang="EN-US">http://hdl.handle.net/11459/CCR_C-6709_cb3572ed-ffd3-04f1-c145-b9c1f26bfc82</span></a><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level1 lfo2">
<![if !supportLists]><span lang="EN-US" style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><a href="http://purl.org/dc/terms/rightsHolder"><span lang="EN-US">http://purl.org/dc/terms/rightsHolder</span></a><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Mapping file used in production ca b fined at [1]. This file contains also descriptions for facet.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Perhaps we have to update this file with the concept “legalOwner”.</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><br>
>>In some CMDI instances the module reports broken links in the Resource section, for instance 37 in
</span><a href="https://clarin.phonetik.uni-muenchen.de/BASRepository/Public/Corpora/ALC/ALC.2.php?format=cmdi"><span lang="EN-US">https://clarin.phonetik.uni-muenchen.de/BASRepository/Public/Corpora/ALC/ALC.2.php?format=cmdi</span></a><span lang="EN-US"><br>
>>I checked all the URLs listed in this CMDI instance and they all are valid.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">I am aware of this problem. It happens due to the high concurrency. Response timeout is set to 5s but sometimes servers need more time.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">I will try to find a better way to do link validation.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Regarding major issues :<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">>>1. Since we encourage users to build redundant-free hierarchical MD structures in the CMD framework, would it be possible that the curator module follows hierarchies (if they are there) all the way to the top and add
the encountered >>MD to the MD content of the CMDI?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">I was not familiar with this case when I started with development but its sound like a crucial thing. I will create a new issues for the first (bottom up) case but I cannot say when I will have time
to implement it. <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><br>
<br>
>>2. What about the top-down way? When analysing a level 1 CMDI, this will contain no MD facets that are specific for the single resources, such as Date. Consequently the curator module should identify ResourceLinks of type 'Metadata', >>and add all the MD
of the linked level 2 CMDIs.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">This case I am afraid won’t be (and can’t be) supported. The web application is meant for curation of a single instance or profile. The library in the backend can validate collections or to work
in a batch mode. <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">>>One possible solution would be to recognize that a CMDI instance has ResourceLinks of type 'Metadata', and if so, treat it differently than CMDI instances that don't.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US" style="color:#1F497D">Could you explain this a bit better or do you have any concrete proposal?
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">In the future when you experience any problems with curation module you can create an issue by yourself at [2] or you can write to us directly.
</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Best,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Davor<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">[1] </span><a href="https://raw.githubusercontent.com/clarin-eric/VLO/master/vlo-commons/src/main/resources/facetConcepts.xml"><span lang="EN-US">https://raw.githubusercontent.com/clarin-eric/VLO/master/vlo-commons/src/main/resources/facetConcepts.xml</span></a><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">[2] </span><a href="https://github.com/clarin-eric/clarin-curation-module/issues"><span lang="EN-US">https://github.com/clarin-eric/clarin-curation-module/issues</span></a><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<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="color:windowtext">From:</span></b><span lang="EN-US" style="color:windowtext"> Florian Schiel [</span><a href="mailto:schiel@phonetik.uni-muenchen.de"><span lang="EN-US">mailto:schiel@phonetik.uni-muenchen.de</span></a><span lang="EN-US" style="color:windowtext">]
<br>
<b>Sent:</b> Friday, April 29, 2016 9:09 AM<br>
<b>To:</b> Durco, Matej <</span><a href="mailto:Matej.Durco@oeaw.ac.at"><span lang="EN-US">Matej.Durco@oeaw.ac.at</span></a><span lang="EN-US" style="color:windowtext">><br>
<b>Cc:</b> Ostojic, Davor <</span><a href="mailto:Davor.Ostojic@oeaw.ac.at"><span lang="EN-US">Davor.Ostojic@oeaw.ac.at</span></a><span lang="EN-US" style="color:windowtext">>; Draxler Christoph <</span><a href="mailto:draxler@phonetik.uni-muenchen.de"><span lang="EN-US">draxler@phonetik.uni-muenchen.de</span></a><span lang="EN-US" style="color:windowtext">>;
Nina Pörner <</span><a href="mailto:nina.poerner@gmail.com"><span lang="EN-US">nina.poerner@gmail.com</span></a><span lang="EN-US" style="color:windowtext">><br>
<b>Subject:</b> Re: [Tf-curation] TF Curation - meeting in Utrecht<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><br>
Dear Matej, dear Davor,<br>
<br>
I tested the curation module interface with different instances and profiles. It works very well!<br>
<br>
But when testing CMDI instances nested in a hierarchy I encountered the following (conceptional?) problem:<br>
Each CMDI instance is tested by the module in isolation. Why is this a problem?<br>
<br>
Consider for example a 2-level hierarchy of metadata: on the first level (corpus level) the metadata of a complete collection of resources is stored as in [1]; on the second level (that is linked as resources of type 'Metadata') in the first level) the metadata
of a single resource is stored as in [2]. To avoid massive replication, MD that concern all members of the collection are only stored in the first level, for example availabilty.<br>
When analysing a single CMD instance of the second level, we can't find this information in the CMDI. But what we find is a pointer to the upper level, namely the IsPartOf entry in the CMDI header.<br>
<br>
So, I guess my questions are:<br>
<br>
1. Since we encourage users to build redundant-free hierarchical MD structures in the CMD framework, would it be possible that the curator module follows hierarchies (if they are there) all the way to the top and add the encountered MD to the MD content of
the CMDI?<br>
<br>
2. What about the top-down way? When analysing a level 1 CMDI, this will contain no MD facets that are specific for the single resources, such as Date. Consequently the curator module should identify ResourceLinks of type 'Metadata', and add all the MD of the
linked level 2 CMDIs.<br>
This may in principle the right thing to do, but in reality it is of course not feasible, since some collections contain millions of resources.<br>
One possible solution would be to recognize that a CMDI instance has ResourceLinks of type 'Metadata', and if so, treat it differently than CMDI instances that don't.<br>
<br>
I hope I made myself clear. If not, don't hesitate to ask back.<br>
<br>
--------------<br>
<br>
Some minor things I noticed:<br>
<br>
The module report a missing facet 'rightsHolder' on instances of profile 'media-corpus-profile', but the profile (and the instances I tested) contains the element <Owner> which is linked to concept
</span><a href="http://hdl.handle.net/11459/CCR_C-2956_519a4aab-2f76-0fd3-090e-f0d6b81a7dbb"><span lang="EN-US">http://hdl.handle.net/11459/CCR_C-2956_519a4aab-2f76-0fd3-090e-f0d6b81a7dbb</span></a><span lang="EN-US"><br>
<br>
In some CMDI instances the module reports broken links in the Resource section, for instance 37 in
<br>
</span><a href="https://clarin.phonetik.uni-muenchen.de/BASRepository/Public/Corpora/ALC/ALC.2.php?format=cmdi"><span lang="EN-US">https://clarin.phonetik.uni-muenchen.de/BASRepository/Public/Corpora/ALC/ALC.2.php?format=cmdi</span></a><span lang="EN-US"><br>
I checked all the URLs listed in this CMDI instance and they all are valid.<br>
<br>
Finally, it would be very useful for the maintainer to have a list of facet definitions, for instance I couldn't figure out what exactly is 'distributionType' and to which concept is this facet linked?<br>
<br>
<br>
Best regards, <br>
<br>
Florian<br>
<br>
<br>
[1] </span><a href="https://clarin.phonetik.uni-muenchen.de/BASRepository/Public/Corpora/ALC/ALC.2.php?format=cmdi"><span lang="EN-US">https://clarin.phonetik.uni-muenchen.de/BASRepository/Public/Corpora/ALC/ALC.2.php?format=cmdi</span></a><span lang="EN-US"><br>
[2] </span><a href="https://clarin.phonetik.uni-muenchen.de/BASRepository/Public/Corpora/ALC/ses1009.2.cmdi.xml"><span lang="EN-US">https://clarin.phonetik.uni-muenchen.de/BASRepository/Public/Corpora/ALC/ses1009.2.cmdi.xml</span></a><span lang="EN-US" style="font-size:12.0pt"><o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US"><br>
<br>
<br>
On 28.04.2016 15:27, Durco, Matej wrote:<o:p></o:p></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Dear Florian, </span>
<span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">thanks! </span><span lang="EN-US" style="font-family:Wingdings;color:#1F497D">J</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">that would be either me, or my colleague
</span><a href="mailto:davor.ostojic@oeaw.ac.at"><span lang="EN-US">davor.ostojic@oeaw.ac.at</span></a><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Best,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Matej<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="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="color:windowtext">From:</span></b><span lang="EN-US" style="color:windowtext"> Florian Schiel [</span><a href="mailto:schiel@phonetik.uni-muenchen.de"><span lang="EN-US">mailto:schiel@phonetik.uni-muenchen.de</span></a><span lang="EN-US" style="color:windowtext">]
<br>
<b>Sent:</b> Thursday, April 28, 2016 2:29 PM<br>
<b>To:</b> Durco, Matej </span><a href="mailto:Matej.Durco@oeaw.ac.at"><span lang="EN-US"><Matej.Durco@oeaw.ac.at></span></a><span lang="EN-US" style="color:windowtext"><br>
<b>Subject:</b> Re: [Tf-curation] TF Curation - meeting in Utrecht</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US">Dear Matej,<br>
<br>
this is very useful. Thank you for that!<br>
Since I cannot be at the meeting, to whom (or which address) I can send (constructive) feedback about the curation module?<br>
<br>
Best,<br>
<br>
Florian<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">On 28.04.2016 10:57, Durco, Matej wrote:<o:p></o:p></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span lang="EN-US">Dear all, <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">During the CLARIN Centre meeting in Utrecht, there is space on the 11 May afternoon for TF meetings.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">We would like to take this opportunity to meet with you (the curation taskforce), to report about the recent developments and discuss possible further steps.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Could you please indicate who of you will be there and could join the meeting?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">(It would be either 13:30-15:00 or 15:00/30 – 17:00, depending on coordination with other TFs, especially CMDI)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Meanwhile, you can already have a look at the main progress achieved.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">A first version of the curation module has been delivered by my colleague Davor Ostojic, as task within CLARIN-PLUS project.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">It is described in clarin-trac [1]<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">And there is also a simple web-application to try out:<o:p></o:p></span></p>
<p class="MsoNormal"><a href="https://clarin.oeaw.ac.at/curate/"><span lang="EN-US">https://clarin.oeaw.ac.at/curate/</span></a><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Looking forward to any comments/feedback.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Thank you <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Best,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Matej<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">[1] </span><a href="https://trac.clarin.eu/wiki/Curation%20Module"><span lang="EN-US">https://trac.clarin.eu/wiki/Curation%20Module</span></a><span lang="EN-US"><o:p></o:p></span></p>
</blockquote>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
</blockquote>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
</div>
</div>
</body>
</html>