Changes between Version 5 and Version 6 of SearchContext
- Timestamp:
- 08/29/11 12:53:30 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
SearchContext
v5 v6 44 44 45 45 Resource not accessible :: 46 The critical part is, how to handle situations, where the Resource is not accessible at all (i.e. irrespectively of access-rights)?46 The critical question is, how to handle situations, where the Resource is not accessible at all (i.e. irrespectively of access-rights). 47 47 This is often the case for written corpora, where the individual texts of the corpus are not available directly. 48 Possible solutions: 48 Optimally this situation shouldn't arise at all - if there is Metadata-record it should contain a link to the resource (or any sensible proxy) and if the resource itself is not accessible (like a piece of text in a big text-corpus), it shouldn't be announced by a separate MD-Record to the outer world at all. 49 But if it still occurs, possible solutions are: 49 50 * Link to the MD-Record of the resource 50 * Link to the MD-Record of the collection 51 * If available Link to a part of the Resource that is available (Sometimes at least a bit bigger context-snippet around the keyword is available 52 53 51 * Link to the MD-Record of the parent collection 52 * Link to a part of the Resource that is available (Sometimes in a text-corpus at least a bit bigger context-snippet around the keyword is available.) 54 53 55 54 == Corpus as a Resource == 56 55 As mentioned in previous chapter (under ''Resource not accessible'') if individual items of a corpus are not accessible at all, they '''shouldn't''' be exposed via corresponding MD-Records. In such cases it seems more practical to provide '''just one''' MD-Record for the whole corpus, describing the corpus as whole, including coverage across various dimensions (time, space, genre) and linking to an endpoint, where the corpus can be searched in.
