Wiki

New document browser

Concept

A rewrite(?) of the existing document browser with some new features:

chunking
sorting
more search possiblities:

facet browsing
predefined filters

lookup of related WFs and possible transitions in the various tasks (?)
multi-document-selection (useful for making multi-value daisy-link field editors friendlier)
pdf export

some standard listing of the current resultset to pdf
bonus for having a pluggable xsl-fo of some sort (pulling in logos and stuff

extra actions:

in the search-result list, there could be buttons to various actions. These could be general actions (like "show", "edit", "start workflow"...) or user-defined actions (i.e. /daisy/site/ext/some-custom-action?documentId={docId})

There are several places where the document browser could be used, with different configuration requirements (e.g. when linking to a document, multi-selection would not make sense). Hence, there would be an xml document that configures the document browser instance, a query parameter can then be used
to select the right configuration:
http://.../daisy/site/documentBrowser?config=images
would match ${wikidata}/conf/documentbrowser-{config}.xml

<?xml version="1.0"?>
<docbrowser>
  <aspects>
    <daisy-meta/>
    <fulltext/>
    <facets>
      <!-- ... configuration for facets -->
    <predefined>
      <predef label="predef.withnavpart">hasPart("NavigationData")</predef>
      <predef label="predef.summercollection">InCollection("summer")</predef>
      ...
    </predefined>
  </aspects>

  <results multiselect="true">
    <columns>
      <column label="docbrowser.id" select="id"/>
      <column label="docbrowser.name" select="name"/>
      <column label="docbrowser.lastModifierLogin" select="lastModifierLogin"/>
      <column label="docbrowser.lastModified" select="lastModified"/>
      <column label="docbrowser.pubYear" select="Year(Publication)"/>
      <column label="docbrowser.somethingelse" select="Random()"/>
      <column label="docbrowser.aMultiValueField" select="$Gimmicks"/>
      <!-- NTH: this may be a good place to say something about date formatting as well -->
    </columns>
    <row-actions>
      <builtin-action label="showPreview" type="showPreview"/>
      <custom-action label="startWorkflow" url="{pageContext.mountPoint}/{site}/workflow/new?documentId={row.id}" icon="{pageContext.mountPoitn}/resources/skins/{skin}/img/wf.png"/>
      <custom-action label="mailTo" url="mailto:user@example.com?subject=Daisy Document: {row.name}&body=Click here for to for an interesting document: {pageContext.baseurl}/{pageContext.mountPoint}/{site}/workflow/new?documentId={row.id}" icon="{pageContext...}/email.png"/>
      <custom-action label="showReferrers" url="{pageContext.mountPoint}/{site}/{row.id}/referrers.html" icon="{...}/refer.png"/>
    </row-actions>
    <actions>
      <custom-action label="exportPdf" url=".../exportPdf?ids={comma_separated_ids}"/>  <!-- Probably needs to support POST-links to be practical, plus ways to control what is sent. -->
    </actions>
  </results>
</docbrowser>

Layout ideas

Like the current document browser, the document browser would have two distinct halves: The "search" part and the "search-result" part.
The "search" part would show different search aspects: fulltext, daisy-metadata, facets and predefined filters.
To save space, these would be rendered in tabs or an accordeon widget.

The "search-result" part would become table-like (like the querySearch results), but there should be a possibility of toggling between "table" mode and "preview mode" (preview-mode being the style used in the current document browser).

Mockups

These are the 'search' aspects as they would appear in an accordeon widget (all aspects are shown in collapsed mode and in expanded mode)

This is what the whole document browser would look like:

Click to enlarge

Additional requirements (not visible in current mockups):

A button to toggle between "preview" and "table" mode.
Chunking links
A button to toggle between "results" and "current selection" (the current selection of documents must be available even if not all documents are in the current resultset.

Creating a multi role authentication scheme

This step by step instruction explains how to extend the Daisy CMS with your own authentication scheme that fits your needs.

Assumption: You already set up daisy on a windows system and everything's working great. Your also doing the codeing and compiling on a separate system (a mac) because you too lazy to install the dev tool on the windows sever...

Task: You would like new daisy users to be allocated a given role when they first logon. The system admin chaps would ideally like the group the user belongs to on a windows network to dictate this role allocation.

This solution is useful where there are a number of different users who need to see different resources on the same server (ie. student and staff at a university).

Step 1: Checking out the sources

Download the daisy sources daisy-x.x.x.tar.gz of the latest stable (or milestone) release at the download area (or check out the lastest version from SVN, whatever you prefer). Extract the tarball into a directory on your local machine (although you do not have to create that environment variable, I will refer to that directory as DAISY_SRC during the rest ot this tutorial):

$ tar xvzf daisy-x.x.x.tar.gz

Step 2: Copy the sources of the Ntlm-authentication

Descend to the dircectory $DAISY_SRC/services/ and make a copy of the directory ntlm-auth, which contains the sources for the Ntlm authentication scheme. We take these sources as starting point and we will modify them to fit our needs.

$ cp -R ntlm-auth/ ntlm-group-auth

Step 3: Create the java classes for authentication

Step 3a: Rename the existing sourcefiles for AuthenticationFactory and AuthenticationScheme

Descend into the directory $DAISY_SRC/services/ssh-auth/src/java/org/outerj/daisy/authentication/impl
Rename the both existing sourcefiles for the AuthenticationFactory and the AuthenticationScheme

$ mv NtlmAuthenticationFactory.java NtlmGroupAuthenticationFactory.java
$ mv NtlmAuthenticationScheme.java NtlmGroupAuthenticationScheme.java

Step 3b: Edit NTLMGroupAuthenticationFactory.java

In your favourite editor or IDE, edit the source file for the NTLM Group Authentication Factory and change it to:

package org.outerj.daisy.authentication.impl;

import org.apache.avalon.framework.configuration.Configuration;
import org.apache.avalon.framework.configuration.ConfigurationException;
import org.outerj.daisy.authentication.spi.*;
import org.outerj.daisy.plugin.PluginRegistry;

import javax.annotation.PreDestroy;
import java.util.Map;
import java.util.HashMap;

/**
 * Constructs and registers NtlmGroupAuthenticationSchemes with the UserAuthenticator.
 *
 */
public class NtlmGroupAuthenticationFactory  {
    private PluginRegistry pluginRegistry;
    private Map<String, AuthenticationScheme> schemes = new HashMap<String, AuthenticationScheme>();

    public NtlmGroupAuthenticationFactory(Configuration configuration, PluginRegistry pluginRegistry) throws Exception {
        this.pluginRegistry = pluginRegistry;
        this.configure(configuration);
        registerSchemes();
    }

    @PreDestroy
    public void destroy() {
        unregisterSchemes();
    }

    private void registerSchemes() throws Exception {
        for (Map.Entry<String, AuthenticationScheme> entry : schemes.entrySet()) {
            pluginRegistry.addPlugin(AuthenticationScheme.class, entry.getKey(), entry.getValue());
        }
    }

    private void unregisterSchemes() {
        for (Map.Entry<String, AuthenticationScheme> entry : schemes.entrySet()) {
            pluginRegistry.removePlugin(AuthenticationScheme.class, entry.getKey(), entry.getValue());
        }
    }

    private void configure(Configuration configuration) throws ConfigurationException {
        Configuration[] schemeConfs = configuration.getChildren("scheme");
        for (Configuration schemeConf : schemeConfs) {
            String name = schemeConf.getAttribute("name");
            String description = schemeConf.getAttribute("description");
            String domainControllerAddress = schemeConf.getChild("domainControllerAddress").getValue();
            String domain = schemeConf.getChild("domain").getValue();
			
			String file1 = schemeConf.getChild("fileLocation1").getValue();
			String file2 = schemeConf.getChild("fileLocation2").getValue();
			
			Configuration subUserCreator1 = schemeConf.getChild("subUserCreator1");
			UserCreator userCreator1 = UserCreatorFactory.createUser(subUserCreator1, name);
			
			
			Configuration subUserCreator2 = schemeConf.getChild("subUserCreator2");			
			UserCreator userCreator2 = UserCreatorFactory.createUser(subUserCreator2, name);

		
			AuthenticationScheme scheme = new NtlmGroupAuthenticationScheme(name, description, domainControllerAddress, domain, file1, userCreator1, file2, userCreator2);
			Configuration cacheConf = schemeConf.getChild("cache");
			if (cacheConf.getAttributeAsBoolean("enabled")) {
				int maxCacheSize = cacheConf.getAttributeAsInteger("maxCacheSize", 3000);
				long maxCacheDuration = cacheConf.getAttributeAsLong("maxCacheDuration", 30 * 60 * 1000); // default: half an hour
				scheme = new CachingAuthenticationScheme(scheme, maxCacheDuration, maxCacheSize);
			}

			if (schemes.containsKey(name))
				throw new ConfigurationException("Duplicate authentication scheme name: " + name);
			
			schemes.put(name, scheme);
				

            
        }
    }
}

Note that this authentication factory reads in the configuration for two files and userCreators which are then passed to the authentication scheme.

Step 3c: Edit NTLMGroupAuthenticationScheme.java

In your favourite editor or IDE, edit the source file for the NTLM Group Authentication Scheme and change it to:

package org.outerj.daisy.authentication.impl;

import org.outerj.daisy.authentication.spi.AuthenticationScheme;
import org.outerj.daisy.authentication.spi.AuthenticationException;
import org.outerj.daisy.authentication.spi.UserCreator;
import org.outerj.daisy.repository.Credentials;
import org.outerj.daisy.repository.user.User;
import org.outerj.daisy.repository.user.UserManager;
import jcifs.smb.SmbException;
import jcifs.smb.SmbAuthException;
import jcifs.smb.SmbSession;
import jcifs.smb.NtlmPasswordAuthentication;
import jcifs.smb.*;
import jcifs.UniAddress;

import java.net.UnknownHostException;
import java.net.MalformedURLException;

public class NtlmGroupAuthenticationScheme implements AuthenticationScheme {
    private final String name;
    private final String description;
    private final String domainControllerAddress;
    private final String domain;
	private final String file1;
    private final UserCreator userCreator1;
	private final String file2;
    private final UserCreator userCreator2;

    public NtlmGroupAuthenticationScheme(String name, String description, String domainControllerAddress, String domain, String file1, UserCreator userCreator1, String file2, UserCreator userCreator2) {
        this.name = name;
        this.description = description;
        this.domainControllerAddress = domainControllerAddress;
        this.domain = domain;
		this.file1 = file1;
		this.userCreator1 = userCreator1;
		this.file2 = file2;
        this.userCreator2 = userCreator2;
    }

    public String getName() {
        return name;
    }

    public String getDescription() {
        return description;
    }

    public boolean check(Credentials credentials) throws AuthenticationException {
		if ( check1(credentials) ) {
			return true;
		}
		if ( check2(credentials) ) {
			return true;
		}			
		return false;
    }

    public boolean check1(Credentials credentials) throws AuthenticationException {
        UniAddress mydomaincontroller;
        try {
            mydomaincontroller = UniAddress.getByName(domainControllerAddress);
        } catch (UnknownHostException e) {
            throw new AuthenticationException("Error authenticating using NTLM.", e);
        }
        NtlmPasswordAuthentication mycreds = new NtlmPasswordAuthentication(domain, credentials.getLogin(), credentials.getPassword());		
		jcifs.Config.registerSmbURLHandler();
		SmbFile smbf;
		try {
			smbf = new SmbFile(file1, mycreds);

		}	catch( MalformedURLException seed ) {
            // NETWORK PROBLEMS?
            throw new AuthenticationException("Can't find the file specified", seed);
        }

        try {			
            return smbf.exists();	
        } catch( SmbAuthException sae ) {
            // AUTHENTICATION FAILURE
            return false;
        } catch( SmbException se ) {
            // NETWORK PROBLEMS?
            throw new AuthenticationException("Error authenticating using NTLM.", se);
        }
    }

    public boolean check2(Credentials credentials) throws AuthenticationException {
        UniAddress mydomaincontroller;
        try {
            mydomaincontroller = UniAddress.getByName(domainControllerAddress);
        } catch (UnknownHostException e) {
            throw new AuthenticationException("Error authenticating using NTLM.", e);
        }
        NtlmPasswordAuthentication mycreds = new NtlmPasswordAuthentication(domain, credentials.getLogin(), credentials.getPassword());
		
		jcifs.Config.registerSmbURLHandler();
		
		SmbFile smbf;
		
		try {
			smbf = new SmbFile(file2, mycreds);
		}	catch( MalformedURLException seed ) {
            // NETWORK PROBLEMS?
            throw new AuthenticationException("Can't find the file specified", seed);
        }

        try {
									
			return smbf.exists();
			
        } catch( SmbAuthException sae ) {
            // AUTHENTICATION FAILURE
            return false;
        } catch( SmbException se ) {
            // NETWORK PROBLEMS?
            throw new AuthenticationException("Error authenticating using NTLM.", se);
        }
    }

    public void clearCaches() {
        // do nothing
    }

    public User createUser(Credentials crendentials, UserManager userManager) throws AuthenticationException {
        if (userCreator1 != null) {
		if (check1(crendentials)) {
				User aUser = userCreator1.create(crendentials.getLogin(), userManager);
				return aUser;				
			}
        }
		if (userCreator2 != null) {
			if (check2(crendentials)) {
				User aUser = userCreator2.create(crendentials.getLogin(), userManager);
				return aUser;					
			}
        }
        return null;
    }
}

The jcifs library which daisy uses to perform NTLM authentication does not provide a simple method for checking if a user belongs to a certain windows group. However, by using the SmbFile() method for the jcifs library we can see if a user with a siven set of creidentials can access a file on a windows share. As a windows server can restrict access using groups this provides a cunning workaround.

The location of the file and other parameters are read from a the configuration file myconfig.xml, which we will create later on. This information is used inside the constructor of a new instance of our SSHAuthenticationScheme, which we created above.

You'll notice this section of code contains a number of fairly similar methods [i.e. check1() and check2()]. The methods which Daisy itself uses [i.e. check() and createUser()] calls these in order to perform the authentication at the two different levels .

I'm sure there a more elegent way of doing this....

Step 4: Building the authentication scheme

Step 4a: Compiling and packing your classes

I compile the files on my mac something like this:

Use the method of your choice to compile the code (Ant, Maven, your IDE, ...). When using the command below, we hope you know enough about this that everything should be on one line. For Windows, replace $DAISY_HOME with %DAISY_HOME% and the colons with semicolons)

javac -classpath 
   ~/Documents/intranet/daisy-2.2/lib/daisy/jars/daisy-repository-api-2.2.jar:
   ~/Documents/intranet/daisy-2.2/lib/daisy/jars/daisy-repository-server-spi-2.2.jar:
   ~/Documents/intranet/daisy-2.2/lib/daisy/jars/daisy-pluginregistry-api-2.2.jar:
   ~/Documents/intranet/daisy-2.2/lib/daisy/jars/daisy-pluginregistry-api-2.2.jar:
   ~/Documents/intranet/daisy-2.2/lib/avalon-framework/jars/avalon-framework-api-4.3.jar:
   ~/Documents/intranet/daisy-2.2/lib/jcifs/jars/jcifs-1.1.11.jar:
   ~/Documents/intranet/daisy-2.2/lib/javax.annotation/jars/jsr250-api-1.0.jar:
   ~/Documents/intranet/daisy-2.2/lib/javax.servlet/jars/servlet-api-2.4.jar:
   ~/Documents/intranet/ntlm-group-auth/src/org/outerj/daisy/authentication/impl/NtlmGroupAuthenticationScheme.class 
   ~/Documents/intranet/ntlm-group-auth/src/org/outerj/daisy/authentication/impl/NtlmGroupAuthenticationFactory.java 
   ~/Documents/intranet/ntlm-group-auth/src/org/outerj/daisy/authentication/impl/NtlmGroupAuthenticationScheme.java

jar cvf ntlm-group-auth.jar *

I run this command from the directory shown below:

~/Documents/intranet/ntlm-group-auth/src/

Step 4b: Copying the jar-file into place

Copy the newly created jar file both into the lib directory of your daisy binary distribution ($DAISY_HOME/lib). Copy the file daisy-auth-ssh-<version>.jar into the directory daisy/jars/.

$ cp target/daisy-auth-ssh-<version>.jar $DAISY_HOME/lib/daisy/jars/

If you don't want to create a binary distribution of daisy it might be sufficient to copy the jar-file to the $DAISY_HOME/lib directory only.

Details from this point on are a little sketchy, need to check the info on a different PC.

Step 5: Registering and configuring the new component

Step 5a: Registering the new component

Edit the file $DAISY_HOME/repository-server/conf/block.xml. Inside the container named authentication, include your newly created scheme. The element <container> of block.xml now should look like (adapt the versions of your jar files for ntlm and ssh authentication!):

<container name="authentication">
  <services>
    <service type="org.outerj.daisy.authentication.UserAuthenticator">
      <source>authenticator</source>
    </service>
    <service type="org.outerj.daisy.authentication.AuthenticationSchemeRegistrar">
      <source>authenticator</source>
    </service>
  </services>

  <component name="authenticator" class="org.outerj.daisy.authentication.impl.UserAuthenticatorImpl"/>

  <component name="daisy-native" class="org.outerj.daisy.authentication.impl.DaisyAuthenticationFactory">
    <configuration>
      <cache enabled="true" maxCacheSize="3000" maxCacheDuration="1800000"/>
    </configuration>
  </component>

  <component name="ldap" class="org.outerj.daisy.authentication.impl.LdapAuthenticationFactory">
    <configuration>
      <!-- See myconfig.xml.template for an example configuration -->
    </configuration>
  </component>

  <include name="ntlm" id="daisy:daisy-auth-ntlm" version="1.4-dev"/>
  <include name="ssh" id="daisy:daisy-auth-ssh" version="1.4-dev"/>
  <include name="ntlm-group" id="daisy:daisy-auth-ssh" version="1.4-dev"/>

</container>

Step 5b: Configuring the new component

Inside the directory $DAISY_HOME/repository-server/conf/ you will find a file myconfig.xml.template. Copy this file into the directory conf/ inside your repository and rename it to myconfig.xml

$ cp $DAISY_HOME/repository-server/conf/myconfig.xml.template /path/to/your/repository/conf/myconfig.xml

Edit the newly created file myconfig.xml. Add a target in order to configure your authentication scheme, inside that target, fill in the IP or host name of your SSH-server. Also, in order to enable automatically creation of user accounts once the user logs in to daisy for the first time, define our newly created scheme as authentification scheme for user creation as shown below:

<targets>
  <target path="..."
    ...
  </target>

  ... many more targets

  <target path="/daisy/repository/authentication/authenticator">
    <configuration>
      <!-- Indicates which authentication scheme to use, if any, to automatically create new users. -->
      <authenticationSchemeForUserCreation>ntlmgroup1</authenticationSchemeForUserCreation>
    </configuration>
  </target>

  ... many more targets

  <target path="XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX">
    <configuration>
       <!-- You can configure one or more NTLM-based authentication schemes here -->
          <!-- Notes:
                - the name of a scheme should not be daisy, no two schemes can have the same name
                - the autoCreateUser element is optional
          -->
          <scheme name="ntlmgroup1" description="Test NTLM Group config">
            <domainControllerAddress>127.0.0.1</domainControllerAddress>
            <domain>yum</domain>
            <cache enabled="true" maxCacheSize="3000" maxCacheDuration="1800000"/>
			<fileLocation1>afilelocation</fileLocation1>
			<fileLocation2>afilelocation</fileLocation2>
			<subUserCreator1>
			   <autoCreateUser>
				  <roles>
					<role>User</role>
				  </roles>
				  <defaultRole>User</defaultRole>
				  <updateableByUser>true</updateableByUser>
				</autoCreateUser>
				<test>astring</test>
                         </subUserCreator1>
			 <subUserCreator2>
			   <autoCreateUser>
				  <roles>
					<role>User</role>
				  </roles>
				  <defaultRole>User</defaultRole>
				  <updateableByUser>true</updateableByUser>
				</autoCreateUser>
                         </subUserCreator2>
	</scheme>
    </configuration>
  </target>
</targets>

Step 6: Running and testing the new scheme

Now we are ready to test our new scheme! Restart the repository server and the daisy wiki.
Try to log on to daisy with any username/password combination which should have permissions to access one of the files at either FileLocation1 or FileLocation2.

Log in should be successfull, you should be logged on with the role defined in the myconfig.xml configuration file. Login as an administrator, invoke the user administration. In the user list, an account should exist with the username you just logged on as. Also, if you create a new user or edit an existing user, in the drop-down box for the authentication scheme, you now should have the choice between the daisy built in scheme and the scheme we newly created.

It's worth noting a couple of points:

if a user can access both files at FileLocation1 and FileLocation2 they don't get both sets of roles
the roles associated with FileLocation1 and subUserCreator1 are checked before FileLocation2 and subUserCreator1

Best of luck getting it to work. A working example is provided here (application/octet-stream, 11.4 kB, info).

Java's not my strong point; I'd never coded in it before tying this. I'm sure that there's a better way of structuring this code, possibly involving passing arrays of FileLocations and subUserCreators from the authentication factory to the authentication scheme. Please leave some hints. :)

