| 1 | 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.
|
|---|
| 2 |
|
|---|
| 3 | * currently nothing is cached - service decriptions, text strings etc could all be cached. use
|
|---|
| 4 |
|
|---|
| 5 | - user preferences cached? eg query params from previous query request?
|
|---|
| 6 |
|
|---|
| 7 | * document structure - new greenstone archive format? TEI, XHTML, OO, GML compatible? parallel document structures?
|
|---|
| 8 | - associated resources/documents - xlinks
|
|---|
| 9 |
|
|---|
| 10 | * greenstone 3 building - is building going to change for gs3, or will we continue to use the perl scripts?
|
|---|
| 11 | - import, build, activate
|
|---|
| 12 | - info extraction, augmentation
|
|---|
| 13 | - incremental update?
|
|---|
| 14 | - modular? xml pipeline?
|
|---|
| 15 |
|
|---|
| 16 | * additional services - music search
|
|---|
| 17 | - keyphrase stuff
|
|---|
| 18 | - search history
|
|---|
| 19 |
|
|---|
| 20 | * all the gs2 admin/security stuff - user management, authentication
|
|---|
| 21 |
|
|---|
| 22 | * server side threading issues - is it thread safe?
|
|---|
| 23 |
|
|---|
| 24 | * usage logs
|
|---|
| 25 |
|
|---|
| 26 | * better error handling
|
|---|
| 27 |
|
|---|
| 28 | * document version control
|
|---|
| 29 |
|
|---|
| 30 | * combining requests to MR - results from first one becoming content for second one??
|
|---|
| 31 |
|
|---|
| 32 | * 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.
|
|---|
| 33 |
|
|---|
| 34 | * retrieving resources/associated docs
|
|---|
| 35 |
|
|---|
| 36 | * keeping state eg for usage logs, preserving preferences between pages,
|
|---|
| 37 | old gs preferences page etc
|
|---|
| 38 |
|
|---|
| 39 | * 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?
|
|---|
| 40 |
|
|---|
| 41 | can we tell in gs3 where bits will be in pages?
|
|---|
| 42 | 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?
|
|---|
| 43 | 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.
|
|---|
| 44 |
|
|---|
| 45 | what about the interface bits?
|
|---|
| 46 |
|
|---|
| 47 | * is the 'to' att compulsory? do we have to have to=""?
|
|---|
| 48 |
|
|---|
| 49 | * query info - eg num docs found from a search, query term info -
|
|---|
| 50 | is this called metadata for the query and returned in a metadataList? or
|
|---|
| 51 | should it have another name?
|
|---|
| 52 |
|
|---|
| 53 | <response>
|
|---|
| 54 | <metadataList>
|
|---|
| 55 | <metadata name="numDocs">55</metadata>
|
|---|
| 56 | <content>
|
|---|
| 57 | <document name="HASHxxx"/>
|
|---|
| 58 | ...
|
|---|
| 59 | </content>
|
|---|
| 60 | </response>
|
|---|
| 61 |
|
|---|
| 62 | ????
|
|---|
| 63 |
|
|---|
| 64 | * how do we specify content type for a service?
|
|---|
| 65 | eg DocumentRetrieve content is a list of <document name="xxx"/>,
|
|---|
| 66 | MetadataRetrieve content is a list of docs as above, and a list of <metadata name="dc:Title"/>.
|
|---|
| 67 |
|
|---|
| 68 | Need to specify this in the service description??
|
|---|
| 69 |
|
|---|
| 70 | * use collectionConfig as well as buildConfig.
|
|---|
| 71 | - format of the collection config file - indexes, display strings (old collection meta), format stuff - xslt
|
|---|
| 72 | - make sure there is nothing hard coded in a service about its services where it should be looking at the config file.
|
|---|
| 73 |
|
|---|
| 74 | * are message formats fixed? can we create a DTD? or will they evolve too much over time?
|
|---|
| 75 |
|
|---|
| 76 | * sitewide service agents - may want to specify that only some of the services that could potentially be provided by an agent are actually provided.
|
|---|
| 77 |
|
|---|
| 78 | * 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?
|
|---|
| 79 |
|
|---|
| 80 | * download new version of tomcat. what about soap? is there a new version of that too?
|
|---|
| 81 |
|
|---|
| 82 | * 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.
|
|---|
| 83 |
|
|---|
| 84 | or do the same thing across title and creator indexes in mg to approximate fielded searching?
|
|---|
| 85 |
|
|---|
| 86 | true cross collection search would probably need a new service??
|
|---|
| 87 |
|
|---|
| 88 | * 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.
|
|---|
| 89 |
|
|---|
| 90 | * 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.
|
|---|
| 91 |
|
|---|
| 92 | * can the xslt dynamically retrieve the metadata it needs for say query results??
|
|---|
| 93 |
|
|---|
