Tool Name: Glossary Developer(s): OSPI developers
|Description of Tool||Tool displays a list of terms and short description. Clicking on the term gives a longer description. Has editing and upload facilities.|
|Origin of Tool||OSPI developers|
|Agreement with original Authors (please state process and nature of agreement)||none required, available with Sakai download|
|Platform used (please tick)||JetSpeed: uPortal: GridSphere: LifeRay: CHEF (OGCE): Sakai: x Other:|
|Integration Technology used (please tick)||JSR-168: WSRP: OKI OSID: TPP: x|
|In repository? (note discussions with NeSC and status||Status: Download:|
|With OMII? (note discussions with OMII and status||Status:|
|With Sakai? (note discussions with Sakai and status||Status: available with Sakai download|
|Integration signed off by|
Description of work undertaken during porting:
None, but additional work could be suggested, including using a standard XML format for gossary, such as the one proposed by http://www.creativyst.com/Prod/Glossary/Doc/XMLOut.htm.
In using the tool RJA wrote an XSLT script to translate a previously-defined glossary (for ReDRESS and the JISC eFER) which uses the above schema to the much simpler schema used by OSPI. According to the developers, the latter was designed to meet their needs and no more. RJA has sent copies of the script and sample input together with a list of issues to the developers.
Tool is unstable. editing sometimes loses input. Upload of large quantities of data sometimes does not work. XML input has to be in exactly the expected format with all tags present for each entry. Tool is somewhat cumbersome for large glossaries.
Ongoing support issues:
Non-standard XML schema as note above.
Tool use case:
Provides a list of terms for a project with precise definitions which can be collaboratively edited and agreed
Help information for tool users: