On Thu, Aug 29, 2013 at 6:46 AM, Arturo Vázquez <[email protected]>wrote:

> Couldn't you place the author name and surname fields in separate
> entries in your JSON files?


The schema could be changed to be more fine grained at the expense of
additional complexity for users, but you'd need more than two fields.
 You'd need at least surname, given name, title/prefix,
suffix/postnominals, and display order -- and that probably wouldn't deal
with matronymics/patronymics and other names which don't fall nicely into
the Anglo view of how things should work.

On Thu, Sep 12, 2013 at 9:10 AM, Karen Coyle <[email protected]> wrote:

>
> HOWEVER, any of the original data that came from libraries or from
> Amazon has a name with the surname first, then a comma, then the
> forename.


That's one of the one comma cases.  There are also a great variety of 2-4
comma cases such as:

2 - Haulleville, Prosper Charles Alexandre, Baron de
   Champagney, Frédéric Perrenot de Granvelle, seigneur de
   Champagney, Frédéric Perrenot de Granvelle, seigneur de

3 - Andlau, Marie Françoise Félicité (Mauguet de Mézières) du Crest,
marquise de Saint-Aubin, baronne d'
   Abrantès, Laure Junot, duchesses, d'
   Chamberlin, Mary Jane (Wilson), "Mrs. Alden Chamberlin,"

4 - Mant, Richard, Bp. of Down, Connor, and Dromore

It would make sense to me to store those names in the records
> even though that might not display on the web page. Your use is one
> possible one - more precise output. Also, the original names would match
> name forms in libraries and in the Virtual International Authority File,
> thus giving us more possibility of linking or providing links.


I think having the original name for provenance is good, but if it's a
hidden string that's not shown or updated by users, it's going to get
stale.  Citation applications (and others that think they know how names
are structured) would really need to have structured names in the database
to work properly.  It's not clear to me that the extra complexity is worth
it, but it's something to consider.

Tom
_______________________________________________
Ol-tech mailing list
[email protected]
http://mail.archive.org/cgi-bin/mailman/listinfo/ol-tech
To unsubscribe from this mailing list, send email to 
[email protected]

Reply via email to