|
|
| (300 intermediate revisions by 16 users not shown) |
| Line 1: |
Line 1: |
| − | Describe the common functionality provided by any Community Web Portal for searching a collection, browsing the results, managing the content etc.
| + | ==Workspace== |
| | + | A workspace represents a collaborative area in which users can exchange and organize information objects (items) according to their specific needs. Because of this, every user of any Virtual Research Environment is provided with this area. Such an area is further organized in workspaces and baskets as to resemble a classic folder-based file system. The information objects that can be managed via the workspace range from files to D4Science documents, i.e. compound objects comprising metadata, alternative representations and multiple parts. The modality a workspace is populated range from the dragging of D4Science documents (or part of them) to the upload of files from its desktop and the exchange of workspace objects among users. |
| | | | |
| − | == Search ==
| + | [[Workspace | Click here for more information]] |
| − | Desribe the functionality commonly offered by the Search tab on GridSphere.
| + | |
| | | | |
| − | === Basic Search === | + | == Login to VO/VRE == |
| | | | |
| − | === Advanced Search ===
| + | See [[Log in User Guide]]. |
| | | | |
| − | === Collections Browsing === | + | == Search == |
| | | | |
| − | == Result Browsing ==
| + | See [[Search User Guide]]. |
| − | Available functionality for browsing the search results
| + | |
| − | | + | |
| − | === The Basket ===
| + | |
| − | | + | |
| − | '''The Basket is thought as a personal user DL dependent area.'''
| + | |
| − | The user can save its own preferred results by dragging them on it.
| + | |
| − | | + | |
| − | | + | |
| − | [[Image:DragRecordInBasket.jpg|frame|none|Example of dragging record in the Basket]] | + | |
| − | | + | |
| − | | + | |
| − | It is even possible to drag images in the basket (if they are retrieved results).
| + | |
| − | Indeed in the results page it is possible to drag whether records or images. The possibility is also thought for using them in the report generation and courses management.
| + | |
| − | | + | |
| − | [[Image:4_DragAndDrop_FromResults.jpg|frame|none|Example of dragging an image in the Basket]]
| + | |
| − | | + | |
| − | | + | |
| − | Once you have chosen your results you have the possibility to '''make them persistent''' by giving the basket a name and saving it on the server.
| + | |
| − | | + | |
| − | [[Image:14_GaliciaResults_And_SaveBasket.jpg|frame|none|Example of saving a Basket]]
| + | |
| − | | + | |
| − | | + | |
| − | You can always '''load your saved basket''' using the dropdown list placed on the top of the Basket.
| + | |
| − | | + | |
| − | [[Image:LoadBasket.jpg|frame|none|Load Basket example]]
| + | |
| − | | + | |
| − | By accessing the File menu besides the dropdown list it is possible to '''save the basket, to clean it or delete it'''.
| + | |
| − | Be aware that the delete command will phisically remove your saved basket from the server without any possibility to have it back.
| + | |
| − | | + | |
| − | [[Image:BasketMenuFile.jpg|frame|none|Load Basket example]]
| + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | Once you have your chosen items in the basket it is possible to access to all the actions you had in the results record page such as accessing metadata, add annotations, save or view the content. If the item is an image you can access to a small preview of it.
| + | |
| − | | + | |
| − | [[Image:7_All_Collection_Search_-_ViewContent.jpg|frame|none|Record actions from basket]]
| + | |
| − | [[Image:4 GeoSpatial Results inBasket with Preview.jpg|frame|none|Image Preview from basket]]
| + | |
| − | | + | |
| − | === Common Browsing Activities ===
| + | |
| | | | |
| | == Annotations == | | == Annotations == |
| | | | |
| − | Annotations’ management is performed by Annotation Front-End/ Portlet. This is a graphical user interface which provides an easy and sufficient way to annotate gCube resources. Annotation Front-End can be invoked by selecting to manage the annotations of an object in Results portlet. | + | Annotations’ management is performed by the Annotation Portlet. This is a graphical user interface which provides an easy and sufficient way to annotate gCube information objects. Annotation Portlet can be invoked by selecting the “Manage Annotations” action among the actions associated with any item displayed in the Results portlet. |
| − | | + | |
| − | Then the user is moved to the generic annotation portlet where he is able to see the title, the mimetype, the content of the selected object as well as its generic annotations sorted by their creation date.
| + | |
| − | | + | |
| − | Depending on the mimetype of the annotated object the visualization of its content may differ. For the majority of the objects which are supported from browsers, the content is displayed in a specified part of the portlet. For zip files, its entries are displayed and the user is able to download it. Tiff images are transformed into a displayable format (png), video files are available only for download and the visualization of pdf files depends on the behaviour of the browser (normally a plug-in is required).
| + | |
| − | | + | |
| − | On the other hand, the annotations are shown up as a list where their title, the author’s user name and their creation/ modification date are posted up. The user is able to select which annotations (comments or associations) he wants to see just by clicking on the available checkboxes. The content of the annotations is shown below this list. In the case of associations, the title of the associated object as well as a link to its content is displayed.
| + | |
| − | | + | |
| − | The user may perform three operations. He can add an annotation by clicking on the “Add Annotation” button and afterwards by filling in the title and text field in the case of text annotations or by filling in the title field and selecting an object existing in basket as an associated object in the case of associations. He may also delete or edit an annotation.
| + | |
| − | | + | |
| − | If anchored annotations are supported for the annotated object the user can choose to be moved to the appropriate portlet by clicking on the “Go to anchored mode” button. Three portlets for anchored annotations are provided which are cover images, text and video files.
| + | |
| − | | + | |
| − | | + | |
| − | [[Image:GenericAnnotationScaled.png|frame|none|Generic Annotation Portlet]]
| + | |
| − | | + | |
| − | | + | |
| − | In image annotation portlet a user is able to add an annotation to a specific part of the image file. The user selects a space fragment which can be a rectangular area or a specific point (with a pin) and then he fills in the title and text fields. Then the space fragments are shown on the image and by clicking on one of them the content of the annotation is displayed.
| + | |
| − | | + | |
| − | | + | |
| − | [[Image:ImageAnnotationScaled.png|frame|none|Image Annotation Portlet]]
| + | |
| − | | + | |
| − | | + | |
| − | In text annotation portlet there is the capability of adding an annotation on a selected text fragment of the file. The selection of the text fragment is done in a very user friendly way as the user has only to choose the part of the text file with his mouse. The text fragments are shown with a different background in order to be distinguishable and by clicking on one of them the content of the annotation is displayed.
| + | |
| − | | + | |
| − | | + | |
| − | [[Image:TextAnnotationScaled.png|frame|none|Text Annotation Portlet]]
| + | |
| − | | + | |
| − | | + | |
| − | In video annotation portlet (still under construction) a user is able to select a time fragment which means a part of the video file that is defined by its starting and ending moment. Video annotation portlet has although some requirements as it needs Java Media Framework installed on the user’s computer.
| + | |
| − | | + | |
| − | | + | |
| − | [[Image:VideoAnnotationScaled.png|frame|none|Video Annotation Portlet]]
| + | |
| − | | + | |
| − | == Metadata Management ==
| + | |
| − | View and Edit metadata are the two functionalities that gCube offers to its users concerning the Metadata Management. These are described below.
| + | |
| − | | + | |
| − | === Metadata Viewing ===
| + | |
| − | | + | |
| − | The Metadata Viewing Portlet is a graphical user interface that displays the metadata which are associated with a specific information object. This interface displays the object’s metadata in a graphical way which depends on their schema.
| + | |
| − | | + | |
| − | Furthermore the portlet provides the ability for each user to change the way the metadata are displayed. If a user wants to manage the layout of the metadata viewing portlet, he may choose one layout of the available. This selection can be done in the user profile editing portlet.
| + | |
| − | | + | |
| − | | + | |
| − | [[Image:MetadataViewingScaled.png|frame|none|Metadata Viewing Portlet]]
| + | |
| − | | + | |
| − | === Metadata Editing ===
| + | |
| − | | + | |
| − | Metadata’s editing is performed by Metadata Editing Portlet. This is a graphical user interface which can be invoked by selecting to edit the metadata of an object in Results portlet. Depending on the schema of the metadata different editors can be displayed. There are two visual editors for dc and eiDB schemas and a generic one for the rest. However, for some collections, it is forbidden to change the metadata, something that is stated on screen with a relevant message.
| + | |
| − | | + | |
| − | The visual metadata editors provide an easy and user friendly way of editing the metadata. Adding, deleting and editing elements can be performed by clicking on the appropriate buttons and filling in text fields. When the user completes his desired changes, he has to apply the changes he has done by clicking on the “Save Changes” button.
| + | |
| − | | + | |
| − | | + | |
| − | [[Image:MetadataEditingScaled.png|frame|none|Visual Editor]]
| + | |
| − | | + | |
| − | | + | |
| − | The generic editor provides two options. The first one is to edit the bare xml in a text editor and the second one is to upload an xml file as metadata. However, these options require the user to have sufficient knowledge of XML.
| + | |
| − | | + | |
| − | | + | |
| − | [[Image:MetadataEditingGenericScaled.png|frame|none|Generic Editor]]
| + | |
| − | | + | |
| − | == Index Management ==
| + | |
| − | | + | |
| − | === Full Text Index ===
| + | |
| − | | + | |
| − | After opening the the FullTextManagementPortlet, you will see a screen with an Index Explorer tree on the left side, and an (empty) Index Detail panel on the right. The IndexDetail Panel will be emty as no index resource is currently selected in the Index Explorer tree. The Index Explorer panel however, will always display one or more folder icons when the portlet is ready for use:
| + | |
| − | [[Image:FullTextPortlet1.png|frame|none|Generic Editor]]
| + | |
| − | | + | |
| − | The folder icons represent metadata collections available in the VO.
| + | |
| − | A big green folder (marked with a [<span style="color:red">1</span>] above) represents a collection name which has one or more related indices.
| + | |
| − | A big blue folder (marked [<span style="color:red">2</span>]) represents a collection name which does not have any related indices.
| + | |
| − | The single blue folder with a pencil above it and the text "Fake Collections" (marked [<span style="color:red">3</span>]) is the only icon which is certain to be shown (even if no collections exist). This icon represents all collection IDs which are related to one or more indices, but which can not be mapped to a true metadata collections. This is a usual scenario when test indices are created without the need to be connected to a collection, or with a specific need not to be connected to a collection in order to not be used by the rest of the DL infrastructure.
| + | |
| − | | + | |
| − | | + | |
| − | A collection name is not necessarily unique, as many collections are allowed to have the same name though not the same ID. Actual metadata collections are represented by a smaller folder icon, along with its collection ID. Collections which have been indexed, are represented by a green folder (marked [<span style="color:red">4</span>]), while collections which have not been indexed are represented by a grey foler (marked [<span style="color:red">5</span>]).
| + | |
| − | | + | |
| − | ==== Full Text Index Information ====
| + | |
| − | If you expand the green collection tree items (by clicking on the [+] besides them), one or more Index icons (marked [<span style="color:red">1</span>] bellow) will reveal them selves. These represent Index Managers. If any Index Lookups are connected to the Index Manager, the Index item can be expanded to reveal one or more Index Lookup icons (marked[<span style="color:red">2</span>]):
| + | |
| − | | + | |
| − | [[Image:FullTextPortlet2.png|frame|none|Generic Editor]]
| + | |
| − | | + | |
| − | If you select either an Index item or an Index Lookup item in the Index Explorer, the Index Detail panel will show a tab panel with information related to the selected resource (WS ResourceProperty values). If an Index item is choosen, the IndexDetail will look similar to the following illustration:
| + | |
| − | | + | |
| − | [[Image:FullTextPortletDetail1.png|frame|none|Generic Editor]]
| + | |
| − | | + | |
| − | And if an Index Lookup item is chose, it will look similar to the following:
| + | |
| − | [[Image:FullTextPortletDetail2.png|frame|none|Generic Editor]]
| + | |
| − | | + | |
| − | ==== Editing the IndexType ====
| + | |
| − | | + | |
| − | In order to edit the Index Type of an Index Manager, make sure the correct Index item is selected in the Index Explorer, and select the "Edit" tab in the Index Detail tab panel. This will reveal Index Edit panel:
| + | |
| − | [[Image:FullTextPortletDetail3.png|frame|none|Generic Editor]]
| + | |
| − | The chosen Index items IndexType is displayed as a list of Index Type Fields with editable checkboxes. The save button will save the IndexType currently shown to the selected Index Management resource.
| + | |
| − | | + | |
| − | If a Index Lookup item was selected, choosing the "Edit" tab will reveal the Index Lookup Edit panel:
| + | |
| − | [[Image:FullTextPortletDetail4.png|frame|none|Generic Editor]]
| + | |
| − | This panel is identical to the Index Edit panel, however only the "Return" checkboxes are enabled. This is due to the fact that the Return Element is the only part of an IndexLookup's index type which is editable. Any other changes will have to be performed towards the Index Management (using the Index Edit panel)
| + | |
| − | | + | |
| − | ==== Creating a Full Text Index ====
| + | |
| − | Creating a new Index can be accomplished by either selecting the "New Index" item (marked [<span style="color:red">1</span>] bellow) or the "New Fake Collection" item (marked [<span style="color:red">2</span>])in the Index Explorer:
| + | |
| − | [[Image:FullTextPortlet5.png|frame|none|Generic Editor]]
| + | |
| − | Upon selecting one of the two said items, the Index Detail panel will allow you to specify the properties of the new Index. The IndexID property textbox should usually be left empty, in which case the IndexService itself will create a unique ID for the Index. If the "New Fake Collection" item was chosen, you will also need to specify a collection ID (fake - "myTestCollection1" or something to that effect), however if the "New Index" item was chosen, the collection ID will be retrieved from the parent collection item and will not be editable (as shown in the image above).
| + | |
| − | | + | |
| − | After specifying the properties of the new Index, push the "Create" button in order to create the new Index. Upon success, the new Index Item will appear and be selected in the Index Explorer. The "Info" tab of the new Index will be shown in the Index Detail panel:
| + | |
| − | [[Image:FullTextPortlet6.png|frame|none|Generic Editor]]
| + | |
| − | Usually (and as shown in the above image), the Index Detail panel will be unable to retrieve information about the newly created Index. This is due to the fact that there is a slight lag between the creation of an Index and the availability of information about the Index. Selecting the newly created Index item once more (by clicking on it) will update the Index Detail panel with valid data.
| + | |
| − | | + | |
| − | ==== Creating a Full Text Index Lookup ====
| + | |
| − | In order to query an Index, an Index Lookup resource is needed. An Index Lookup can be created at any point in the life time of an Index, and will automatically be updated when new information is indexed by its Index Manager. In order to create a new Index Lookup resource for an Index, select the "New Lookup" item under the Index item in the Index Explorer:
| + | |
| − | [[Image:FullTextPortlet7.png|frame|none|Generic Editor]]
| + | |
| − | The Index Detail panel will show a very simple interface, allowing you to specify the Lemmatizer plugin the new Index Lookup should use. Usually, this text box should be left empty, in which case the default Lemmatizer plugin will be used. Pushing the "Create" button will trigger the creation of the new Index Lookup. Upon success, an item with a new icon will appear and be selected in the Index Explorer. This item represents the newly created Index Lookup. The "Info" tab of theIndex Lookup will be shown in the Index Detail panel:
| + | |
| − | [[Image:FullTextPortlet8.png|frame|none|Generic Editor]]
| + | |
| − | | + | |
| − | As with the creation of an Index, the Index Detail will usually not be able to get information about the Index Lookup right after its creation, in which case you will have to select the Lookup item once more if you need to see valid information about the new item.
| + | |
| − | | + | |
| − | ==== Feeding a Full Text Index ====
| + | |
| − | The information to be indexed is fed to the Index through a [[ResultSet Framework|ResultSet]]. In order to index the ResultSet, select the Index item to use in the Index Explorer, and choose the "Feed" tab. Enter a valid RSLocator string in the textbox as shown bellow (the RSLocator string in the example is a bit strange since points to a local ResultSet):
| + | |
| − | [[Image:FullTextPortlet9.png|frame|none|Generic Editor]]
| + | |
| − | | + | |
| − | Push the "Update" button to start the indexing of the provided ResultSet. A green label will indicate that the update has been successfully started:
| + | |
| − | [[Image:FullTextPortlet10.png|frame|none|Generic Editor]]
| + | |
| − | | + | |
| − | ==== Testing/Querying a Full Text Index ====
| + | |
| − | In order to test (by querying) an Index, an Index Lookup for the Index in question is needed. If one is not available, it has to be [[Common_Functionality#Creating a Full Text Index Lookup|created]]. If an Index Lookup is available for the Index to be queried, select the Index Lookup in the Index Explorer and select the "Query" tab in the Index Detail panel. This tab allows you to enter a query string as shown bellow:
| + | |
| − | [[Image:FullTextPortlet11.png|frame|none|Generic Editor]]
| + | |
| − | | + | |
| − | Pushing the Query button will perform a query against the Index Lookup. Upon success, the first page of the results of the query will be shown in its raw XML format bellow the query text box:
| + | |
| − | [[Image:GeneralIndexDesign.png|frame|none|Generic Editor]]
| + | |
| − | | + | |
| − | ==== Removing a Full Text Index or Index Lookup ====
| + | |
| − | | + | |
| − | In order to remove an Index or an Index Lookup, select the item to be removed in the Index Explorer and choose the "Remove" tab in the Index Detail. Clicking the remove button (marked [<span style="color:red">1</span>] bellow), will cause a warning dialog (marked [<span style="color:red">2</span>]) to be shown. Push the "OK" button to remove the resource (and keep in mind that removing an Index resource will automatically remove all Index Lookup and Index Updater resources connected to it):
| + | |
| − | [[Image:FullTextPortletDetail5.png|frame|none|Generic Editor]]
| + | |
| − | | + | |
| − | Upon success, a green confirmation message will be shown:
| + | |
| − | [[Image:FullTextPortletDetail6.png|frame|none|Generic Editor]]
| + | |
| − | | + | |
| − | Upon failure, a red error message will be shown. This messge is usually due to the resource already having been removed, but still being present in the Index Explorer due to delays in the underlying infrastructure.
| + | |
| − | [[Image:FullTextPortletDetail7.png|frame|none|Generic Editor]]
| + | |
| − | | + | |
| − | === Geo Index ===
| + | |
| − | ==== Overview ====
| + | |
| − | ==== Geo Index Information ====
| + | |
| − | ==== Editing the GeoIndexType ====
| + | |
| − | ==== Creating a Geo Index ====
| + | |
| − | ==== Testing a Geo Index ====
| + | |
| − | ==== Removing a Geo Index ====
| + | |
| − | | + | |
| − | | + | |
| − | == VRE Monitoring ==
| + | |
| − | | + | |
| − | The monitoring allows to control the status of infrastructure for the VRE.
| + | |
| − | | + | |
| − | [[Image:Monitoring.png|frame|none|Monitoring]]
| + | |
| − | | + | |
| − | On the left panel the user has the opportunity to choose which type of resource he wants to monitor.
| + | |
| − | | + | |
| − | On the upper-right panel the user can navigate the list of the resources of the type selected of the left panel.
| + | |
| − | | + | |
| − | The profile of the selected resource in the list is shown in the down right panel. By default the profile is shown in an user oriented view.
| + | |
| − | Clicking on the button ''"XML View"'' the profile is shown in XML mode. Newly clicking on ''"Normal View"'' the profile is shown in an user oriented view.
| + | |
| − | | + | |
| − | [[Image:MonitoringXML.png|frame|none|Monitoring]]
| + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | Selecting ''"Map"'' on the left panel the location Map of the hardware resources are shown.
| + | |
| − | | + | |
| − | [[Image:MonitoringMap.png|frame|none|Monitoring]]
| + | |
| | | | |
| − | The green icons [[Image:GlueSite.png]] represent gLite Nodes, instead the yellow icons [[Image:GCubeNode.png]] represent DHN.
| + | Then the user is moved to the annotation portlet where s/he is able to see the title, the mimetype, the content of the selected object as well as its annotations sorted by their creation date and grouped into threads. |
| | | | |
| − | Clicking on the icon a zoom is performed if needed and a ''Tabbed Information Window'' is open. Each tab represents a part of the information available for the selected node. In some cases in the ''Tab Information Window'' there are some links which cause the opening of a new browser window.
| + | Depending on the mimetype of the annotated object, the visualization of its content may differ. |
| | | | |
| − | [[Image:MonitoringMapNodeInformation.png|frame|none|Monitoring]]
| + | In most cases, the content is displayed in a specified part of the portlet. |
| | | | |
| − | == VRE Management ==
| + | For a zip file, its entries are displayed and the user is able to download any of them. |
| − | === Resources Registration ===
| + | |
| | | | |
| − | It is possible to register various types of resource on infrastructure. There is a dedicated user interface for each of them.
| + | Tiff images are transformed into a displayable format (png); video files are available only for download and the visualization of pdf files depends on the behavior of the browser (normally a plug-in is required). |
| − | After the registration process, each resource is going on a pending state and needs to be approved by one administrator with the approval user interface.
| + | |
| | | | |
| − | ==== External Running Instance Registration ====
| + | On the other hand, the annotations are grouped into threads, shown up as a list where the title of each thread is the title of the first contained annotation. |
| | + | The user can enter each thread and the annotations of this thread are displayed as a list where the title, their creation/ modification date and the author’s name are posted up. |
| | + | The user is able to select which annotations (comments or associations) s/he wants to see just by clicking on it. The content of the annotations is shown at a pop up window where you can edit it. In the case of associations, the title of the associated object as well as a link to its content is displayed. |
| | | | |
| − | An External Running Instance is a WEB-Service which we want to make available in the infrastructure.
| + | The user can either enter a selected Thread or create a new Thread by clicking on the corresponding buttons. By creating a new Thread a new annotation is actually created. |
| | + | After entering a Thread the uses can add an annotation by clicking on the “Add” button and afterwards by filling in the title and text field, in the case of text annotations, or by filling in the title field and selecting an object existing in the basket as an associated object in the case of associations. S/he may also delete or edit an annotation. |
| | | | |
| − | [[Image:ExternalRunningInstanceRegistration.png]]
| + | All the changes made by the user are persisted when s/he presses the "Save Changes" button. |
| | | | |
| − | ==== Service Archive Registration ====
| + | <!--If anchored annotations are supported for the annotated object the user can choose to be moved to the appropriate portlet by clicking on the “Go to anchored mode” button. Three portlets for anchored annotations are provided, namely, cover images, text and video documents.--> |
| | | | |
| − | A Service Archive is a software component compliant with gCube policies we want to register in the infrastructure.
| |
| | | | |
| − | [[Image:ServiceArchiveRegistration.png]] | + | [[Image:AnnotViewThreads.png|frame|none|Annotation Portlet]] |
| | | | |
| − | ==== DHN Registration ====
| |
| | | | |
| − | A DHN is a Server empowered by the DHN software component.
| |
| | | | |
| − | [[Image:DHNRegistration.png]]
| |
| | | | |
| − | ==== Archive/Data source Registration ====
| + | When the object that is annotated is an image the user is able to add an annotation to a specific part of the image file. The user selects a space fragment and then he fills in the title and text fields. Then the space fragments are shown on the image and by clicking on one of them the content of the annotation is displayed. |
| | | | |
| − | Any existing data sources can be made available in the infrastructure defining the appropriate configuration file.
| |
| − | The syntax of the configuration file is described in the Archive Import service documentation.
| |
| | | | |
| − | [[Image:ArchiveDataSourceRegistration.png]] | + | [[Image:AnnotCreateNew.png|frame|none|New annotation with fragment]] |
| | | | |
| − | === Resources Approval ===
| + | The user can edit an annotation be selecting the annotation s/he wants to edit and click on the "Edit" button. A pop up window appears with the content of the annotation |
| | | | |
| − | For each kind of resource the user can register, the approving step need to be performed by one administrator.
| + | [[Image:AnnotEdit.png|frame|none|New annotation with fragment]] |
| − | After this step the resource are available on the infrastructure.
| + | |
| | | | |
| − | All this portlets are list with a checkbox on each row. After the selection process the administrator has the opportunity to choose the action he want to do.
| |
| − | Two actions are possible: ''Approve'' or ''Withdraw''. This is performed on the selected resources by clicking on the relative button.
| |
| − | The list is paginated and present 10 resource for each page. The action has affect only on the selected resources on the current page.
| |
| | | | |
| − | ==== External Running Instance Approval ====
| + | <!-- In text annotation portlet there is the capability of adding an annotation on a selected text fragment of the textual document (e.g. plain text, xml documents). The selection of the text fragment is done in a very user friendly way as the user has only to choose the part of the text document with his mouse. The text fragments are shown with a different background in order to be distinguishable and by clicking on one of them the content of the annotation is displayed. |
| | | | |
| − | [[Image:ExternalRunningInstanceApproval.png]]
| |
| | | | |
| | + | In video annotation portlet (still under construction) a user will be able to select a time fragment which means a part of the video file that is defined by its starting and ending moment. Video annotation portlet has although some requirements as it needs Java Media Framework installed on the user’s computer. --> |
| | | | |
| − | ==== Service Archive Approval ====
| |
| | | | |
| − | [[Image:ServiceArchiveApproval.png]]
| + | == Content Viewer == |
| | | | |
| − | ==== DHN Approval ====
| + | The content viewer portlet provides the functionality to view a gCube object and all its properties and transform it, if any transformation is available for the object's mime type. |
| | | | |
| − | [[Image:DHNApproval.png]]
| + | Using this portlet you can: |
| | + | * View the content of the selected object |
| | + | * View the available metadata of the object |
| | + | * View the aternative representations |
| | + | * Transform the main object using any of the available transformation programs (if any) and save the result of the transformation as a new object |
| | | | |
| | + | In order to use this portlet you should select from the results menu the '''Explore Object''' option for the object you would like to explore. After selecting this option you will be redirected to the Content Viewer portlet.<br> |
| | + | The main object is displayed as you can see at the image below<br> |
| | | | |
| − | ==== Archive/Data source Approval ====
| + | [[File:CVMain.png]] |
| | | | |
| − | [[Image:ArchiveDataSourceApproval.png]]
| + | When you click on the '''Display''' button the pop-up window with the all the available properties for this object is displayed. You can select any of the available properties to view. |
| | + | For example you can see at the image below the metadata at the FARM_dc schema for this object.<br> |
| | | | |
| − | === Services Deployment ===
| + | [[File:CMDisMetadata.png]] |
| | | | |
| − | This task is available with an user interface looks like the monitoring.
| + | To view any of the alternative objects that are related to this object click on them<br> |
| − | Apart a reduced the monitoring issue the administrator can select the ''DHN'' and the ''Services'' he wants to deploy on the nodes.
| + | |
| − | For the ''DHN'' only, the one in bold in the list can be selected. This due to configuration of the ''DHN'' made by the administrator, for example in respect of the institution policy or others reason.
| + | |
| − | All ''Services'' can be selected.
| + | |
| | | | |
| − | The selection/deselection of one ''DHN'' or ''Service'' can be done using the button on the header of the bottom-right panel.
| + | [[File:CVDisAlt.png]] |
| − | When a ''Node'' or a ''Service'' is selected, it is inserted on the '''"Selected Resource Tree"'''. These tree can be browsed as the '''"Available Resource Tree"'''. These allow the user to have a sort of basket to check the selected resources in each moment.
| + | |
| | | | |
| − | Further, when a ''DHN'' is selected another entry is presented on the left panel. In particular it is present '''Running Instance On <Name of Selected DHN>''' entry.
| + | === Transforming the selected object === |
| − | Clicking on it, the upper-right panel lists the already available ''Running Instance'' on that ''DHN''. This allows the administrator to evaluate a ''DHN''. For example, the administrator can decide if the selected ''DHN'' is the proper one to host new ''Service[s]'' deployment.
| + | |
| | | | |
| − | When at least one ''DHN'' and one ''Service'' are selected a '''Deploy''' button appears on the left panel.
| + | Depending on the available transformations programs you can transform the object to a new object and save it. |
| | + | In the example below the main object can be transformed to a new image with given height and width. <br> |
| | | | |
| − | Clicking on it the deploy process starts after a confirmation request.
| + | [[File:CVTransformMain.png]] |
| | | | |
| − | During the deployment is presented a Dialog Box with the deployment status. The status is refreshed until the process is completed with a failure or with a success.
| |
| | | | |
| − | [[Image:ServiceDeployment.png]]
| + | === Search Profile Settings === |
| | | | |
| − | == VRE Creation ==
| + | The Search Profile portlet can be accessed by all users that have a portal account. Each user has his/her own search profile and he/she can view and/or edit its content through this portlet. |
| | + | By editing the search profile's contents you have several options that affect the search results or the presentation of the results and their metadata. |
| | | | |
| − | Wizard mechanism is the way used to create a new VRE.
| + | <!-- * <b>Personalize the search results:</b> |
| | + | ** Change the language using the drop-down list. The language in the profile affects the results that will be retrieved. The results will be only contain content in the preferred language. |
| | + | ** <b>EngineType:</b> InternalEngine |
| | + | EngineType element specifies the desired type of the engine that will be |
| | + | employed for executing plans produced by the search engine. The value |
| | + | type of this element is string. Currently these types are supported: |
| | + | InternalEngine: Search internal execution engine |
| | + | ActiveBPEL: ActiveBPEL engine |
| | + | OSIRIS: OSIRIS execution engine |
| | + | * <b>Persistence:</b> false |
| | + | Persistence refers to the ability of the execution engine to |
| | + | persist its runtime state, in order to perform execution reincarnation, |
| | + | multiple executions, execution logging and analysis, etc. |
| | + | The value type of this element is boolean (true or false). |
| | + | * <b>FaultTolerance: </b>false |
| | + | FaultTolerance refers to |
| | + | the ability of the execution engine to recover from errors. The value |
| | + | type of this element is boolean (true or false). |
| | + | <br> |
| | + | --> |
| | | | |
| | | | |
| − | [[Image:VREStart.png]]
| + | * <b>Personalize the presentation of the results and their metadata:</b> |
| | + | ** For each available collection you can select any of the available presentable fields that will be used for the presentation of the results from the results portlet when this collection is used in search. If you don't select any field then all the available presentable fields will be displayed. |
| | + | ** For each available metadata schema you can select one of the available xslts that will be used for the presentation of the metadata. If you don't change anything the default XSLT will be used. |
| | + | ** A preview is displayed for the current selected schema and XSLT. This helps you to select the desired XSLT. |
| | | | |
| − | The wizard is composed by 4 step at design time.
| + | In order to apply the changes you need to click on the '''Save profile''' button. A message is displayed to inform you if the profile was successfully updated. |
| | | | |
| − | - '''''VRE Information'''''
| + | == Report Management == |
| − | - '''VRE Content'''
| + | See [[Report Management]] page. |
| − | - '''''VRE Collections'''''
| + | |
| − | - '''''VRE Metadata Format'''''
| + | |
| − | - '''''VRE Functionality'''''
| + | |
| | | | |
| | + | == Time Series == |
| | + | [[Time Series | Click here to visit the Time Series portlet guide]] |
| | | | |
| − | When the Administrator will approve the VRE will be able to see and modify each step. Further he will do an additional step '''''VRE Architecture'''''.
| + | == AquaMaps Suite == |
| | + | The AquaMaps suite supports the production of AquaMaps and related data products, i.e. compound objects containing species and biodiversity occurrence predictive maps. |
| | | | |
| − | [[Image:VREInformationAdmin.png]] | + | [[AquaMaps | Click here to visit the AquaMaps Suite guide]] |
A workspace represents a collaborative area in which users can exchange and organize information objects (items) according to their specific needs. Because of this, every user of any Virtual Research Environment is provided with this area. Such an area is further organized in workspaces and baskets as to resemble a classic folder-based file system. The information objects that can be managed via the workspace range from files to D4Science documents, i.e. compound objects comprising metadata, alternative representations and multiple parts. The modality a workspace is populated range from the dragging of D4Science documents (or part of them) to the upload of files from its desktop and the exchange of workspace objects among users.
Annotations’ management is performed by the Annotation Portlet. This is a graphical user interface which provides an easy and sufficient way to annotate gCube information objects. Annotation Portlet can be invoked by selecting the “Manage Annotations” action among the actions associated with any item displayed in the Results portlet.
Then the user is moved to the annotation portlet where s/he is able to see the title, the mimetype, the content of the selected object as well as its annotations sorted by their creation date and grouped into threads.
Depending on the mimetype of the annotated object, the visualization of its content may differ.
For a zip file, its entries are displayed and the user is able to download any of them.
Tiff images are transformed into a displayable format (png); video files are available only for download and the visualization of pdf files depends on the behavior of the browser (normally a plug-in is required).
On the other hand, the annotations are grouped into threads, shown up as a list where the title of each thread is the title of the first contained annotation.
The user can enter each thread and the annotations of this thread are displayed as a list where the title, their creation/ modification date and the author’s name are posted up.
The user is able to select which annotations (comments or associations) s/he wants to see just by clicking on it. The content of the annotations is shown at a pop up window where you can edit it. In the case of associations, the title of the associated object as well as a link to its content is displayed.
The user can either enter a selected Thread or create a new Thread by clicking on the corresponding buttons. By creating a new Thread a new annotation is actually created.
After entering a Thread the uses can add an annotation by clicking on the “Add” button and afterwards by filling in the title and text field, in the case of text annotations, or by filling in the title field and selecting an object existing in the basket as an associated object in the case of associations. S/he may also delete or edit an annotation.
All the changes made by the user are persisted when s/he presses the "Save Changes" button.
The user can edit an annotation be selecting the annotation s/he wants to edit and click on the "Edit" button. A pop up window appears with the content of the annotation
The content viewer portlet provides the functionality to view a gCube object and all its properties and transform it, if any transformation is available for the object's mime type.
To view any of the alternative objects that are related to this object click on them
Depending on the available transformations programs you can transform the object to a new object and save it.
In the example below the main object can be transformed to a new image with given height and width.
The Search Profile portlet can be accessed by all users that have a portal account. Each user has his/her own search profile and he/she can view and/or edit its content through this portlet.
By editing the search profile's contents you have several options that affect the search results or the presentation of the results and their metadata.
The AquaMaps suite supports the production of AquaMaps and related data products, i.e. compound objects containing species and biodiversity occurrence predictive maps.
