Open denisnazarov opened 7 years ago
Two mechanisms supported at the lowest level:
@denisnazarov the case you're describing goes like this:
Let me give you a simple example of merging based on ukiyo-e. For example, this image:
http://www.mfa.org/collections/object/226444
gets a WKI of mfa:226444
, while this one:
gets mia:2006
. For simplicity, let's say that the prefixes and namespaces are the same. Then in the ukiyoe
namespace, you have a statement w/o a body but with wki refs of mfa:226444, mia:2006
, which says that from this perspective, these items constitute a single entity. Does that make sense?
Yep makes total sense. I think the artist example is more exciting because it would let you find artworks in a different collection (picassos in tate) using an artist id in yours (picasso in moma).
Is this something we can illustrate with a query with what we have built today? If so would be great to get an example so I can include that in the tutorial/vid.
@denisnazarov yeah, I used this example for clarity, the artist case is equivalent. This kind of join is not supported yet, tho
How does one use refs to other objects?
Example: https://github.com/MuseumofModernArt/collection has an Artists.json and Artworks.json. Artworks reference objects in Artists via an array of
ConstituentID
:I want to include a reference to the Artist object via the statement's refs array:
museums.moma.artwork
andmuseums.moma.artist
)?Other, probably not solved via refs:
museums.moma.artist
(museum 1) represents the same person/entity inmuseums.tate.artist
(museum 2) (example)?