[Esip-semanticharmonization] [EXT]SWEET terms derived from ENVO

[Kai Blumberg]

Hey again everyone just wanted to update you all that I've finished
collecting SWEET terms to map to the set of ENVO terms in our SSSOM mapping
table
<https://docs.google.com/spreadsheets/d/1MFxPjzD_fw64htkXyO-LNV3tiObGqdR82QAhZYXcf08/edit?usp=sharing>
doc, see the first sheet. Now it's a more concise list of 170 terms with
potential mappings between ENVO and SWEET terms. That is to say we now have
a smaller term set where the ENVO and SWEET IRIs are filled. However we
still need to review many of the mappings and assign the match type
predicates. Thanks again Chuck for making the SWEET to ENVO mapping (above
in this thread) I've also incorporated that in our table here.

Cheers,
Kai

On Thu, Apr 14, 2022 at 3:11 PM Kai Blumberg <kblumberg at email.arizona.edu>
wrote:

> Hey Charles and Brandon (as well as all everyone cc'd). I hope all is
> well. Here are some brief developments regarding the ENVO/SWEET
> harmonization work.
>
> Thanks again Charles for making your https://tinyurl.com/e4h4v76e SWEET
> to ENVO mapping table. We've finally incorporated all the scoped terms into
> ENVO, and now we're working on the reverse ENVO to SWEET mapping within
> this SSSOM mapping table
> <https://docs.google.com/spreadsheets/d/1MFxPjzD_fw64htkXyO-LNV3tiObGqdR82QAhZYXcf08/edit?usp=sharing>.
> We had some discussion yesterday about next steps for you guys the SWEET
> developers about potentially incorporating some of our mapping efforts on
> the ENVO side into SWEET.
>
> Our plan is to discuss the SSSOM mapping artifact for the manuscript
> <https://docs.google.com/document/d/16pK9ov6ygk5xlI0Luvl1tvCUfUonY6vsQJgZCgGY4UM/edit?usp=sharing>,
> however, it would be even better if material added to ENVO terms in the
> scope of this work were also incorporated into SWEET. It's totally up to
> you guys as the SWEET developers how you want to proceed, however, the idea
> was floated during yesterday's call that if terms that are candidates for
> SKOS:ExactMatches in SWEET take on the harmonized definitions that we've
> all been working on (that are now in ENVO), then we could more confidently
> assign such terms as exact matches.
>
> Sorry for getting a bit into the weeds but I feel it would be a great
> contribution to the work as well as SWEET to proceed at least to some
> extent as I've outlined above.
>
> Let us know if there might be interest in doing something like this,
> Thanks,
> Kai
>
>
> On Mon, Sep 27, 2021 at 1:49 PM Kai Blumberg <kblumberg at email.arizona.edu>
> wrote:
>
>> Great thanks Chuck when I get a chance I'll do the query the other way!
>> Once we've merged in the remaining ENVO pull request.
>>
>> Cheers,
>> Kai
>>
>> On Mon, Sep 20, 2021 at 5:43 PM Charles Vardeman <cvardema at nd.edu> wrote:
>>
>>> *External Email*
>>> Greeting Kai!!!
>>>
>>> Here is a link to the COR SPARQL query for any SWEET entity that has
>>> prov:wasDerivedFrom and a string matching an ENVO URI
>>> https://tinyurl.com/e4h4v76e
>>>
>>> I've attached the csv of the query output. I printed both the SWEET and
>>> ENVO URIs. There is a mismatch between entities with Ruth's ORCID (30
>>> entities) and entities with the wasDerivedFrom ENVO uri (32 entities), so I
>>> think that the wasDerivedFrom statement is the better way to extract the
>>> information.
>>>
>>> We should be able to figure out from this the missing references to ENVO
>>> entities from SWEET that have the DBXref in ENVO.
>>>
>>>
>>> Best,
>>> --Chuck
>>>
>>> --
>>> —————————————————
>>> Charles F. Vardeman II, Ph.D.
>>> Computational Scientist, Center for Research Computing
>>> Research Assistant Professor, Computer Science and Engineering
>>> University of Notre Dame
>>> PO BOX 539
>>> 911 Flanner Hall
>>> Notre Dame, IN 46556
>>> cvardema at nd.edu
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.esipfed.org/pipermail/esip-semanticharmonization/attachments/20220422/4dac5cbf/attachment.htm>