Expanding the administration section

In Daisy's administration section it is currently possible to administrer collections, users, document types, ACLs and so forth. However the web based administration is far from complete.

Sites

A Daisy instance can have any number of sites. These sites typically have a homepage, navigation, skin, ... Currently administrators must have shell access to the hosting server to create and configure sites. Creating sites can be done by creating a number of directories and files or by calling a script which pretty much does the work for you. Typically when admins wish to modify sites they will edit xml files.

A nice addition to the administration frontend would be the administration of Daisy sites. Administrators should then be able to create update and delete sites. A basic implementation would be to allow the admins to edit settings found in the siteconf.xml and skinconf.xml. Should you finish this quickly and still feeling frisky then you might also have a shot at the faceted browser configurations found in the site. Each 'browser' if configured or defined by a single xml file. This file is used to specify which facets apply, what the default conditions are, which styling can be used, etc.

Import/Export

Recently Daisy has been improved to be able to make exports and import documents from other repositories. Again administrators would need shell access to do the export and import actions.
Typically the administrator would want to be able to specify which documents would need to be exported/importend and with which options. If you are interested in what the current possibilities are have a look here or here.

If you are up for the task you'll be getting your hands dirty with

• Daisy wiki frontend.
• cocoon. The forms framework cforms to be more specific.
• xml, xsd and how to process them.