Display images in a query using query-styling

Objective

This article is about displaying a query-based table of images within a daisy installation for the visual selection of pictures.

Background

Once daisy is accepted by those working with it (in our case a company using it for background info and end-user documentation), a lot of pictures get uploaded ("a pictures makes up for a thousand words"). Even when there are naming-conventions, the picture's names usually only make sense to those who uploaded them.

Since re-using a picture in several pages does not only make sense, but is the only way for easing the exchange of e.g. a company logo easily across all documents, we encountered the need to be able to query for all pictures in the system including their thumbnail to have a visual choice of pictures..

The problem is that pictures cannot be displayed within a query using a standard daisy installation. Luckily the query may be "styled" manually.

The following day-to-day notation is what this document aims to do:

select name, link, image_thumbnail from my_daisy

i.e. Select all names, links and the image thumbnail from a daisy installation and display them as a table.

Credits:
Info, code and ideas for this document provided by Júlio, Karel and Paul on daisy's mailing list.

How it's done

Since daisy does not support querying for pictures, the trick is to add an option to the query with a style hint that is picked up by daisy and results in the display of the pictures rather than only the name and link of the picture.

Since daisy automatically generates a preview and a thumbnail from every picture added to the system, one of these want to be displayed.

The file handled is the one sitting in daisy's default template:

