compared with
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (4)

View Page History

h3. Used business h1. Business terms and abbreviations

|| *Term* || *Description* ||

h3. Use Cases
h1. Req Items
Requirements for semantic search, based on the [Search Spec 201107] and requirements for FTS and search results based on the ResearchSpace Specification.

| | | *Semantic search* \| |
| 05.SEMSEARCH.R1 | RS3 | It should be possible to indicate the datasets (by namespace) to be included in a search either by choosing those that should be included or excluded. Tools should be available for making selection and clearing of selections straight forward. |
| 05.SEMSEARCH.R2 | RS3 | Users should be able to save their selections for other sessions. |
| 05.SEMSEARCH.R3 | RS3 | The system should allow users to type a search term and for authorised terminology to be suggested as each letter of the search is typed, if the string is contained within a term. |
| 05.SEMSEARCH.R4 | RS? | There is a possibility that synonym (and other helper features) functional could also be included. |
| 05.SEMSEARCH.R5 | RS? | The system should be capable of being configured so that the system only draws upon a certain level of terminology (or all) in a hierarchy (e.g. configuration so that a search will only find potential terms at the first or second levels of a thesaurus with multiple levels of narrower terms). However, the search itself could be configured to use the narrower terms of the term selected. |
| 05.SEMSEARCH.R6 | RS3 | There should be an opportunity for the user to consult an authority list or thesauri hierarchy directly if they are unable to find the correct term through the suggestion system above. |
| 05.SEMSEARCH.R7 | RS3 | Search results should be categorised according to the fundamental categories above. (Results should belong to a class reflecting these categories either directly or through a sub class.) |
| 05.SEMSEARCH.R8 | RS3 | The number of results should be indicated against each category. |
| 05.SEMSEARCH.R9 | RS3 | It should be possible to explore data by using the Fundamental Relationships between different categories. For example, a thing may have a relationship with an actor, which will relate to a place or period which may then relate to other things. The interface should provide the ability to explore in this flexible manner. |
| 05.SEMSEARCH.R10 | RS? | The tool should be configurable to work with other CRM data implementations outside ResearchSpace. For example, it should be possible for the tool to be used on the British Museum’s Collection Online system (COL), if COL data complied with CIDOC-CRM and used RDF. |
| 05.SEMSEARCH.R11 | RS? \\ | The tool should be compatible with co-referencing resources where terminology is mapped across different organisations vocabularies. |
| 05.SEMSEARCH.R12 | RS? \\ | It must be possible to extract data and links from results data for use in other tools and environments. The ResearchSpace environment requires that results be used in other tools and that there be a data and information exchange with the ResearchSpace collaborative environment. |
| | | *Text Searching Component* |
| 21.TXTSEARCH.R1 | RS3 | Text search should be performed on the following resources |
| 21.TXTSEARCH.R1-1 | RS3 | \-          The shared ResearchSpace RDF repository |
| 21.TXTSEARCH.R1-2 | RS3 | \-          The project RDF repository |
| 21.TXTSEARCH.R1-3 | RS3 | \-          The Content Management System -- (Social networking data) |
| 21.TXTSEARCH.R1-4 | RS3 | \-          The Content Management System -- Document & Asset Libraries |
| 21.TXTSEARCH.R2 | RS3 | Text searching is limited by user security access and to the repositories that are available to the user. A project team member can search their own project store and the shared research project store. The results must indicate which store the data refers to. |
| | | *Search Result* |
| 05.SEMSEARCH.R13 | RS3 | Summary results should be a thumbnail and the following fields |
| 05.SEMSEARCH.R14 | RS3 | Results should include the remaining information about an object organised according to the original source data and then the annotation and versions of data below. |
| 05.SEMSEARCH.R15 | RS3 | Users should be able to mark records for other research tools. For example, create a basket of data records for timeline or geographical mapping. |
| 05.SEMSEARCH.R16 | RS3 | From the search tool the relevant research tools should be available for launch |

h1. Use Cases

The UCs for Semantic Search and Full Text Search are used by the researchers to search the RS project space for  data objects, documents and discussions.