diff --git a/docs/reference/administration/ontologies.ttl b/docs/reference/administration/ontologies.ttl index 95339f8..53809de 100644 --- a/docs/reference/administration/ontologies.ttl +++ b/docs/reference/administration/ontologies.ttl @@ -58,7 +58,7 @@
lapp:https://w3id.org/atomgraph/linkeddatahub/acl#https://w3id.org/atomgraph/linkeddatahub/admin/acl#lacl:CONSTRUCT queryTimeouts and connection lifetimes for LinkedDataHub's pooled HTTP clients, used for the Linked Data proxy and for accessing SPARQL services. All values are in milliseconds and are passed as CATALINA_OPTS system properties.
+To render paginated lists of resources, legacy applications would normally have a dedicated API endpoint that supports pagination, ordering etc. In LinkedDataHub, views achieve the same functionality by simply building the SPARQL query string on the client-side. Therefore views can be seen as client-side "containers".
-Views can be rendered in multiple layout modes: properties, list, grid, table, map, chart etc. They also show +
Views can be rendered in multiple layout modes: properties, list, grid, table, map, chart, and graph. They also show the total number of results and allow result ordering by property.
The UI layout can be customized and extended using stylesheets.
Note that user interface features are subject to access control. For example, - the search box will not be visible if the user is not authorized to access the search container.
+ actions such as creating or editing documents are only available to users with the corresponding write access.
@@ -28,7 +28,8 @@
The application title or logo in the top-left always links to the root container of the current application.
-Search box lets users search for resources within the current application that have the specified keyword in their titles, descriptions etc. Results are shown in a dropdown list.
+The address bar in the middle accepts the URI of a resource to navigate to. Entering an external http:// or https:// URL loads it through the Linked Data proxy so that it can be browsed within LinkedDataHub.
On the right, dropdown menus provide access to the list of applications and to your user account.
Due to current web browser limitations, it is not possible to logout using client certificate authentication. As a workaround, you can close the browser, and click Cancel when asked to select a @@ -54,38 +55,36 @@
The left sidebar provides two complementary ways to navigate your data: by document hierarchy and by class.
+The left sidebar is the main way to navigate your data. At the top, the search box finds resources within the current application that have the specified keyword in their titles, descriptions etc.; results are shown in a dropdown list. Below the search box, the sidebar offers complementary ways to browse the dataspace — by document hierarchy, by class, and through a few other data-driven views.
Document tree shows the document hierarchy of the dataspace. By clicking on a container, it expands to show its children.
In a desktop layout mode, the document tree folds out when the mouse is moved to the left edge of the screen. In a responsive layout, it is always shown.
In addition to browsing by document hierarchy, you can navigate your data by class. The class tree displays all classes defined in your
- application's ontology, organized by their rdfs:subClassOf relationships. Clicking on a class in the tree shows all instances
- of that class in your dataspace.
In addition to browsing by document hierarchy, you can navigate your data by class. The Classes list shows the classes (rdf:type values) that actually occur in the dataspace, each labelled with the number of its instances and ordered with the most-used classes first. Clicking a class opens a dialog listing all instances of that class across the dataspace.
Class-based navigation is particularly useful when:
The class tree respects your access control settings — you'll only see classes and instances you're authorized to access.
-The document tree also provides shortcuts to system containers:
+Because the list is derived from the data itself, it reflects whatever types are present — you do not need to define an ontology or class hierarchy. It also respects your access control settings: you only see classes and instances you are authorized to access.
+Below the classes, the sidebar provides a couple of additional data-driven views of the dataspace:
A right sidebar appears alongside the main view to show navigation into and out of the current data:
+In addition to navigating by document hierarchy, LinkedDataHub provides class-based navigation through the class tree widget.
- The class tree displays all classes from your application's ontology, organized by their inheritance relationships (rdfs:subClassOf).
In addition to navigating by document hierarchy, LinkedDataHub lets you navigate by class. The Classes list in the left sidebar shows the classes (rdf:type values) that occur in your data, each labelled with the number of its instances and ordered with the most-used classes first.
Class-based navigation is most useful when:
The class tree respects your access control settings — you'll only see classes you're authorized to view, and only instances you have permission to access.
+The classes list is derived from the data itself, so it reflects whatever types are present — no ontology needs to be defined. It respects your access control settings — you'll only see classes and instances you're authorized to access.
Search for resources using text keywords
You can lookup resources by typing a phrase (it does not have to be complete, start with a few letters) into the input in the navigation bar.
+You can lookup resources by typing a phrase (it does not have to be complete, start with a few letters) into the search box at the top of the left sidebar.
A dropdown list will appear if there are any matches. Use up/down keys or mouse click to select one of the results, and you will be redirected to its document.
The matching is done by looking for substrings using SPARQL regex() in common literal properties such as dct:title, rdfs:label, foaf:name etc. You can find the exact query in Queries / Select labelled.
The same widget is used for autocomplete inputs in the create/edit forms.
+The same widget is used for autocomplete inputs in the create/edit forms.