Changes between Version 7 and Version 8 of CDMDC


Ignore:
Timestamp:
05/29/11 20:52:52 (13 years ago)
Author:
vronk
Comment:

adding == Querying metadata indices ==

Legend:

Unmodified
Added
Removed
Modified

  • CDMDC

    v7 v8  
    101101MD-Search could be packed as a virtual collection, sending only a reference of it to the content search. The overhead of creating a VC seems justified mainly when reuse and sharing of the selection/query is intended.
    102102
     103== Querying metadata indices ==
     104''section being written''
     105
     106We have metadata fields in the MD-Records. These can be searched in the MDRepository.
     107And we have metadata fields that the content search allows to query directly.
     108
     109Basic example: wanting to search in Resources of a specific language.
     110This can be simply encoded in the Collection-MDRecord, for all the member resources,
     111so the MD-Result would be the Collection-MDRecord (with appropriate Repository attached)
     112
     113Another repository could serve resources of different languages and expose `language` as MD-filter.
     114Then we would pass the language-parameter to the repository.
     115The Repository-MDrecord (or the `explain`-record) would inform, that it exposes given index.
     116
     117How to avoid confusion? Probably try to handle this transparently for the user,
     118meaning that SHe does not have to bother where which index applies.
     119That means that the CDMDC-component has to do the maths (routing the MD-query correctly, mapping between equivalent indices).
     120