[cc-devel] API to Internet Archive?
Nathan R. Yergler
nathan at yergler.net
Mon Oct 17 18:02:14 EDT 2005
So two things. First, you *have* to specify the license URL in the
<licenseurl> element, otherwise IA won't display the license
correctly. The fact that we populate the <license> element is really
just an artifact of the way ccPublisher handles metadata. That said,
we have settled on the text there as the de facto standard for
embedded license declarations, so if you populate it, that'd be
cool. Two points about that text:
1) The "verify at ..." is optional (this just needs to be taken into
account when parsing); you can't make any validity claims without
this portion, but we don't require it (since it requires an external
metadata file).
2) The url following verify at is the location of the verification
RDF, not the license. So you have [date] [holder] Licensed to the
public under [license_uri]. Verify at [verify_uri].
Nathan
On Oct 17, 2005, at 2:17 PM, Tim Olsen wrote:
> Hi Nathan,
>
> The Advanced Contribution page says to use <licenseurl> to specify a
> license url. I noticed, however, you use <license> to specify a
> license url in the _meta.xml file, and in the _files.xml you use
> <license> to specify the whole license claim ( [date] [holder]
> Licensed to the public under bla bla. verify at [license url]) for
> each file.
>
> I'm guessing that regardless of what the Advanced Contribution page
> says, your way will become the de-facto standard as they are pushing
> the ccPublisher.
>
> should I just follow what you're doing?
>
> thanks,
> Tim
>
> On 10/10/05, Nathan R. Yergler <nathan at yergler.net> wrote:
>
>> Hi Tim,
>>
>> I saw your earlier email (not sure if you or the Archive forwarded
>> it to
>> me), but completely spaced out replying. Mea culpa.
>>
>> ccPublisher originally used the Advanced Contribution interface from
>> IA. The interface is documented at
>> http://www.archive.org/help/contrib-advanced.php. It involves
>> uploading
>> the files and metadata to IA and then polling a URI to start the
>> import
>> process. The latest release of ccPublisher (and last few releases of
>> Ourmedia Publisher) all use the new Direct Contribution interface,
>> which
>> reduces the delay between when an item is uploaded and when it is
>> available on the site. The Direct Contribution interface is
>> documented
>> at http://www.archive.org/help/contrib-direct.php.
>>
>> ccPublisher abstracts it's Archive.org functionality into the
>> PyArchive
>> module, in CVS at
>> http://cvs.sourceforge.net/viewcvs.py/cctools/pyarchive/
>> pyarchive/. In
>> particular submission.py contains our wrappers for the contribution
>> interfaces. If I recall correctly, CVS HEAD is still the old-style
>> interface, and the ccp8_1_0_x branch has the new DC interface.
>>
>> I'd be happy to help you with any naggling details or questions
>> you have.
>>
>> Nathan R. Yergler
>> Software Engineer
>> Creative Commons
>>
>> Tim Olsen wrote:
>>
>>
>>> Hi,
>>>
>>> My coworkers and I are adding to LimeWire the ability to upload
>>> CC-licensed files to the Internet Archive. I noticed ccPublisher
>>> has
>>> this ability. Does anyone know of a published API for
>>> interfacing to
>>> the Internet Archive?
>>>
>>> I've tried asking this on the Internet Archive discuss list
>>> (archivists-talk at yahoogroups.com), but haven't received a response
>>> yet.
>>>
>>> thanks,
>>> Tim
>>> _______________________________________________
>>> cc-devel mailing list
>>> cc-devel at lists.ibiblio.org
>>> http://lists.ibiblio.org/mailman/listinfo/cc-devel
>>>
>>>
>>>
>>
>>
>
More information about the cc-devel
mailing list