Maria Todorova
Business terms and abbreviations
Term | Description |
---|---|
FCs | Fundamental Categories. The FCs are Thing (Artwork), Actor (Artist) , Place, Event, and time thereby incorporating the classic When, What, Where and Who. We broaden the FCs with Support Materials, Techniques and Object Types |
FRs | Fundamental Relations. The FRs are 1. "has type: denotes relations to a classification, category, type, essential role or other property, such as a format, material, color. The relationship is applicable to all FCs and has always range Concept. 2. is part of: denotes structural relations of an item to a wider unit it is contained in. The relationship is applicable to all FCs, except for Concept. In case of Actors, one would rather speak of “is member of”, and persons are the minimal elements. Domain and range must be identical. 3. is similar or the same with: denotes the symmetric relation between items that share features or are possibly identical. It is only usual for Things to document similarity manually. There exist enough comparison algorithms that deduce degrees of similarity automatically. We do not deal with these in this work. 4. has met: denotes the symmetric relation between items that were present in the same event, including time intervals and places. Applicable to any combination of FCs, except for Concepts. 5. from, has founder or has parent: denotes the relations of an item to constituents of a context in its history which is either significant for the item, or the item is significant for the context, “provenance” in the widest sense, including time intervals and places. In case of genealogy or group formation, natural language prefers the terms parent and founder respectively in order to refer to Actors. The relationship is a special case of has met. The applicability is analyzed in Table 1. 6. is origin of, founder of, parent of: the inverse of from, has founder or parent. In case of Actor as domain, one would rather speak of “is provider or creator of “ 7. at: denotes the relation of an Event to the Time and Place within which the event happened. 8. refers to: denotes the relation of an item that is information, contains information or has produced information to the item this information refers to or is about. The relation can even be extended to a Place from where such information originated. 9. is referred by/ is referred to at: the inverse of refers to. (TBD: The list to be updated with the rest fundamental relations) |
FTS |
Full Text Search |
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 |
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.
Diagram 05.1 Use Case Diagram
05.SSUC01: Advanced Semantic Search
Preconditions:
|
05.SSUC01.R1 | The user has permissions to perform Advanced Semantic Search. (The user is not with the roles of Collaboration Team Member or Project Observer) |
Constraints:
|
05.SSUC01.R2 | The search is performed only in project datasets (named graphs) to which the user has access. |
Transitions: No
Initiating operation/ button: Advanced Semantic Search
GUI:
Main Menu Bar/ Advanced Semantic Search- Project Dashboard/ Advanced Semantic Search tab
Description:
DO: This specification would need an overall description of the search function to make sense. You need an overall view of how the search system will work before you can split it into individual items.
|
05.SSUC01.R3 | RS3.1 |
When the user selects Advanced Semantic Search button a screen opens where the user captures different search criteria. |
05.SEMSEARCH.R1 | 05.SSUC01.R4 | “Project Dataset” Search Criteria | |
05.SEMSEARCH.R1 | 05.SSUC01.R4-1 |
|
|
05.SEMSEARCH.R1 | 05.SSUC01.R4-2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
05.SEMSEARCH.R1 | 05.SSUC01.R4-6 |
|
|
05.SSUC01.R4-7 |
|
||
|
05.SSUC01.R5 | “Object Type” search criteria | |
|
05.SSUC01.R5-1 |
|
|
05.SEMSEARCH.R3 | 05.SSUC01.R5-2 |
|
|
05.SEMSEARCH.R6 | 05.SSUC01.R5-3 |
|
|
|
05.SSUC01.R5-4 |
|
|
|
05.SSUC01.R5-5 |
|
|
05.SEMSEARCH.R7 05.SEMSEARCH.R9 |
05.SSUC01.R5-6 | RS3.1 |
|
|
05.SSUC01.R5-7 | RS3.1 |
|
|
05.SSUC01.R6 | RS3.1 |
“Artists” Search Criteria (TBD: What is the proper label name: Artist, Creator, Actor, Author) |
|
05.SSUC01.R6-1 | RS3.1 |
|
05.SEMSEARCH.R3 | 05.SSUC01.R6-2 |
|
|
05.SEMSEARCH.R6 | 05.SSUC01.R6-3 |
|
|
|
05.SSUC01.R6-4 |
|
|
05.SEMSEARCH.R7 05.SEMSEARCH.R9 |
05.SSUC01.R6-5 | RS3.1 |
|
|
05.SSUC01.R6-6 | RS3.1 |
|
|
05.SSUC01.R7 | RS3.1 |
“Places” Search Criteria |
|
05.SSUC01.R7-1 | RS3.1 |
|
05.SEMSEARCH.R3 | 05.SSUC01.R7-2 |
|
|
05.SEMSEARCH.R6 | 05.SSUC01.R7-3 |
|
|
|
05.SSUC01.R7-4 |
|
|
05.SEMSEARCH.R7 05.SEMSEARCH.R9 |
05.SSUC01.R7-5 | RS3.1 |
|
|
05.SSUC01.R7-6 | RS3.1 |
|
|
05.SSUC01.R8 | |
“Time Period” Search Criteria |
|
05.SSUC01.R8-1 | |
|
|
05.SSUC01.R8-2 | |
|
|
05.SSUC01.R8-3 | |
|
|
05.SSUC01.R8-4 | |
|
|
05.SSUC01.R8-5 | |
|
|
05.SSUC01.R8-6 | |
|
05.SEMSEARCH.R7 05.SEMSEARCH.R9 |
05.SSUC01.R8-7 | |
|
|
05.SSUC01.R9 | RS3.1 | “Support Material” Search Criteria |
|
05.SSUC01.R9-1 | RS3.1 |
|
05.SEMSEARCH.R3 | 05.SSUC01.R9-1 |
|
|
05.SEMSEARCH.R6 | 05.SSUC01.R9-2 |
|
|
|
05.SSUC01.R9-3 |
|
|
05.SEMSEARCH.R7 05.SEMSEARCH.R9 |
05.SSUC01.R9-4 | RS3.1 |
|
|
05.SSUC01.R9-5 | RS3.1 |
|
05.SSUC01.R10 | RS3.1 | "Technique" Search Criteria |
|
05.SSUC01.R10-1 | RS3.1 |
|
|
05.SEMSEARCH.R3 | 05.SSUC01.R10-2 |
|
|
05.SEMSEARCH.R6 | 05.SSUC01.R10-3 |
|
|
05.SEMSEARCH.R7 05.SEMSEARCH.R9 |
05.SSUC01.R10-4 | RS3.1 |
|
05.SSUC01.R10-5 | RS3.1 |
|
|
|
05.SSUC01.R11 | RS3.1 | The search result is a section of all search criteria entered. |
|
05.SSUC01.R12 | RS3.1 | There are 3 views that will be supported for the search result: |
05.SEMSEARCH.R13 | 05.SSUC01.R13 | RS3.1 | Lightbox View of Search Result |
|
05.SSUC01.R13-1 | RS3.1 |
|
|
05.SSUC01.R13-2 | RS3.1 |
|
|
05.SSUC01.R13-3 |
|
|
05.SSUC01.R13-4 |
|
||
|
05.SSUC01.R14 | RS3.1 | Details View of the Search Result |
|
05.SSUC01.R14-1 | RS3.1 |
|
|
05.SSUC01.R14-2 | RS3.1 |
|
|
05.SSUC01.R14-3 |
|
|
05.SSUC01.R14-4 |
|
||
|
05.SSUC01.R15 | RS3.1 | Timeline View of the Search Result |
|
05.SSUC01.R15-1 | RS3.1 |
|
|
05.SSUC01.R15-2 | RS3.1 |
|
|
05.SSUC01.R15-3 | RS3.1 |
|
|
05.SSUC01.R15-4 | RS3.1 |
|
|
05.SSUC01.R16 | RS3.1 | The search result is faceted according to the following categories: Object Type, Artist, Place, Time. Technique and Support Material categories will be additionally used only for Paintings. Facets are multi-valued, eg Material includes both painting support and frame material. Facets must include all hierarchical thesaurus values, so eg a painting in Amsterdam is also counted in Netherlands |
05.SEMSEARCH.R8 | 05.SSUC01.R16-1 | RS3.1 |
|
|
05.SSUC01.R16-2 | RS3.1 |
|
|
05.SSUC01.R16-3 | RS3.1 |
|
Post-Conditions
|
05.SSUC01.R17 | RS3.1 | All object records, which respond the entered search criteria are found and displayed. |
|
05.SSUC01.R18 | When an object record from the search result is selected by the user, then full object record details could be reviewed. See UC 06.DAUC01: View Object Record. | |
|
05.SSUC01.R19 | The user could save the search details. See UC 05.SSUC02: Save Search |
05.SSUC02: Save Search
Preconditions:
|
05.SSUC02.R1 | UC 05.SSUC01: Advanced Semantic Search has been performed. |
Constraints:
Transitions: No
Initiating operation/ button: Save Search
GUI:
Main Menu Bar/ Advanced Semantic Search- Project Dashboard/ Advanced Semantic Search tab
Description:
05.SEMSEARCH.R2 | 05.SSUC02.R2 | When the user selects Save Search button a screen opens where the user enters in free text fields the name of the search | |
05.SEMSEARCH.R2 | 05.SSUC02.R3 | The system saves the search criteria, entered by the user, and he could later reuse them. | |
05.SEMSEARCH.R2 | 05.SSUC02.R4 | The search result is not saved, because it could be changed later on. |
Post-Conditions
05.SEMSEARCH.R2 | 05.SSUC02.R5 | The search is saved and could later be reused by the user. |
05.SSUC03: Open Saved Search
Preconditions:
|
05.SSUC03.R1 | UC 05.SSUC02: Saved Search has been performed and there is successfully saved search. |
Constraints:
Transitions: No
Initiating operation/ button: Select Search
GUI:
Main Menu Bar/ Advanced Semantic Search- Project Dashboard/ Advanced Semantic Search tab
Description:
05.SEMSEARCH.R2 | 05.SSUC03.R2 | When the user selects Open Saved Search button a list is displayed with all saved by the user searches. | |
05.SEMSEARCH.R2 | 05.SSUC03.R3 | The user could view only searches saved by himself. | |
05.SEMSEARCH.R2 | 05.SSUC03.R4 | The user could select a search from the list and to repeat the search again. |
Post-Conditions
05.SEMSEARCH.R2 | 05.SSUC03.R5 | The Search Criteria are filled in with the saved search criteria and user could perform exactly the same search again. |
05.SSUC04: Delete Saved Search
Preconditions:
05.SEMSEARCH.R2 | 05.SSUC03.R1 | UC 05.SSUC02: Saved Search has been performed and there is successfully saved search. |
Constraints:
Transitions: No
Initiating operation/ button: Delete Search
GUI:
Main Menu Bar/ Advanced Semantic Search- Project Dashboard/ Advanced Semantic Search tab
Description:
05.SEMSEARCH.R2 | 05.SSUC04.R2 | When the user selects Select Search button a list is displayed with all saved by the user searches. | |
05.SEMSEARCH.R2 | 05.SSUC04.R3 | The user could view only searches saved by himself. | |
05.SEMSEARCH.R2 | 05.SSUC04.R4 | Next to each saved search in the list, there is a button "Delete" and the user could select a search from the list and delete it. |
Post-Conditions
05.SEMSEARCH.R2 | 05.SSUC04.R5 | The saved search is deleted and is no longer in the list with saved searches. |
05.SSUC05: Full Text Search
Preconditions:
Constraints:
Transitions: No
Initiating operation/ button: Main Menu Bar/ Search
GUI:
- Search field in the Main Manu Bar
- Project Dashboard/ Advanced Semantic Search tab
Description:
21.TXTSEARCH.R1 | 05.SSUC05.R1 | FTS is performed over all documents, discussions, etc. and all over the semantic repository with data objects. | |
21.TXTSEARCH.R1-1 | 05.SSUC05.R1-1 |
|
|
21.TXTSEARCH.R1-2 | 05.SSUC05.R1-2 | RS3.1 |
|
21.TXTSEARCH.R1-3 21.TXTSEARCH.R1-4 |
05.SSUC05.R1-3 |
|
|
21.TXTSEARCH.R1 | 05.SSUC05.R2 | If the user performs FTS while working on a specific Research Project then the dataset (named graph) is set by default to the current research project and the user will search only data objects from the current project | |
21.TXTSEARCH.R1 | 05.SSUC05.R3 | If the user performs FTS while on his personal dashboard, then the dataset user will be able to search between all data objects from all projects to which he has access plus the shared repository. This includes the case when a user works on more than one research projects and also there are datasets public to the research space. | |
05.SEMSEARCH.R13 | 05.SSUC05.R4 | RS3.1 | The search result will be displayed in details view |
|
05.SSUC05.R4-1 | RS3.1 |
|
|
05.SSUC05.R4-2 | RS3.1 |
|
|
05.SSUC05.R4-3 | RS3.1 |
|
|
05.SSUC04.R4-4 |
|
Post-Conditions
|
05.SSUC05.R5 | RS3.1 | When the user enters one or several keywords, a search is performed and the system displays in details list the search result. |
|
05.SSUC05.R5a | RS3.1 | In case of several keywords, they are searched as a conjunction (all must appear), not literal phrase |
|
05.SSUC05.R6 | RS3.1 | When an object record from the search result is selected by the user, then full object record details could be reviewed. See UC 06.DAUC01: View Object Record. |
05.SSUC06: Select Search Result for Further Use
Preconditions:
|
05.SSUC06.R1 | UC 05.SSUC01: Advanced Semantic Search or UC05.SSUC05: Full Text Search has been performed and there is search result displayed. |
Constraints:
Transitions: No
Initiating operation/ button:
GUI:
- Search result
Description:
05.SEMSEARCH.R15 | 05.SSUC06.R2 | In front of each item in the search result there is a check box, and the item could be marked by the user. | |
05.SEMSEARCH.R15 | 05.SSUC06.R3 | There is option “Select All” and when selected by the user all items in the search result are selected. | |
05.SEMSEARCH.R15 | 05.SSUC06.R4 | When there is at least one item selected then are activated the following actions, which could be performed by the user: | |
05.SEMSEARCH.R16 | 05.SSUC06.R4-1 |
|
|
05.SEMSEARCH.R16 | 05.SSUC06.R4-2 |
|
|
|
05.SSUC06.R4-3 |
|
Post-Conditions
05.SEMSEARCH.R16 | 05.SSUC06.R5 | Link of the select item is copied into the select location |
05.SSUC07: Clear Search
Preconditions:
Constraints:
Transitions: No
Initiating operation/ button: Clear Search
GUI:
Main Menu Bar/ Advanced Semantic Search- Project Dashboard/ Advanced Semantic Search tab
Description:
05.SSUC03.R1 | When the user selects Clear Search button all values entered in the search criteria fields are deleted. |
Post-Conditions
UI and Navigation
Advanced Semantic Search mock-ups
Here are given example mock-ups for Advanced Semantic Search functionality. These mock-ups are designed for the developers to obtain more detailed understanding on the requirements listed above. It is not necessary the real screens to be 100% copy of the mock-ups.
Semantic Search screen
- The above picture is mock up of the semantic search. The user could search by project dataset or to search amongst all available for him datasets.
- The search result in the above mock-up is example of Details View.
- "Add to DataBasket" action could be performed only when a data object (one or more) is selected.
- If the search is started while a user is contributing into a discussion, then the action is active
- The search result in the above mock-up is example of Details View and LightBox view. Both views could not exist together, this is just for the example.
Select from Thesaurus screen
Saved searches screen
Advanced Semantic Search Navigation
The user interface-flow diagrams below is used to model the interactions that users have with application, as defined in the use case diagram above (see Diagram 05.1 Use Case Diagram)