Quoting roles in data services

[Anne Catherine Raugh]

I'm one of those people who sits and watches movie credits - especially if
I want to find out who did the music. SAG and AFTRA have had a long time to
figure this problem out in their context, and most people a familiar with
the result. The director, the producer, and the stars get "billing",
everyone else gets something else that, if there's someone like me
interested in a particular point, will wait to see and will appreciate
having.

I am reminded of a quote from Kermit the Frog  during the credits for one
Muppet movie, in which he was riding in a hot air balloon with Fozzy Bear.
They watched the scroll, and FOzzy asked sadly, "Do you think anyone ever
reads these credits?"

To which Kermit chirpily replied: "Sure! They all have families!"

I had a point....oh, yes. So I would be happy to include many roles that
are never considered for "citation" credit because that relationship is
special in research literature and I really don't want to dilute it. But I
would like to get the contributor metadata into the record so that those
who are looking for it can find it and brag about it.

The DataCite Contributor Role standard value list is a Tall Pole problem
for DataCite, however, so tread carefully.

-Anne.


On Mon, Feb 3, 2025 at 8:36 AM Henneken, Edwin via semantics <
semantics at ivoa.net> wrote:

> Dear all
>
> This is a challenge that is very much on our (i.e. the Astrophysics Data
> System) radar as well. For one, we need to consider whether we need to
> update our metadata model to include the same distinction between different
> types of authors/contributors that the DataCite metadata model has.
> Updating the metadata model and capturing the associated metadata is
> probably the easy part. Integrating the distinction between different types
> of authors in our API/UI is definitely more work, but a solvable problem
> too. Attribution can be the hardest part, depending how you want to weigh
> citations. Does a curator get the same level of attribution as, say, the
> creator? This is particularly true when you look at derived metrics like
> normalized citations and citation-based indicators.
>
> Best wishes,
> Edwin
>
> *Edwin Henneken *(he | him | his)
>
> Astrophysics Data System / Science Explorer
>
> Center for Astrophysics | Harvard & Smithsonian
>
> 60 Garden Street | MS 83 | Cambridge, MA 02138
>
>
> ads.harvard.edu | @adsabs <https://twitter.com/adsabs> | *ui.adsabs.harvard.edu
> <https://ui.adsabs.harvard.edu/>*
>
> *cfa.harvard.edu <https://cfa.harvard.edu/>* | Facebook
> <http://cfa.harvard.edu/facebook> | Twitter
> <http://cfa.harvard.edu/twitter> | YouTube
> <http://cfa.harvard.edu/youtube> | Newsletter
> <http://cfa.harvard.edu/newsletter>
>
>
> On Mon, Feb 3, 2025 at 7:20 AM Baptiste Cecconi via semantics <
> semantics at ivoa.net> wrote:
>
>> Hi Stéphane,
>>
>> indeed, this is a bit of a tricky issue, since accurately acknowledging
>> attribution or authorship is a key aspect of science ethics.
>>
>> My first answer is to clearly identify what contribution is attributed to
>> whom. I mean: the EPNcore or ObsCore table metadata should be very explicit
>> on what it is, and how to has been produced. The title and description has
>> to be very clear on the content and the scope.
>>
>> With your example:
>> The EPNTAP service is a "Curated catalogue of planetary observations by
>> HST". The EPNcore metadata has been produced by Erard, et al. The original
>> datasets used to produce the metadata are provided by the NASA/MAST
>> database (or any other that has been used).
>>
>> The metadata in the Registry concerns the catalog metadata, and should
>> (must?) contain reference to the progenitor data if required, e.g., with
>> relation like "is-metadata-for" linking to the DOI (or any identifier) of
>> the original dataset (possibly included as a provenance statement)
>>
>> So to me:
>> - the metadata of the EPNcore/Obscore table should relate to the metadata
>> and not the original data,
>> - the relation to the source data should be explicitly stated and
>> presented, both on the service description, as well as in the registry
>> metadata.
>> - the EPNcore/Obscore table landing page should propose explicit citation
>> policies ("how to cite this metadata", "how to cite the underlying
>> datasets")
>>
>> Cheers
>> Baptiste
>>
>>
>>
>>
>> Le 2 févr. 2025 à 11:01, Stéphane Erard via semantics <semantics at ivoa.net>
>> a écrit :
>>
>> Hello
>>
>>
>> I'm reviving an old request from the Solar System community but more
>> general in scope:
>> What are the common practices concerning references to data services?
>> How do we cite creators of content (ie: data) vs services (ie, very
>> often: a metadata table)? Can there be 2 different roles? - this is a
>> recurring request from our providers, and a sensitive one.
>> Example: I'm maintaining an EPN-TAP service identifying planetary data
>> from the HST catalog. Creating the metadata table is a significant work
>> which deserves identification and involves a responsibility; but I can't
>> pretend I've created the data. How do I call my role there?
>>
>> VESPA distinguishes 3 roles, following current practices: Creator,
>> Contributor, Publisher
>> But there is an obvious ambiguity with Creator that needs to be addressed.
>>
>> Cheers
>> Stéphane
>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/semantics/attachments/20250203/573a0743/attachment.htm>