Changeset 3950
- Timestamp:
- 2003-03-20T16:33:17+12:00 (21 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/gsdl3/TODO_michael
r3813 r3950 3 3 /home/kjdon/public_html/michael (www.cs.waikato.ac.nz/~kjdon/michael) has some helpful docs - actually only one - the jni book. 4 4 also see hints.tex and manual.tex in docs/manual - printed out too. 5 6 7 * GS2MGPPSearch - currently for field searching, it uses a hard coded list of fields - this should be read in from the config file and be colleciton dependent. see createParameter, for the FIELD_FIELD_PARAM.8 5 9 6 … … 15 12 I've been meaning to do this for ages, but never got around to it. The code is at www.greenstone.org/gatherer. talk to david. 16 13 17 * dynamic xslt ie old format statements.18 in gs2 the collection builder can add format statements for search results, doc text, classifiers to the collect.cfg file. gs3 uses xslt for formatting pages.19 collection builders should be able to specify some xslt eg a single template for a document in a search result list, to the config file, to be passed to the actions and incorporated into teh stylesheet before processing the page.20 21 What I have done so far:22 In browse action, the code checks for the existence of a <stylesheet> element in the response:'23 24 Node new_style = GSXML.getChildByTagName(response, GSXML.STYLESHEET_ELEM);25 if (new_style !=null) {26 GSXSLT.mergeStylesheets(style_doc, (Element)new_style);27 response.removeChild(new_style);28 }29 30 If it finds it, it adds it in to the stylesheet which will be used for transforming the page (mergeStylesheets), and then removes it from the response.31 32 If a template is added with a higher priority, it will be used instead of the default one33 34 eg35 <xsl:template match="document" priority="3">36 37 I have tried this out with hardcoding the service to return a static xslt along with a classifier response and it works fine.38 39 TODO:40 41 For classifiers: edit the GS2Browse service agent to look in a config file for xslt fragments - should probably go in the collectionConfig.xml which isn't used yet. but for now can go in buildConfig.xml.42 43 Then it needs to pass the appropriate one back with a response. - they are classifier specific.44 have a look at classifier.xsl (in interfaces/default/transforms) to see how the templates are used. The ones you'd want to return are document and maybe node, but node is really complicated.45 46 you need to decide how to add it into the config file - element names etc and where to put it - inside the classifier element? in a <stylesheet> node or something different?47 48 Once that is working for classifiers, you can do the same thing for query search results and document text. You will need to do the action side as well for those, but that should just be a metter of cutting and pasting code.49 50 Another thing to think about: the browse action just looks for the stylesheet element in a normal response. but perhaps it should be a separate request sent to a service? do you have some xslt which you would like me to use?51 52 if it just comes back in a response from a different request, when doing eg a query, when does it come back? with the original query result? I guess you'd send a request to a query, and along with the document list, it could send back a stylesheet element if it wanted too.53 54 It may be cleaner to have a separate request, I dont know.55 14 56 15 * Display stuff vs metadata … … 92 51 If the program is running locally its much simpler just to send a filename - can we somehow check for this? 93 52 94 * 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. 53 * configure Collection for building 54 55 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. 95 56 96 57 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. … … 115 76 * Lucene - svetlana has done a project comparing mg, mgpp and lucene. investigate further whether lucene would be good for us to use. incremental update? 116 77 report on my desk. 78
Note:
See TracChangeset
for help on using the changeset viewer.