talk@lists.collectionspace.org

WE HAVE SUNSET THIS LISTSERV - Join us at collectionspace@lyrasislists.org

View all threads

Best practices for reconciling data

NS
Nate Solas
Fri, Mar 30, 2012 6:55 PM

The Walker has a copy of the Getty vocabs, and I've been working to map our
artist names to ULAN. This is valuable on its face since we can get the
correct names and spellings for people in our database, but it becomes
really exciting when we can reconcile these names to actual URIs and link
up the data. Assuming I'm able to connect those dots (ULAN, DBPedia, etc),
is there a "best practice" for storing this information with our Person
records? I know this is probably out of scope at the moment, but... it's
where I want to be eventually so I thought I'd ask.

Nate

The Walker has a copy of the Getty vocabs, and I've been working to map our artist names to ULAN. This is valuable on its face since we can get the correct names and spellings for people in our database, but it becomes really exciting when we can reconcile these names to actual URIs and link up the data. Assuming I'm able to connect those dots (ULAN, DBPedia, etc), is there a "best practice" for storing this information with our Person records? I know this is probably out of scope at the moment, but... it's where I want to be eventually so I thought I'd ask. Nate
JD
John Deck
Fri, Mar 30, 2012 8:15 PM

A couple of ideas:

  1. store the URI in its own field and not mix with literals.  Thus, you
    would have distinct fields:

Person="John Doe"
PersonURI=http://bigpersondb/john+doe

  1. Use a known namespace for PersonURI (foaf??)

John Deck

On Fri, Mar 30, 2012 at 2:55 PM, Nate Solas nate.solas@walkerart.orgwrote:

The Walker has a copy of the Getty vocabs, and I've been working to map
our artist names to ULAN. This is valuable on its face since we can get the
correct names and spellings for people in our database, but it becomes
really exciting when we can reconcile these names to actual URIs and link
up the data. Assuming I'm able to connect those dots (ULAN, DBPedia, etc),
is there a "best practice" for storing this information with our Person
records? I know this is probably out of scope at the moment, but... it's
where I want to be eventually so I thought I'd ask.

Nate


Talk mailing list
Talk@lists.collectionspace.org

http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

--
John Deck
(541) 321-0689

A couple of ideas: 1. store the URI in its own field and not mix with literals. Thus, you would have distinct fields: Person="John Doe" PersonURI=<http://bigpersondb/john+doe> 2. Use a known namespace for PersonURI (foaf??) John Deck On Fri, Mar 30, 2012 at 2:55 PM, Nate Solas <nate.solas@walkerart.org>wrote: > The Walker has a copy of the Getty vocabs, and I've been working to map > our artist names to ULAN. This is valuable on its face since we can get the > correct names and spellings for people in our database, but it becomes > really exciting when we can reconcile these names to actual URIs and link > up the data. Assuming I'm able to connect those dots (ULAN, DBPedia, etc), > is there a "best practice" for storing this information with our Person > records? I know this is probably out of scope at the moment, but... it's > where I want to be eventually so I thought I'd ask. > > Nate > > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > > -- John Deck (541) 321-0689