Changes between Version 2 and Version 3 of FCS-FeatureMatrix
- Timestamp:
- 05/29/11 15:51:52 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
FCS-FeatureMatrix
v2 v3 1 1 = FCS - Feature Matrix = 2 This is to list/summarize individual features that individual FCS-compliant search engines shouldimplement.2 This shall be a comprehensive list of individual features that every FCS-compliant search engine must/can implement. 3 3 They are discussed in detail in [[FCS-spec]]. 4 4 … … 6 6 7 7 ''Obviously the list is not complete. '''TODO:''' complete '' 8 9 10 [[FCS-spec#Explainoperation|explain response]] :: 11 Provide information about the configuration of the service, mainly about available indices and defaults. 12 13 ''We have to examine, if `explain`-record can be the single authoritative source of information about a repository.'' 14 15 8 16 9 17 == Query == … … 19 27 index relation searchTerm 20 28 }}} 29 30 See more about indices in next chapter. 31 32 supported relations :: 33 SRU proposes: 34 {{{ 35 any, adj, all 36 }}} 37 honor search context :: 38 Allow to restrict search to specific collections/resources specified as a parameter (see [[SearchContext]]) 39 {{{ 40 `?x-cmd-context` 41 }}} 21 42 boolean search :: 43 {{{ 44 AND OR PROX 45 }}} 22 46 23 search by ccs-indices :: 47 == Indices == 48 Indices are to be used in different operations. 49 * `search` 50 * `scan` (/`aggregate`) 51 * `output` (/`group`, /`sort`) 24 52 25 search by isocat-indices :: 53 This needs to be explicated in the description of the repository. 26 54 27 honor search context :: 28 Allow to restrict search to specific collections/resources specified as a parameter (`x-cmd-context` - but [[SearchContext|under discussion]] yet) 55 Types of indices: 29 56 30 == search result == 57 ccs-indices :: 58 isocat-indices :: 59 supporting index-search on `isocat` data categories. 60 search by cmd-indices? :: 61 content search supporting also MD-filters 62 63 We should agree on some basic set of MD-indices, at least for `output` that "should" be implemented would make life easier to software and users. Hot candidates are: 64 * title/name (default string representation of the resource) 65 * language 66 * resource-type 67 * creation/publication date 68 * or simply inspire by the VLO-facets 69 70 == Search Result == 31 71 provide resource reference :: 32 72 `Resource@pid` … … 39 79 provide link to CMD-metadata :: 40 80 Fill ccs:Metadata@cmd-link with reference to CMD-record. 81 provide CMD-metadata :: 82 alternatively resolve and embed the CMD-record 83 {{{ 84 <ccs:Metadata><cmd:CMD> 85 }}} 41 86 42 87 == supporting operations == 43 88 44 [[FCS-spec#Explainoperation|explain response]] ::45 Provide information about the configuration of the service, mainly about available indices and defaults.46 47 89 scan indices :: 48 90 implement `scan`-operation allowing to query the terms available in individual indices