PATH_TO_DAISY/daisywiki/webapp/daisy/resources/skins/default/query-styling/query-styling-html.xsl

Copy this to your skin (create the folder, if not there):

PATH_TO_YOUR_SKIN/query-styling/

You will find the style-hint "bullets" already defined, we will add the the two query styles

image-preview
image-thumbnail

Adding the Code

Before you start adding the code, find out which partIDs your thumbnails and previews have in you system.

Finding the Part Type of the Preview and the Thumbnail

You will need to hard-code the partIDs for your preview and thumbnail pictures. Go to your administration page, choose Part Types and note the IDs for the image preview and its thumbnail. In our case:

12	ImagePreview	false	view/edit \| delete
11	ImageThumbnail	false	view/edit \| delete

This should apply all systems that have not been tweeked.

Code to add to query-styling-html.xsl

Júlio came up with the idea of using the same template for previews and thumbnails (a bit smaller and faster to load than previews.)
Therefore two templates are added that simply set some variables and then call the template that sorts out the rest.
This is it:

<!--image-preview-->

<xsl:template match="d:searchResult[@styleHint='image-preview']">
  <xsl:call-template name="tabular-results-with-image">
    <xsl:with-param name="partId" select="12"/>
    <xsl:with-param name="imageTitle" select="'Preview'"/>
  </xsl:call-template>
