This is just a random list of things for the future - if anyone works on something can they remove it from the list or mark that its done. * currently nothing is cached - service decriptions, text strings etc could all be cached. use - user preferences cached? eg query params from previous query request? * document structure - new greenstone archive format? TEI, XHTML, OO, GML compatible? parallel document structures? - associated resources/documents - xlinks * greenstone 3 building - is building going to change for gs3, or will we continue to use the perl scripts? - import, build, activate - info extraction, augmentation - incremental update? - modular? xml pipeline? * additional services - music search - keyphrase stuff - search history * all the gs2 admin/security stuff - user management, authentication * server side threading issues - is it thread safe? * usage logs * better error handling * document version control * combining requests to MR - results from first one becoming content for second one?? * getting the interface to determine from the xslt what info to ask for, eg whther to display Title or To and From metadata for a document in the search result list. * retrieving resources/associated docs * keeping state eg for usage logs, preserving preferences between pages, old gs preferences page etc * katrinas language translation stuff - when translating, we want to click on a text piece or macro and go to a sample page with that text string in it. can we do this? can we tell in gs3 where bits will be in pages? I think we could have a new type of request, that provides a page containing all teh text strings used by a service/agent. - would it be class specific or service specific? eg it would contain the service form, some sample results, and if its a process type of thing, all teh possible error and success messages. what about the interface bits? * is the 'to' att compulsory? do we have to have to=""? * query info - eg num docs found from a search, query term info - is this called metadata for the query and returned in a metadataList? or should it have another name? 55 ... ???? * how do we specify content type for a service? eg DocumentRetrieve content is a list of , MetadataRetrieve content is a list of docs as above, and a list of . Need to specify this in the service description?? * use collectionConfig as well as buildConfig. - format of the collection config file - indexes, display strings (old collection meta), format stuff - xslt - make sure there is nothing hard coded in a service about its services where it should be looking at the config file. * are message formats fixed? can we create a DTD? or will they evolve too much over time? * sitewide service agents - may want to specify that only some of the services that could potentially be provided by an agent are actually provided. * should actions respond to describe requests? and what would they say if they did? are they agents and part of teh system, or somehow outside the system? * download new version of tomcat. what about soap? is there a new version of that too? * combined query services - eg one page with two service forms on there eg text query and music query - need to combine the results. eg teh action could carry out both queries then use xslt to combine the results. or do the same thing across title and creator indexes in mg to approximate fielded searching? true cross collection search would probably need a new service?? * if leave an applet page you lose all teh previous info eg for the status display for importing. need a function to retrieve again all the previous messages to redisplay them. * there should be a command that anyone can send to any agent to reconfigure itself eg reload a colection if its indexes have changed, load in a new collection, reload a service agent etc. * can the xslt dynamically retrieve the metadata it needs for say query results??