Fwd: Re: [Clipart] REPOST: openclipart packages and the idx file
mtraum at yahoo.com
Wed Apr 13 12:00:25 PDT 2005
This was direct to me, as opposed to the list (probably because of
the list misconfiguration I just posted about), so I figured I'd fwd
it to the list.
--- Nathan Eady <eady at galion.lib.oh.us> wrote:
> Mike Traum wrote:
> > I haven't heard anything back about this yet.
> > I think it would make a lot of sense to have a well-structured
> > file in your packages so that other applications can be more
> > written to take advantage of your efforts and improve the user
> > experience when dealing with openclipart.
> >>With regards to the keywords.idx file in the package, can you
> >>making that an xml file? It's a very perl centric file, which
> >>make's it difficult for others (like myself) to write tools that
> >> your packages.
> Okay, I'll dewarnock it.
> The existing keywords.idx file was _mainly_ intended to be used by
> keyword search tool (though of course it may have other uses). It
> exists largely because it was very easy to create. The code that
> it is about two lines long. (That is just writing the index file;
> data are collected as part of a larger metadata processing
> called authority control.) It is also very practical for the
> search tool, because, again, the code that reads it is one line
> I can see the value of having an XML index, but should it index
> just the
> keywords, or also authors, titles, and other metadata? Also it
> be named with an .xml suffix probably, something like index.xml or
> similar. Anyone is welcome to write a tool that creates such an
> and presumably if the tool existed we would roll it into the
> procedure so that the release packages would include the index. If
> a tool were written in Perl, it could just read the existing index
> one line and then walk the data structure; if it were written in
> language, it would have to duplicate some of what the authority
> script does, in walking the actual collection and reading the
> metadata from the images -- which means also duplicating
> In other words, it would be significantly easier to write it in
> I might get to it myself, eventually (in which case I would
> just roll the functionality into the existing authority control
> but at this time, I have several more urgent things on my personal
> list for this project. Primarily, we really need to iron out those
> issues with the upload script and image validation, sooner rather
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
More information about the clipart