[ckan-dev] Handle System extensions for CKAN?

[John Erickson]

Hi Everyone!

We're working on extending the CKAN deposit workflow to including
object registration with esp. the Handle System. This will include
basic PID generation/registration, type-based metadata collection and
deposit, and of course data deposit (or "deposit" of external download
link).

We're curious if anyone has any lessons-learned from hacking the basic
CKAN ingest workflow in that way: calling out to third party
registration systems, etc. One of the big issues we'll be facing is
implementing a type registry, in which the metadata template presented
to the user is based on a Handle-named object type, which will be
defined esp. by an RDF schema linked to from the Handle record (so the
CKAN metadata template will need to be driven by an external
definition, not hard-coded in an extension).

Thoughts? Thanks!

John
PS: In addition to depositing the typed data objects via CKAN (e.g. a
scientific dataset of a particular type), the data files (e.g. RDF)
that will define the object types will be deposited in this same way.

-- 
John S. Erickson, Ph.D.
Director, Web Science Operations
Tetherless World Constellation (RPI)
<http://tw.rpi.edu> <olyerickson at gmail.com>
Twitter & Skype: olyerickson