Custom Query (424 matches)

We need a new release kit.

It should check out of svn the documented example collections, build each collection (will it need to install greenstone to do this?), delete the archives/building folders, then zip up the collections.

The check out currently has a top level documented-example-collections folder, then sub folders for each collection. This structure should be kept in the zip file. So when the release zip is unzipped into the collect directory, the top level folder is kept - this is a collectgroup, so all doc eg colls are on a separate home page linked to by a single icon.

collect groups now work properly for local greenstone and gli.

Collect groups is a folder in the collect directory, with an etc directory, with collect.cfg file with 'collectgroup true' in it. then you can put collections in the subfolder and they will be grouped together.

We need to check remote gli to see if it can handle this. I think at the moment it won't because all the commands get a collection name - nothing to say its in a subdir.

Do we want to make this work for this release or the next one?

In our oaiserver code, we allow any extra information to be added as elements to the identify response. But this is not allowed (at least in 2.0. Check for 1.1).

You can have a description element, and that can contain anything but must validate to a schema.

I propose we make up a schema for the description element that allows anything, then put the new elements in that. Or else, could use metadata name="" elements.