search

linked-conservation-data / board-pilot-data

Processed datasets for the board reattachment pilot of the Linked Conservation Data project
1 stars 0 forks source link

E55 Type used for books #4

Closed natuk closed 3 years ago

natuk commented 3 years ago

We should use codices (bound manuscripts) from the AAT for typing books in the datasets and not the LoB entry codex-form books. In general we opt for AAT if the local dataset does not provide its own type, and then drop to LoB if AAT does not cover the term. Also the Stanford dataset seems not to include types for books, so these cannot be retrieved.

acampagnolo commented 3 years ago

Fixed

ryunleeuu commented 3 years ago

We don't capture this as an explicit data point in itself but rather only possibly in free text, so it won't be available as it is in the other datasets.

natuk commented 3 years ago

Can we add this retrospectively to the dataset? It could be a constant statement in 3M. It is not critical if not.

kristen-stjohn commented 3 years ago

Why would codex be a better choice than book? As far as I recall none or almost none of our pilot data are manuscripts.

ryunleeuu commented 3 years ago

I'm willing to add AAT for "books" or initial LoB for "codex-form books" since they'll suit our objects--will AAT for "books" shared by Kristen work?

natuk commented 3 years ago

Absolutely, I think this makes more sense. @acampagnolo can you also update the transformation for Bod and LoC?

ryunleeuu commented 3 years ago

fixed so all our objects have type http://vocab.getty.edu/aat/300028051

acampagnolo commented 3 years ago

changed to "books", but the link to the AAT is now on the vocabulary side and not in the RDFs

natuk commented 3 years ago

OK, so sul data have a direct link to AAT for book type whereas loc, bod and tna have an indirect link. I can create a union query to catch both cases.