On 28 March 2012 14:18, Ross Singer <[email protected]> wrote:
> On Mar 27, 2012, at 4:06 PM, Ben Companjen wrote:
>
>> On 27 March 2012 18:05, Karen Coyle <[email protected]> wrote:
>>> On 3/27/12 3:08 PM, Ben Companjen wrote:
>>>
>>>> - we want to keep the distinction between foaf:Person and other
>>>> entities, so changing the author template to use foaf:Agent (because
>>>> we cannot tell the difference at the moment) is not accepted.
>>>> I created issue 145 [1] to 'standardize' the values for entity_type
>>>> found in author records. Using its value ("person" for humans and
>>>> pseudonyms, "org" for organization) or its absence, we can choose
>>>> foaf:Person, foaf:Organization or foaf:Agent.
>>>
>>> I wonder if some of this cannot be done using a comparison to VIAF --
>>> because in VIAF there should be coding to indicate whether it is a
>>> person or a corporation. Also, some of this information could be
>>> recovered from the original input records. We could use the MARC coding
>>> from library data, and any unmatched strings from other sources like
>>> Amazon could be designated "Agent" until a match is found from a source
>>> that makes the distinction.
>>
>> I think it must be possible, but first I think we should have a way of
>> storing the information. We can use VIAF if the license terms allow
>> us; Tom Morris pointed out on GitHub that it may be for non-commercial
>> use only. The PD/CC0 MARC records are available anyway, so surely they
>> can be re-read to extract the information.
>>
>
> Hi Ben,
>
> Which MARC records are you referring to here?
>
> -Ross.

Hi Ross,

I was talking in general about the MARC records that most data in Open
Library are based on. At least some of them are CC0 or dedicated to
the public domain: http://archive.org/details/ol_data

Since that data is available, I was thinking we can use them again. Or
am I wrong here?

Ben
_______________________________________________
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