package newfacilities

_content_ {

_pageheading_(Examples of facilities we'd like to add to Greenstone)

<dl>
<dt><b>Internationalization</b></dt>
<dd>We'd like to work with you to provide full  
support for your language, including stemming (when searching), word  
segmentation (for oriental languages), and appropriate alphabetic or  
other sorting for browsing lists.</dd>
<p>
<dt><b><a href="_gwcgi_?a=p&p=plugins">Plugins</a></b></dt>
<dd>Greenstone incorporates plugins for many different file formats. But we are always looking for more! We can write specific plugins on a contractual basis. And of course, we welcome contributions of 
code to enable us to extend Greenstone.</dd>
<p>
<dt><b>Flexible workflow model</b></dt>
<dd>Extend the Greenstone Librarian Interface to  
allow remote users to prepare metadata and submit documents to a  
central site, and enable a librarian at that site to receive documents  
and check and correct the metadata before including it in a centralized  
collection.</dd>
<p>
<dt><b>Exporting documents</b></dt>
<dd>Extend Greenstone to allow the user to export  
selected documents and metadata in a variety of formats.</dd>
<p>
<dt><b>User-friendly format statements</b></dt>
<dd>Create an interactive editor in the  
GLI for format statements.</dd>
<p>
<dt><b>Explode metadata files in the Greenstone Librarian Interface</b></dt>
<dd>Currently  
when you add  into your collection a file of MARC records, or a  
CDS/ISIS database, or any other bibliography file, the metadata is  
included in the Greenstone collection but does not appear as editable  
GLI metadata. If you want to correct it, you have to go back to the  
original source file. This new feature will (optionally) convert  
bibliographic records into GLI metadata so that you can edit and  
maintain them within GLI. However, you will not then be able to go back  
to your original metadata format. Note that GLI is not a full database  
system and there will be a limit to the number of records it can  
accommodate.</dd>
</dl>
}