LD4P / qa_server

A rails engine with questioning authority gem installed to serve as an authority search server with normalized results.
Apache License 2.0
6 stars 3 forks source link

Cannot use QA to find a known value in LC NAF even when parenthesis removed #257

Open CECSpecialistI opened 4 years ago

CECSpecialistI commented 4 years ago

Searching for known value "Verne, Jules, 1828-1905. Tour du monde en quatre-vingts jours. English (Butcher)" does not find expected result associated with URI: http://id.loc.gov/authorities/names/no2019176268 Tried searching exact string above, and: "Verne, Jules, 1828-1905. Around the world in eighty days" "Verne, Jules, 1828-1905. Tour du monde en quatre-vingts jours. English Butcher"
"Verne, Jules, 1828-1905. Tour du monde en quatre-vingts jours. English"

A similar title, "Verne, Jules, 1828-1905. Tour du monde en quatre-vingts jours. English (Legend Press Ltd)", comes up easily with the English variant and with the string omitting the translator's name "Butcher". Not sure what the difference is between these two values that would make one come up and not the other. image image

sfolsom commented 4 years ago

Hi Crystal, I'm glad you're asking about name titles. We've been considering just removing them altogether. Related, we hadn't added the name titles as subauthority because folks at the Library of Congress suggested we focus on linking to bf:Works instead. So instead of http://id.loc.gov/authorities/names/no2019176268, they are suggesting http://id.loc.gov/resources/works/789309. Would adding LC Works meet your need (assuming we can fix the (Butcher) problem? See: https://github.com/LD4P/qa_server/issues/198. If you really want the Name Title entities, we can fix this index and add the subauth.

sfolsom commented 4 years ago

I took a look at your profile, and that field as it stands now seems to be saying the your rda:Expression is a skos:exactMatch with the LCNAF skos:Concept, meaning that the rda:Expression is also a skos:Concept. See: https://www.w3.org/TR/skos-reference/#L4858. I'm not advocating for the use of owl:sameAs, but you might want to consider something other than skos:exactMatch (e.g. rdfs:seeAlso, madsrdf:isIdentifiedByAuthority, schema:sameAs) if you're going to link from a thing to a skos:Concept. If linking from an rda:Expression to a bf:Work (expression), maybe rdfs:seeAlso, schema:samesAs, or maybe maybe owl:sameAs if you really are confident that they are the same thing.

CECSpecialistI commented 4 years ago

Thanks @sfolsom! We'll talk about the property we used to link rda:Expression to LCNAF name/titles today and probably change it to schema:sameAs or owl:sameAs. We made that decision quickly and I can't remember why we chose skos:exactMatch in the first place.

Adding LC Works rather than name titles as lookups in our profiles would make things tricky, since LC is using BIBFRAME works and we are using RDA works, and they are not the same thing (although they do overlap). I'm not sure what LC is doing with hubs, whether those are now the equivalent of a FRBR work and bf:Work is going to be more equivalent to just FRBR expressions going forward, but as it stands right now, the LC works don't suit our needs because the data modeling makes it unclear whether they are RDA Works or Expressions.