< Back | Home | Edit page | 🙋 Check for open issues |

Artsdata Guidelines for location Values

Good practices regarding place granularity

When a building contains multiple performance halls, Artsdata can run into reconciliation issues if the structured data describes the building rather than the performance hall. It may look like two performances are happening at the same time and in the same place, whereas these are, in fact, two different places.

Here is the logic followed by Artsdata’s auto-minting process:

• If two events are in the same Place; AND
• Their startTime is within a one hour difference; THEN
• Mark the two events as ado:PotentialDuplicate AND do not auto-mint.

Recommendations

As per Artsdata’s instructions, it is preferable to be as precise as possible when entering a location nested entity under an @type Event. In other words, it is better to enter the name and sameAs values for the performance hall where the event is taking place rather than for the building as a whole.

However, an organization may prefer to enter the name of the building in their structured data – particularly if the building name is more well-known than the performance hall name, or if the performance hall shares its name with another hall in a different building.

In these instances, there are four potential solutions:

1. Enter different name and sameAs values

Enter the building name under location name, but add a sameAs pointing to a URI describing the performance hall. This way, the building name will be treated as the primary location label. However, machines will still be able to recognize that the physical location is the performance hall contained within the building rather than the building itself. Example:

"location":
         {
            "@type":"Place",
            "name":"Centre des arts Juliette-Lassonde",
            "sameAs":[
               "http://kg.artsdata.ca/resource/K2-227",
               "http://www.wikidata.org/entity/Q111668872"],
            "address":{
               "@type":"PostalAddress",
               "addressLocality":"Saint-Hyacinthe",
               "addressRegion":"QC",
               "postalCode":"J2S 9E2",
               "streetAddress":"1705 Rue Saint-Antoine",
               "addressCountry":"CA"
            }
    },

Note that the Artsdata and Wikidata URIs under sameAs point to the Salle Desjardins performance hall inside Centre des arts Juliette-Lassonde.

2. Enter a separator between the building and performance hall under name

Enter both the building and performance hall name under name, divided by a separator (e.g. an en-dash or vertical bar). You may choose to add whichever location name first, depending on which you would prefer to show up in its entirety (keeping in mind that only the first 60 characters may be displayed in search results). Example:

"location":
         {
            "@type":"Place",
            "name":"Salle Desjardins – Centre des arts Juliette-Lassonde",
            "sameAs":[
               "http://kg.artsdata.ca/resource/K2-227",
               "http://www.wikidata.org/entity/Q111668872"],
            "address":{
               "@type":"PostalAddress",
               "addressLocality":"Saint-Hyacinthe",
               "addressRegion":"QC",
               "postalCode":"J2S 9E2",
               "streetAddress":"1705 Rue Saint-Antoine",
               "addressCountry":"CA"
            }
    },

Note that the Artsdata and Wikidata URIs under sameAs point to the Salle Desjardins performance hall inside Centre des arts Juliette-Lassonde.

3. Add a nested entity under containedInPlace

Enter the performance hall name under location name. Add a containedInPlace nested entity with the building name under name and sameAsvalue pointing to a URI describing the building. This way, machines will be able to recognize that the performance hall is a part of the building rather than a separate location. Example:

 "location":
         {
            "@type":"Place",
            "name":"Salle Desjardins",
            "sameAs":[
               "http://kg.artsdata.ca/resource/K2-227",
               "http://www.wikidata.org/entity/Q111668872"],
            "address":{
               "@type":"PostalAddress",
               "addressLocality":"Saint-Hyacinthe",
               "addressRegion":"QC",
               "postalCode":"J2S 9E2",
               "streetAddress":"1705 Rue Saint-Antoine",
               "addressCountry":"CA"
            },
            "containedInPlace":{
               "@type":"Place",
               "name":"Centre des arts Juliette-Lassonde",
               "sameAs":"http://kg.artsdata.ca/resource/K5-796"
            }
    },

Note that because the performance hall and building share the same address, it is not necessary to repeat the address nested entity within containedInPlace.

4. Add an alternameName value

For semantic reasons, this strategy is not recommended by the Artsdata team. However, you may still to choose to add it to your structured data if the other options do not fit your current needs.

Enter the performance hall under location name and add the building name under alternateName, or vice versa, depending on which you would prefer to use as the primary location label. Example:

"location":
         {
            "@type":"Place",
            "name":"Salle Desjardins",
            "alternateName":"Centre des arts Juliette-Lassonde",
            "sameAs":[
               "http://kg.artsdata.ca/resource/K2-227",
               "http://www.wikidata.org/entity/Q111668872"],
            "address":{
               "@type":"PostalAddress",
               "addressLocality":"Saint-Hyacinthe",
               "addressRegion":"QC",
               "postalCode":"J2S 9E2",
               "streetAddress":"1705 Rue Saint-Antoine",
               "addressCountry":"CA"
            }
    },

Note that the Artsdata and Wikidata URIs under sameAs point to the Salle Desjardins performance hall inside Centre des arts Juliette-Lassonde.

Good practices regarding location sameAs

• Artsdata guidelines about the schema:sameAs property
  • How to retrieve persistent identifiers’ URIs