Changes between Version 3 and Version 4 of CDMDC

Timestamp:

05/20/11 17:22:47 (13 years ago)

Author:

vronk

Comment:

intermediary work in progress revision with "Linking MD and Content"

CDMDC

@@ -1 +1 @@
 = Combined Distributed Metadata Content Search =
+(The related chapters in the [[source:FederatedSearch/docs/FederatedSearch.docx |FederatedSearch doc]] are ''4.6 Combined Metadata and Content Query'' and ''6.3 Combined Metadata Content Search''.)
+
 A combined metadata content search shall allow to restrict the context of the content search by metadata filters.
 Simple examples:
- Find all occurrences where a female Actor said “Ja”.
- 
+{{{
+ Find all occurrences where a female Actor said “Ja”. 
  Find all occurrences of “viable system” in texts where the Organisation responsible for the collection the text is part of is a university.
+}}}
 
 Generally it should be possible to formulate the whole query (both metadata and content part) in one query string (with the same CQL-syntax).
@@ -15 +18 @@
 [[Image(edc_interaction_mks.png)]]
 
-The main challenge seems to be a clear definition of '''how the metadata records are linked with the (endpoints of the) repositories/search engines'''.
-A basic solution is that the ResourceRef of the Collection MDRecord points to the endpoint of given search engine, but this seems to simplistic.[[BR]]
+== Linking MDRecords and Content Services ==
+The main challenge seems to be '''how to relate the metadata records with the (endpoints of the) repositories/search engines''', so that it is possible to map from a MD-result to the candidate repositories to search in.
+
+=== Variant 1: Collection's MDRecord points to the Content Service ===
+
+A basic solution is that the ResourceRef of the Collection MDRecord points to the endpoint of given search engine, but this seems to simplistic.
+
+=== Variant 2: Separate MDRecord `Repository`===
+Define a separate CMD-Profile '''Repository''' (see [[RepositoryRegistry#IdeasonimplementationoftheRegistry RepositoryRegistry]], that carries 
+ 1. the URL of the Content Service endpoint
+ 1. references to the MDRecords (`<ResourceRef>`) of Collections and/or Resources that are searchable via this Service
+ 1. any further technical information about the service
+
+It shouldn't carry any information about the content. That should be maintained separately in the MDRecords for the referenced Collections and Resources.
+
+
+=== Variant 3: Use Virtual Collection ===
+MD-Search could be packed as a virtual collection, sending only a reference of it to the content search.
+
 '''''TODO:''' This needs to be elaborated further.''
 
-(The related chapters in the [[source:FederatedSearch/docs/FederatedSearch.docx |FederatedSearch doc]] are ''4.6 Combined Metadata and Content Query'' and ''6.3 Combined Metadata Content Search''.)