Changes between Version 18 and Version 19 of DiscoveryComponents


Ignore:
Timestamp:
29/04/10 13:15:34 (9 years ago)
Author:
mpritcha
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DiscoveryComponents

    v18 v19  
    2424 
    2525=== Publishing === 
    26    The act of putting metadata records in a system that exposes them for external access over the internet. This is done using OAI, a software toolkit installed at each Data provider site. A data provider would have the "OAI Provider" function of this software installed, which simply exposes a collection of metadata records in a standard way, ready for harvesting. Each data provider is in control of his/her OAI Provider software and should register the details of their "node" using the "OAI Admin interface". 
     26   The act of putting metadata records in a system that exposes them for external access over the internet. This is done using OAI, a software toolkit installed at each Data provider site. A data provider would have the "OAI Provider" function of this software installed, which simply exposes a collection of metadata records in a standard way, ready for harvesting. Each data provider is in control of his/her OAI Provider software and should register the details of their "node" using the [#OAIAdminInterface OAI Admin interface]. 
    2727 
    2828=== OAI Admin Interface === 
     
    3636 
    3737=== Discovery Web Service === 
    38    A piece of software run alongside the discovery database, which offers a "presentation-less" service to handle search requests. On receipt of an appropriately-constructed XML message from the '''search interface''', it will carry out a search of the discovery database and construct a search response message, which is sent back to the search interface. Similarly, it also handles requests for returning specific documents in the database : a request is received as an XML message (via SOAP), and an appropriate response is sent back to the sender. In all cases, messages (request/response) are exchanged in XML via SOAP, with all presentational formatting handled by the search interface (which itself may be part of a 3rd party web portal). 
     38   A piece of software run alongside the discovery database, which offers a "presentation-less" service to handle requests for the execution of a search, or for the retrieval of a document. On receipt of an appropriately-constructed (as defined by the [#WSDL WSDL]) XML message from the [#SearchInterface search interface], it will carry out a search of the discovery database and construct a search response message, which is sent back to the search interface. Similarly, it also handles requests for returning specific documents in the database : a request is received as an XML message (via SOAP), and an appropriate response is sent back to the sender. In all cases, messages (request/response) are exchanged in XML via SOAP, with all presentational formatting handled by the search interface (which itself may be part of a 3rd party web portal). 
     39 
     40=== WSDL === 
     41Web Service Description Language : typically there will be a document describing in machine-readable form the operations that a service is capable of performing, and the required XML structure of the request and response messages for each of these operations. 
    3942 
    4043=== Search Interface === 
    41    A web application consisting of tools to enable a user to define a search to be sent to the discovery web service. At its simplest, this could be a simple text box and submit button, but may have more sophisticated tools such as click-and-drag map tools to define a region of interest, calendar tools to define dates/times, and in some cases may include tools to select terms from '''controlled vocabularies'''. Lists of these terms may be populated by calls (similar to the search request/response messages) to a '''vocab server'''. 
     44   A web application consisting of tools to enable a user to define a search to be sent to the discovery web service. At its simplest, this could be a simple text box and submit button, but may have more sophisticated tools such as click-and-drag map tools to define a region of interest, calendar tools to define dates/times, and in some cases may include tools to select terms from [#ControlledVocabulary controlled vocabularies]. Lists of these terms may be populated by calls (similar to the search request/response messages) to a [#VocabServer vocab server]. 
    4245 
    4346=== Web Portal ===