Custom Query (424 matches)

Nikolaos reported on the mailing list:

In a greenstone 3 library metadata is correctly displaying in utf-8, but in oaiserver its coming out as iso-8859-1.

Need to fix this.

Currently only GLI "knows about" ex metadata. GLI strips ex off before writing out the config file.

This is confusing for users, who have to write different things when they are in GLI compared with editing config file by hand.

Make the whole system accept ex metadata.

• build code (classifiers, index etc) - can we just strip off when reading in config file
• runtime - format statements need to strip off ex. anywhere else?

Then we can get rid of the horrible code in GLI which is looking for ex. and removing it.

GLI and coll build and gs2 will be modified to cope with explicit ex. metadata (see #577).

Make gs3 runtime do the same.