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# Access control lacl: diff --git a/docs/reference/command-line-interface.ttl b/docs/reference/command-line-interface.ttl index 9f7ad17..def280c 100644 --- a/docs/reference/command-line-interface.ttl +++ b/docs/reference/command-line-interface.ttl @@ -231,7 +231,7 @@ Options: Add CONSTRUCT query - admin/ontologies/add-construct.sh + admin/ontologies/add-constructor.sh Create ontology diff --git a/docs/reference/configuration.ttl b/docs/reference/configuration.ttl index 16524e5..2a23ec4 100644 --- a/docs/reference/configuration.ttl +++ b/docs/reference/configuration.ttl @@ -140,6 +140,20 @@
Configures a proxy server for accessing SPARQL services and backend endpoints
+
+

HTTP client timeouts

+

Timeouts 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.

+
+
CLIENT_SOCKET_TIMEOUT
+
Socket (read) timeout — how long to wait for data on an established connection. By default 120000.
+
CLIENT_CONNECT_TIMEOUT
+
Connection timeout — how long to wait to establish a connection. By default 10000.
+
CLIENT_CONNECTION_TIME_TO_LIVE
+
Maximum lifetime of a pooled connection before it is closed. By default 300000.
+
CLIENT_VALIDATE_AFTER_INACTIVITY
+
Idle time after which a pooled connection is validated before reuse. By default 10000.
+
+

Varnish

diff --git a/docs/reference/data-model/resources/views.ttl b/docs/reference/data-model/resources/views.ttl index 78fa08a..e7177bb 100644 --- a/docs/reference/data-model/resources/views.ttl +++ b/docs/reference/data-model/resources/views.ttl @@ -22,7 +22,7 @@

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.

Layout modes

diff --git a/docs/reference/user-interface.ttl b/docs/reference/user-interface.ttl index fce9725..d99a1c5 100644 --- a/docs/reference/user-interface.ttl +++ b/docs/reference/user-interface.ttl @@ -17,7 +17,7 @@

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.

User interface @@ -28,7 +28,8 @@ Navigation bar

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 @@

-

Document tree

-

The left sidebar provides two complementary ways to navigate your data: by document hierarchy and by class.

+

Left sidebar

+

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 hierarchy navigation

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.

Class-based navigation

-

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:

  • You want to see all instances of a particular type across your entire dataspace
  • You need to browse data organized by domain concepts rather than container structure
  • -
  • You're working with data that has rich class hierarchies
-

The class tree respects your access control settings — you'll only see classes and instances you're authorized to access.

-

System containers

-

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.

+

Other views

+

Below the classes, the sidebar provides a couple of additional data-driven views of the dataspace:

-
Latest
-
A container with the latest resources in the application's dataset by creation/modification date
-
Files
-
A container for file uploads
-
Imports
-
A container for data imports
-
Queries
-
A container for end-user SPARQL queries (including vocabulary - mappings)
Geo
-
A container with all resources in the application's dataset that have geographic coordinates
-
Charts
-
A container with charts that visualize SPARQL query results
+
Opens a dialog listing all resources in the dataspace that have geographic coordinates.
+
Latest
+
Opens a dialog listing the most recently created resources in the dataspace, newest first.
+
+
+
+

Right sidebar

+

A right sidebar appears alongside the main view to show navigation into and out of the current data:

+
+
Backlinks
+
In properties mode, lists resources that link to a resource in the current document — that is, resources that have a property whose value is the current resource. This complements the outgoing properties shown in the main view.
+
Related results
+
For view result sets, parallax navigation lets you jump from the current results to a related set by following a selected property (for example, from a set of products to the companies that supply them). It works together with the view's faceted search.
diff --git a/docs/user-guide/import-data/import-csv-data.ttl b/docs/user-guide/import-data/import-csv-data.ttl index 05ea75e..95e1c9a 100644 --- a/docs/user-guide/import-data/import-csv-data.ttl +++ b/docs/user-guide/import-data/import-csv-data.ttl @@ -64,8 +64,8 @@
Query title
-
  • Once all the fields have been filled in click Save. You can find this saved under - Queries container in left navigation.
  • +
  • Once all the fields have been filled in click Save. You can find it saved in the + Queries container, which you can open from the document tree in the left sidebar.
  • Click on the Create dropdown button at the top left-hand corner and select CSV Import. This will open a new form.
  • Fill out Item fields
  • diff --git a/docs/user-guide/import-data/import-rdf-data.ttl b/docs/user-guide/import-data/import-rdf-data.ttl index 0409103..f23331a 100644 --- a/docs/user-guide/import-data/import-rdf-data.ttl +++ b/docs/user-guide/import-data/import-rdf-data.ttl @@ -135,8 +135,8 @@
    Query title
    -
  • Once all the fields have been filled in click Save. You can find this saved under - Queries container in left navigation.
  • +
  • Once all the fields have been filled in click Save. You can find it saved in the + Queries container, which you can open from the document tree in the left sidebar.
  • Click on the Create dropdown button at the top left-hand corner and select RDF Import. This will open a new form.
  • Fill out Item fields
  • diff --git a/docs/user-guide/navigate-data.ttl b/docs/user-guide/navigate-data.ttl index 3e34edc..aeecff4 100644 --- a/docs/user-guide/navigate-data.ttl +++ b/docs/user-guide/navigate-data.ttl @@ -24,26 +24,22 @@

    -

    Class tree

    -

    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).

    +

    Class-based navigation

    +

    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.

    Using class-based navigation

      -
    1. Open the left sidebar (slide mouse to left edge on desktop, or it's always visible on responsive layouts)
    2. -
    3. Switch to the class tree view (if not already showing)
    4. -
    5. Browse the class hierarchy — classes are organized by their subclass relationships
    6. -
    7. Click on any class to view all instances of that class in your dataspace
    8. -
    9. Expand parent classes to see their subclasses
    10. +
    11. Open the left sidebar (slide the mouse to the left edge on desktop, or it is always visible on responsive layouts)
    12. +
    13. Find the Classes list
    14. +
    15. Click on any class to open a dialog listing all instances of that class in your dataspace

    When to use class navigation

    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.

    diff --git a/docs/user-guide/search-data.ttl b/docs/user-guide/search-data.ttl index 4981fbc..e52adf3 100644 --- a/docs/user-guide/search-data.ttl +++ b/docs/user-guide/search-data.ttl @@ -13,10 +13,10 @@

    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.

    SPARQL endpoint