| 1 | General todo list. in no particular order. large jobs.
|
|---|
| 2 |
|
|---|
| 3 | * gs3 release - basic stuff, translations, installation, documentation. oct 31? gs2 building only, both default and nzdl interfaces? gatherer?
|
|---|
| 4 |
|
|---|
| 5 | * generic resource retrieval - associated documents, src docs eg pdf/word, niupepa image files etc. if http accessible, put a link otherwise use a general resource retrieve?
|
|---|
| 6 |
|
|---|
| 7 | * collector collection building - do we want to finish this? needs addDocument and configureCollection services.
|
|---|
| 8 |
|
|---|
| 9 | The addDocument service (in GS2Construct) has not been implemented. It should take a file name and add the document to the import directory of teh collection.
|
|---|
| 10 | there are problems with just transmitting a file name - the service may live remotely and therefore the document is not there. You should probably send it attached to the html - therefore need to work out:
|
|---|
| 11 | how to get the document attached to the form (theres something to do with post and encoding = multipart ?? otherwise the browser just sends the filename),
|
|---|
| 12 | and then where to get it in the servlet - is it a parameter? or something else?
|
|---|
| 13 |
|
|---|
| 14 | and then it needs to be added into the xml request to be passed to the service.
|
|---|
| 15 |
|
|---|
| 16 | If the program is running locally its much simpler just to send a filename - can we somehow check for this?
|
|---|
| 17 |
|
|---|
| 18 | * configure Collection for building
|
|---|
| 19 |
|
|---|
| 20 | also to do with building, a little harder, is the ConfigureCollection service. There is no stub for it yet, but easy enough to add one. - need to add this service to the service description xml stuff, and write a processConfigureColleciton() method. It would be easy enough to display the config file in a big text box, and have the user edit it like the collector does.
|
|---|
| 21 |
|
|---|
| 22 | the hard bit is that when you click ConfigureCollection, you dont know what collection you are going to be dealing with - all the building services, you select the collection on the service page. with the configure stuff, you need to select the collection, and then the config file needs to be retrieved. so its really a two step process to configure the coll - first select the coll, submit that, then edit the config file, and submit that.
|
|---|
| 23 |
|
|---|
| 24 | All the services currently are one step - need to think about how this type of service fits into the model.
|
|---|
| 25 |
|
|---|
| 26 | maybe it needs a hidden arg? - to tell teh service if you're at stage 1 or 2?
|
|---|
| 27 | when teh action does the request, it then asks for the service description again to redisplay it for the user. maybe if the service knows that it has done the first half, it sends the second type of description?
|
|---|
| 28 |
|
|---|
| 29 | also do we use the collect.cfg file or the collectionConfig.xml file to show the user?
|
|---|
| 30 |
|
|---|
| 31 | * sequence of services
|
|---|
| 32 |
|
|---|
| 33 | some service clusters have services that you are supposed to carry out in sequence such as building, but there may be others.
|
|---|
| 34 |
|
|---|
| 35 | can we do a generic action or xslt or something that sends teh user to teh next service once they've completed the first one?
|
|---|
| 36 |
|
|---|
| 37 | Maybe the service cluster/serviceRack class specifies teh sequence of services, and they are all handled individually like present except that some xslt puts a next button on each page with a link to teh next service in the list.
|
|---|
| 38 |
|
|---|
| 39 | * proper install package
|
|---|
| 40 |
|
|---|
| 41 | * currently nothing is cached - service decriptions, text strings etc could all be cached. (cgi args are cached by tomcat)
|
|---|
| 42 |
|
|---|
| 43 | * document structure - new greenstone archive format? TEI, XHTML, OO, GML compatible? parallel document structures?
|
|---|
| 44 | - associated resources/documents - xlinks
|
|---|
| 45 |
|
|---|
| 46 | * greenstone 3 building - is building going to change for gs3, or will we continue to use the perl scripts?
|
|---|
| 47 | - import, build, activate
|
|---|
| 48 | - info extraction, augmentation
|
|---|
| 49 | - incremental update?
|
|---|
| 50 | - modular? xml pipeline?
|
|---|
| 51 |
|
|---|
| 52 | * additional services - music search
|
|---|
| 53 | - keyphrase stuff
|
|---|
| 54 | - search history
|
|---|
| 55 |
|
|---|
| 56 | * all the gs2 admin/security stuff - user management, authentication
|
|---|
| 57 |
|
|---|
| 58 | * server side threading issues - is it thread safe?
|
|---|
| 59 |
|
|---|
| 60 | * usage logs
|
|---|
| 61 |
|
|---|
| 62 | * better error handling
|
|---|
| 63 |
|
|---|
| 64 | * document version control
|
|---|
| 65 |
|
|---|
| 66 | * combining requests to MR - results from first one becoming content for second one??
|
|---|
| 67 |
|
|---|
| 68 | * 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?
|
|---|
| 69 |
|
|---|
| 70 | can we tell in gs3 where bits will be in pages?
|
|---|
| 71 | 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?
|
|---|
| 72 | 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.
|
|---|
| 73 |
|
|---|
| 74 | what about the interface bits?
|
|---|
| 75 |
|
|---|
| 76 | * are message formats fixed? can we create a DTD? or will they evolve too much over time?
|
|---|
| 77 |
|
|---|
| 78 | * sitewide service agents - may want to specify that only some of the services that could potentially be provided by an agent are actually provided.
|
|---|
| 79 |
|
|---|
| 80 | * 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?
|
|---|
| 81 |
|
|---|
| 82 | * what about soap? is there a new version of that?
|
|---|
| 83 |
|
|---|
| 84 | * 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.
|
|---|
| 85 |
|
|---|
| 86 | or do the same thing across title and creator indexes in mg to approximate fielded searching?
|
|---|
| 87 |
|
|---|
| 88 | true cross collection search would probably need a new service??
|
|---|
| 89 |
|
|---|
| 90 | * more generally, combining services in general, action and service level
|
|---|
| 91 |
|
|---|
| 92 | * action helpers: query term highlighting, page transformation and metadata determination (remove from receptionist?)
|
|---|
| 93 | * 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.
|
|---|
| 94 |
|
|---|
| 95 | * can the xslt dynamically retrieve the metadata it needs for say query results??
|
|---|
| 96 |
|
|---|
| 97 | * CSS instead of tables? - use html lists than use css to format them.
|
|---|
| 98 |
|
|---|
| 99 | * cross coll search - if colls are built the same, just present the form and search both. need to think about ranking.
|
|---|
| 100 | if colls are not built the same, and have indexes, subcolls, langs - do we merge the lists? and only search those that have the right ones? what if two indexes have different meanings and display text but the same id? are they treated as same index? which name do you display?
|
|---|
| 101 | what about colls with different levels eg oneonly has document, the other doc and section. what do you display? field lists? just combine?
|
|---|
| 102 |
|
|---|
| 103 | * search history
|
|---|
| 104 |
|
|---|
| 105 | * use objects instead of applets? java provides a conversion tool. NPX_PLUGIN_PATH=
|
|---|
| 106 |
|
|---|
| 107 | * danas combined search and browse stuff
|
|---|
| 108 |
|
|---|
| 109 | * can xslt be used to generate requests as well as transform teh output?
|
|---|
| 110 |
|
|---|
| 111 | * kea.
|
|---|
| 112 |
|
|---|
