wiki:ExternalProductDefinition

Version 7 (modified by hsnaith, 13 years ago) (diff)

--

Following from the All Hands meeting on 4 October 06, we have a further definition of the "External Products" that NDG will / should / might generate. This definition will feed into development of the packages / package delivery and also helps define the documentation needed

The Core NDG components and User components of the page below are as before. The DataProviderProducts is primarily focussed on trying to divide the exisitng developments into sensible grouping dependant on what an NDG partner - at whatever level - might need to put in place.

Components of NDG

  • Discovery
  • MOLES browse
  • Delivery Service
  • DX
  • GeoSPlAT
  • Vocabulary/term Server

Core NDG Services – run by “NDG”

  • Discovery web service
    • GUI interface to discovery
    • Runs on SuperGlue
  • MOLES Browse web service
    • BNL thinks not ... this should be a DP thing ...
  • Term server
    • Runs on a BODC system

Documentation:

  • Configuration

“Central” Dx / GeoSPlAT GUI??

  • BNL thinks not ... ... this is a service binding issue really, which dx service is bound to a data object by default should be the "local" one ... but a dx ought to be able to take a uri, and use it anyway ... but that would involve the delivery service ...

Data provider

There are a number of levels of data provider engagement ... beginning with simply providing data behind a delivery service and/or simply providing a directory of data objects available. A full NDG data provider will provide the entire set of services. DataProviderProducts has more on this.

Data Provider - Discovery

  • Generate D ( how: a full partner will do it from MOLES, others will do it how they like )
  • Maintain D in OAI repository
  • Make OAI repository

Required Software:

  • Dlese database
  • For discovery alone there is no requirement for NDG security.

Tools:

Schema:

  • D: currently DIF, soon to be ISO19139. Need to consider which flavour(s).

Documentation:

Useful stuff:

  • Example D from a variety of sources
  • Code repository for generation of DIFs from MySQL / Oracle etc BNL don't think this is the way to go
  • HMS - Code repository for generation of DIF from MOLES instead?

How do you get at data found in repository if DP is not also a full data provider?

Data provider – MOLES

  • Generate MOLES records
  • Maintain MOLES records (in what? Does it matter? BNL: in exist, yes it matters, to deploy browse software need to have it in exist)

Required Software:

  • NDG security – all or subset? Just role mapping? Anything?

Tools:

Schema:

  • MOLES
  • StubB

Documentation:

Useful stuff:

  • Example MOLES - of all types from different data centres
  • Code repository for generation of MOLES from CSML / standard data formats

Some Questions

  • How do you get at data found in MOLES if DP is not also a full data provider?
  • Do you have to be discovery provider if you’re a MOLES provider?

Data Provider – Data Server

  • Generate CSML instances
  • Serve CSML instances to required services
  • Deliver Data – by DX and/or simple file access?

Required Software:

  • NDG security

Tools:

  • CSML Scanner
  • CSML Parser

Documentation:

Useful stuff:

  • example CSML for a variety of sources

Some Questions

  • Do you have to be Discovery and / or MOLES to be full data provider in NDG?
  • Do you have to run a local DX to be a full data provider

Data provider – local DX & GeoSPlAT

Required Software:

Tools:

Schema:

Documentation:

Useful stuff:

Data Provider – portal/GUI

  • Discovery portal – integrate a discovery search widget into your own data web page
  • Browse portal – run a browse interface with your own branding

Required Software:

Tools:

  • the default browser code & style sheets for implementation

Schema:

Documentation:

Useful stuff:

and don't forget the user!

Required Software:

  • a browser - what are minimum specs?

Documentation:

  • primarliy need to provide info buttons on the browse etc