Beta 1 indexer plans

This page lists summary task and progress notes for the beta 1 release of the MKSearch indexer component. This is an archive page.

HTML link element indexing

The current content handlers only process HTML meta elements. The latest Dublin Core in HTML recommendation also allows link elements to be used. This will require a new type of content handler and an XhtmlLinkFilter, ultimately composed into a general purpose XHTML metadata processor.

Task progress: Many of the original alpha classes have been refactored and new interfaces introduced to provide more flexible usage and integration.

• XhtmlLinkFilter completed.
• LinkTripleWriter completed.
• LinkRDFStoreWriter completed.
• Composite XhtmlTripleWriter completed.
• Composite XhtmlRDFStoreWriter completed.
• Full Dublin Core in HTML compatibility complete.

e-GIF compatibility

Currently the system only indexes Dublin Core namespace metadata. The content handlers must be extended to cover UK e-GIF Metadata Standard markup. This standard includes records management fields specified by the National Archives' Requirements for Electronic Records Management Systems, and is based on the e-GMS Application Profile Version 1. This will require an e-GIF com.mkdoc.schema.Schema and a new RDF store writer implementation.

Task progress:

• UKeGMS Schema class completed to e-GMS Application Profile Version 1 specification.
• Custom schema configuration introduced to the XhtmlTripleWriterPlugin class to enable e-GMS indexing. See Crawler development plans.
• Extended the test document Web site to include all e-GMS elements, refinements and encoding schemes.
• Custom schema configuration introduced to the XhtmlStoreWriterPlugin class to enable e-GMS indexing. See Crawler development plans.
• Full e-GIF compatibility complete.

Application profiles

The original indexing system used the Schema interface to expand metadata values to URIs. Extension methods were added to the interface to permit the type of mixed form used in the UK e-GMS schema, which shares elements with the Dublin Core element set and provides its own refinements. An ApplicationProfile interface is required to allow more flexible configuration and enable dynamic configuration of the Query component.

The ApplicationProfile interface will also need methods to iterate through all the predicates they contain to dynamically generate search forms in the Query component.

Task progress:

• Refactored the com.mkdoc.schema and com.mkdoc.sax packages to introduce the new ApplicationProfile interface.
• Introduced DublinCoreProfile and UKeGMSProfile classes in place of the former Schema types.
• Completed DublinCoreProfile and AbstractApplicationProfile.
• Completed UKeGMSProfile.
• Custom application profiles complete (indexing functions)

Beta 2 development plans

Incremental indexing

The current indexing process is driven by worker threads in the JSpider Web crawler and results in a new RDF repository for each crawl session. This will be satisfactory for development and testing purposes and may suit some production configurations, however incremental indexing will ultimately be required, so that "live" repositories can be updated while continuing to provide public query services. This development is co-dependent with more sophisticated repository management interfaces for the Triple Store component.

Beta 2 development plans

Incremental indexing

The current indexing process is driven by worker threads in the JSpider Web crawler and results in a new RDF repository for each crawl session. This will be satisfactory for development and testing purposes and may suit some production configurations, however incremental indexing will ultimately be required, so that "live" repositories can be updated while continuing to provide public query services. This development is co-dependent with more sophisticated repository management interfaces for the Triple Store component.