"harvestable" Metadata following OAI or other standards

be_kul <[email protected]> Thu, 9 Oct 2003 16:24:15 +0200
Newsgroups gmane.comp.web.zope.plone.collective.ticle
Message-ID <[email protected]>
Am Dienstag, 07.10.03 um 17:26 Uhr schrieb Simon Pamies:

> Hi!
> after some days of heavy learning now a living sign fro me ;-)
>
>> One first suggestion is the possibility to have Ticle-Objects be OAI
>> (Open Archives Initiative) compatible by coming harvestable (?)
>> Metadata with them by default.
>
> Doesn't understand what you mean with harvestable Metadata ... example?

What I mean is, that a robot (like the one used by the Open Archive 
Initiative) could visit your Zope-driven website and get the metadata 
information of (all?) objects for "his" database.
Because we here in Rome take part in a European project called ECHO 
(European Cultural Heritage Online, see also 
http://echo.mpiwg-berlin.mpg.de) where it is planned to have a central 
repository of information on the objects stored in the different 
partner databases, we decided to use or offer (at least) OAI 
compatibility, so all of our content could also be found over OAI 
searches: "Open Archives" is exactly what we want :-)
(see also: Open Access Conference: 
http://www.zim.mpg.de/openaccess-berlin )

Ooops: information, guidelines, samples etc. can be found on the OAI 
website: http://www.openarchives.org )

(My basic problem with all this stuff is that Dublin Core or OAI are 
meant to display information about a website - may it be created 
dynamically or be static.
So, a dabatase entry describing Michelangelo's David should not contain 
"Michelangelo" as the creator, but Hutzli Putzli (or whoever created 
the Database entry) ... But, of course, no-one is really interested in 
_that_ information. Then, the problem becomes one of Meta-Metadata or 
so....? (Reminds me of the endless possibilities to create meta-levels 
in philosophical discussions :-)

>
>> PS: Wherever the name TICLE might come from - to me it seems that it
>> could be confused with the pronounciation for "Tcl", couldn't it? I'd
>
> Yes - we didn't had that in Mind - hmmm suggestions for a new name?
> I think internally we'll keep the TICLE (CVS problems when renaming 
> aso...),
> but if someone (Bernd? ;-) has his head full of new names suggestions 
> welcome.
> At the public project sites we'll change it then!

I keep thinking on another name - but some other things here have 
priority at the moment :-)

Ciao

Bernd

>
> cheers
> Simon
>



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php