</xsl:template>


<!--image-thumbnail-->
<xsl:template match="d:searchResult[@styleHint='image-thumbnail']">
  <xsl:call-template name="tabular-results-with-image">
    <xsl:with-param name="partId" select="11"/>
    <xsl:with-param name="imageTitle" select="'Thumbnail'"/>
  </xsl:call-template>
</xsl:template>

<!--used by image-thumbnail and image-preview-->
<xsl:template name="tabular-results-with-image">
  <xsl:param name="partId"/>
  <xsl:param name="imageTitle"/>
  <table class="default">
    <!--table header-->
      <tr>
        <th><xsl:value-of select="$imageTitle"/></th>
        <xsl:for-each select="d:titles/d:title">
          <th><xsl:value-of select="."/></th>
        </xsl:for-each>
        <th><i18n:text key="searchresult.actions"/></th>
      </tr>

    <!--table body-->
    <xsl:for-each select="d:rows/d:row">
      <tr>
        <xsl:variable name="hrefSuffix">
          <xsl:if test="@branchId != $siteBranchId or @languageId !=$siteLanguageId">
            <xsl:value-of select="concat('?branch=', @branchId, '&amp;language=', @languageId)"/>
          </xsl:if>
        </xsl:variable>
        <!--image-->
          <td>
            <img src="{@documentId}/version/last/part/{$partId}/data{$hrefSuffix}"/>
          </td>
        <!--other fields-->
        <xsl:for-each select="d:value|d:xmlValue|d:multiValue|d:linkValue|d:hierarchyValue"> 
          <td>
            <xsl:apply-templates select="."/> 
          </td>
        </xsl:for-each>
        <!--action link-->
        <td><a href="{$searchResultBasePath}{@documentId}.html{$hrefSuffix}"><i18n:text key="searchresult.action-show"/></a></td>
      </tr>
    </xsl:for-each>
  </table>
