Skip to content

Series of wrong matches across different graphs #43

@fjjulien

Description

@fjjulien

Main issue

Gary and detected unexpected events in the upcoming events organized by indigenous agents graph JSON-LD.

The source includes several events from the P'tit bonheur dataset (kg.artsdata.ca/culture-creates/footlight/ptitbonheur-org). The reason these events are selected in the dataset is an inaccurate sameAs. Events in this dataset have two organizer value:

Solution

Secondary issue

The incorrect organizer value was likely entered as a result of a bad string reconciliation in Footlight console. This bad reconciliation string was itself probably the outcome of an ambiguous data record.

There is a resource named "Camille" (http://lod.footlight.io/resource/665825428c76ef006456521d) that has a few questionable sameAs triples:

Image

Among other things, one of the values is http://kg.artsdata.ca/resource/K2-279, a URI that is no longer accessible in the Artsdata database.

Another value is an IPAA member record (https://ipaa.ca/resource/e0f6c625-9149-468c-b1b5-f0c866f2f767) that also appears to be a broken link.

Solutions

###Tertiary issue

The data record that appears to be the source of this confusion is https://ipaa.ca/profile/indigenous-organization/Camille_Usher#Organization. This member profile is clearly describing the Indigenous Curatorial Collective, but it is named "Camille Usher" (after the name of the person who filled in the form). I suspect this new name might have been attributed after the organization changed its name from "Aboriginal Curatorial Collective" to "Indigenous Curatorial Collective".

Solutions

I'm not sure...

  • At a minimum, the name value in the IPAA database should be changed for that of the organization, rather than Camille.

Changing the IPAA record URL slug is also an option. This would create a new entity URI in Artsdata, which @GaryMan1968 could then manually mint/link to its Artsdata ID.

Or else, we could leave the URL as is and accept the ambiguity of the URI name.

@saumier Any thoughts?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions