search

hbz / lobid

Linking Open Bibliographic Data
https://lobid.org/
Eclipse Public License 2.0
15 stars 4 forks source link

Remove birthDate from creator and contributor. #244

Closed jschnasse closed 8 years ago

jschnasse commented 8 years ago

I'd suggest to remove the comma separated birth date from preferredName of gnd-authorities. It would be much better to have the birthdate in an extra triple like provided by dnb.

http://d-nb.info/gnd/134268857 http://d-nb.info/standards/elementset/gnd#preferredName "..., 1953-"^^http://www.w3.org/2001/XMLSchema#string .

Example: http://lobid.org/resource/HT018728844/about

acka47 commented 8 years ago

We will do this. We chose this form as we thought that it would look like this in the Aleph OPAC but it doesn't.

@dr0i I guess we build the strings the same way for subjects and creators/contributors. Obviously, we have to change this as we don't want the birth/death year removed from the subject labels. See https://github.com/hbz/lobid/issues/145.

jschnasse commented 8 years ago

We were told that it looks kind of rude to present the birth date of all ladies and gentlemen to everyone. We chose to present it only to the library staff (useful for individualisation) but not to the end user. Thank you for solving this!

dr0i commented 8 years ago

Cheez. Note: we assume that rudeness is kinda relative: if you would be a subject of something (and not a contributor or creator), we leave the Lebensdaten in the data, see e.g. http://lobid.org/resource/HT015891797. Same goes true for subject chains.

dr0i commented 8 years ago

Deployed to staging.

acka47 commented 8 years ago

+1

jschnasse commented 8 years ago

+1

dr0i commented 8 years ago

Deployed to production, closing.

dr0i commented 8 years ago

We were told that it looks kind of rude to present the birth date of all ladies and gentlemen to everyone

This should have give me the hint - it's about presenting , not so much about the underlying data. This should be an issue of the frontend, especially when considering the ridiculously amount of work and implementation of logik when doing e.g. lobid/lodmill#742. This is not KIS.

jschnasse commented 8 years ago

I think it is better to not include birth dates into 'preferredName'. I think also that it was a mistake to do so in first run. There are potentially many front ends but only one lobid. One work hour at lobid saves n*work hours at the clients.

dr0i commented 8 years ago

Maybe , maybe not. E.g. you may miss birth dates when facetting. Point is, the data is in part concatenated , see e.g. lobid/lodmill#742, doing frontends job. Would be better to have multiple fields (like you said at the beginning of the ticket) and let the frontends doing whatever they want.