<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-forward-container">Dear Markus,
<div class="moz-forward-container">
<p>Thank you for your literary proposal - the use case sounds
more friendly - <br>
</p>
<p>Some comments on your use case (a) - What do you mean with
contact information ? to add email? <br>
email management is not easy - but authors/producer name, may
be affiliation and especially ORCID could help users to
contact the persons.</p>
<p> I agree that "contact information" should be an option. In
fact, I suggest to ban MUST for each "origin" metadata - their
implementation depends of the richness contents of the data
providers.</p>
<p><br>
</p>
<p>I like your idea of a gathertown in next interop: we can plan
one.</p>
<p>Regards,<br>
</p>
<p>Gilles<br>
</p>
<p><br>
</p>
<br>
-------- Message transféré --------
<table class="moz-email-headers-table" cellspacing="0"
cellpadding="0" border="0">
<tbody>
<tr>
<th valign="BASELINE" nowrap="nowrap" align="RIGHT">Sujet :
</th>
<td>Re: Data origin in the Virtual Observatory</td>
</tr>
<tr>
<th valign="BASELINE" nowrap="nowrap" align="RIGHT">Date :
</th>
<td>Thu, 1 Sep 2022 09:13:15 +0200</td>
</tr>
<tr>
<th valign="BASELINE" nowrap="nowrap" align="RIGHT">De : </th>
<td>Markus Demleitner <a class="moz-txt-link-rfc2396E"
href="mailto:msdemlei@ari.uni-heidelberg.de"
moz-do-not-send="true"><msdemlei@ari.uni-heidelberg.de></a></td>
</tr>
<tr>
<th valign="BASELINE" nowrap="nowrap" align="RIGHT">Pour :
</th>
<td><a class="moz-txt-link-abbreviated
moz-txt-link-freetext" href="mailto:datacp@ivoa.net"
moz-do-not-send="true">datacp@ivoa.net</a></td>
</tr>
</tbody>
</table>
<br>
<br>
Dear Gilles, dear Gus,<br>
<br>
On Wed, Aug 31, 2022 at 06:01:47PM +0200, gilles landais wrote:<br>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">In order to improve the traceability and the citation of the resources
consumed in the VO network, we propose to make more visible the data origin
in the VO.
We mean by Data Origin the basic provenance like authors, institutes, DOI,
references, …
</pre>
</blockquote>
<br>
Thanks for taking this action! Count me in on helping out on it.<br>
What about a side meeting on this in the next Interop's
gathertown?<br>
<br>
A few early comments on your use cases:<br>
<br>
(a) on the "get basic provenance" and "trace data origin": I
always<br>
like it better if a use case actually tells a story that is
outside<br>
of the thing itself. In this case: "What do I do with that basic<br>
provenance?" I'd hence say the first could be something like:<br>
<br>
* A researcher has data in a VOTable that shows an odd feature.
They<br>
would now like to talk to the creator of the data to help figure<br>
out whether that feature is physics or an artefact.
[Requirement:<br>
contact information to producers present; but then let's not
make<br>
that a MUST: This can be GDPR-relevant data, and it must be<br>
possible to leave it out if it is]<br>
<br>
* A researcher revisits work they did six months earlier in an
ad-hoc<br>
fashion and would now like to reproduce it in a more structured<br>
fashion. Do do that, they need to know, say, which queries
against<br>
which services, or perhaps which programs, produced the files.<br>
[Requirement: have the request parameters and a service<br>
identification (access url? ivoid?) in the data origin]<br>
<br>
(b) The "final users to cite" and "bibliography of everything"
(and<br>
perhaps even "AAS citation template" use cases imply, I think,<br>
roughly the same requirements. I'd hence merge them to something<br>
like:<br>
<br>
* While preparing a publication, a researcher would like to
properly<br>
cite the software and data that went into their results. They
now<br>
run a program to extract that information from the digital
artefacts<br>
going into the publication -- perhaps even in separate parts of<br>
citations and acknowledgements. [Requirement: The data origin
must<br>
indicate requests for citation and/or acknowledgement in a<br>
machine-readable way, preferably in a way that machines can<br>
generate BibTeX for whatever they specify]<br>
<br>
Thanks,<br>
<br>
Markus<br>
</div>
</div>
</body>
</html>