</xsl:template>

If you want to use the "i18n" tags, you will need to tell daisy what to do with them, by adding the following code at the top section of the xsl file (right under xmlns:d="http://outerx.org/daisy/1.0").

xmlns:i18n="http://apache.org/coccon/i18n/2.1"

If you want to change the order, eg. have the thumbnail at the end of the table, you simply take the image part and put it at the end.

Making your changes visible to Daisy

Daisy won't automatically notice changes to documents inside the <skin>/query-styling directory, so one way of letting Daisy know you've changed the query styling is:

Make sure you have a <skin>/searchresult.xsl file. If you haven't created one for your skin, copy the default searchresult.xsl file from daisy-<X.Y>/daisywiki/webapp/daisy/resources/xslt
Change the searchresult.xsl file. All you need is to change the file's timestamp, and Daisy will pick up the changes to all files inside /query-styling. You can type the command touch searchresult.xsl in your Daisy server's Un*x shell, or re-upload a local copy of searchresult.xsl via FTP.

Remember to 'touch' searchresult.xsl everytime you change the query styling, or the changes won't be applied until the next time Daisy is reset.

Using style-hints

Once you have set up the file, you can start using the style-hints. Below are two examples, each using one of the introduced style-hints.

select name, id, language where documentType='Image' and languageId = '2' order by name option style_hint = 'image-preview'

select name, id where documentType='Image' and languageId = '3' order by id option style_hint = 'image-thumbnail'

Wiki

New document browser

New document browser

Concept

Layout ideas

Mockups

Additional requirements (not visible in current mockups):

Creating a multi role authentication scheme

Creating a multi role authentication scheme

Step 1: Checking out the sources

Step 2: Copy the sources of the Ntlm-authentication

Step 3: Create the java classes for authentication

Step 3a: Rename the existing sourcefiles for AuthenticationFactory and AuthenticationScheme

Step 3b: Edit NTLMGroupAuthenticationFactory.java

Step 3c: Edit NTLMGroupAuthenticationScheme.java

Step 4: Building the authentication scheme

Step 4a: Compiling and packing your classes

Step 4b: Copying the jar-file into place

Step 5: Registering and configuring the new component

Step 5a: Registering the new component

Step 5b: Configuring the new component

Step 6: Running and testing the new scheme

Links

Display images in a query using query-styling

Display images in a query using query-styling

Objective

Background

How it's done

Adding the Code

Finding the Part Type of the Preview and the Thumbnail

Code to add to query-styling-html.xsl

Making your changes visible to Daisy

Using style-hints