Version 2 (modified by lawrence, 12 years ago) (diff)


19th November 2009

To discuss the refactoring out of the MILK codebase.


V1.0 Will consist of

  • (D) discovery client (to the discovery service),
  • (B) browse client to
    • MOLES V1.3 (deprecated)
    • MOLES V2 (recommended)
  • (M) management client to
    • MOLES v2 (allowing editing, creation, publishing etc)
  • (X) xml access to
    • MOLES V1.3 content
    • MOLES V2 content
    • atom feeds from MOLES V2
    • an atom feed of Discovery documents (currently DIF, moving to ISO)

where the underlying xml content is held in an eXist database.

Any deployment of MILK will allow any of the top level (D,B,M,X) to be turned off in the configuration.

Normal deployment might include one of the following:

  • a standalone discovery client (e.g. the NERC data discovery portal)
  • a complete metadata portal (e.g. for CEDA) would have
    • an eXist database visible only inside a firewall
    • a MILK instance with D,B,X outside the firewall
    • another MILK instance with D,B,X,M inside the firewall
  • a complete metadata portal (e.g. for BODC or PML) might have
    • an eXist database visible only inside the firewall
    • a MILK instance with B,X and maybe D outside the firewall
    • another method of creating MOLES content and loading it into the eXist database and managing it.

It is desirable that WMS and WCS clients being developed as part of NDG3 also be integrated, but that's being parked as an issue, pending formulation of an appropriate hand over format (once called a shopping cart format, now called a Web Map Context document).

Software: Meetings (081001,081020,081031,081119)

NDG3: Capability, Discovery, Vocab, Software, MOLES, Security, Community, Roadmap