Differences between revisions 1 and 2
Revision 1 as of 2008-06-26 12:26:04
Size: 2555
Editor: kfc
Comment: Created by the PackagePages action.
Revision 2 as of 2010-03-17 13:13:23
Size: 2562
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
This action is part of [:Iteration7: iteration 7] This action is part of [[Iteration7| iteration 7]]
Line 6: Line 6:
The goal of this action is to set up a test server with Summa. It will use the packaged-for-test-deployment [http://wiki.statsbiblioteket.dk/findex/SummaOnAStick SummaOnAStick]. The test server should be installable for individual DOMS developers and a concrete instance should be installed on alhena. The goal of this action is to set up a test server with Summa. It will use the packaged-for-test-deployment [[http://wiki.statsbiblioteket.dk/findex/SummaOnAStick|SummaOnAStick]]. The test server should be installable for individual DOMS developers and a concrete instance should be installed on alhena.
Line 15: Line 15:
The XSLT for displaying records in the website is more tricky since it is hard coded in the [http://hera/cgi-bin/viewcvs.cgi/SimpleSummaWeb/ SimpleSummaWeb CVS module] in the [http://hera/cgi-bin/viewcvs.cgi/SimpleSummaWeb/resources/showrecord.jsp?rev=HEAD&content-type=text/vnd.viewcvs-markup showrecord.jsp]. To fix this we should add additional (hard coded) provisions to !SimpleSummaWeb support the {{{sbdoms}}} basename, mapping it to the url of the index XSLT in the ViewVC. This is not elegant in any way, but it is relatively quick and allows us to use newer versions of SOAS without modifications. The XSLT for displaying records in the website is more tricky since it is hard coded in the [[http://hera/cgi-bin/viewcvs.cgi/SimpleSummaWeb/|SimpleSummaWeb CVS module]] in the [[http://hera/cgi-bin/viewcvs.cgi/SimpleSummaWeb/resources/showrecord.jsp?rev=HEAD&content-type=text/vnd.viewcvs-markup|showrecord.jsp]]. To fix this we should add additional (hard coded) provisions to !SimpleSummaWeb support the {{{sbdoms}}} basename, mapping it to the url of the index XSLT in the ViewVC. This is not elegant in any way, but it is relatively quick and allows us to use newer versions of SOAS without modifications.

Set Up Summa on A Stick (on a server)

This action is part of iteration 7

The goal of this action is to set up a test server with Summa. It will use the packaged-for-test-deployment SummaOnAStick. The test server should be installable for individual DOMS developers and a concrete instance should be installed on alhena.

Summa needs to know about two XSLTs. One for indexing and one for displaying a record. The indexer has a configuration property for defining the URL to look for the XSLT at and we suggest that we point it directly into the ViewVC interface on merkur, at least for the alhena-instance. An example link to the global build file in trunk looks as follows:

http://merkur/viewvc/trunk/build.xml?root=doms&view=co

This should just be modified to point at the proper XSLT and the indexer will automagically fetch it.

The XSLT for displaying records in the website is more tricky since it is hard coded in the SimpleSummaWeb CVS module in the showrecord.jsp. To fix this we should add additional (hard coded) provisions to SimpleSummaWeb support the sbdoms basename, mapping it to the url of the index XSLT in the ViewVC. This is not elegant in any way, but it is relatively quick and allows us to use newer versions of SOAS without modifications.

Note: If developers want to point the index XSLT to their local installations this is still easily accomplished by changing the jsp to point at their local XSLT.

With this in place it will still take some custom adjustments to !SummaOnAStick to be deployed in a DOMS context. Note however that this iteration does not require integration with the domssetup-script.

  • (1 md) (TE, MKE) (Done) Modify Summa on a Stick to include Lucene Storage.
  • (1 md) (TE) (Done) Write a script or provide detailed information on how to tweak a SoaS-installation to DOMS-use.
  • (½ md) (TE) (Done 1md) Install Summa on a Stick on alhena and couple it to a DOMS-installation on that machine.

Status 2008-01-21: A suitable version of SummaOnAStick has been rolled and TestSetup has been updated to include installation instructions.

ABR: 4 md spent getting Summa to work with miniDOMS

ActionSummaOnAStick (last edited 2010-03-17 13:13:23 by localhost)