a ; ; "2026-09-29T09:52:54.422Z"^^; ; "Step-by-step guide to installing and uninstalling packages"; "Manage packages"; ; . a ; "
\n

Step-by-step guide to installing and uninstalling packages

\n
\n info\n
\n

Package management requires write access to the dataspace's settings document, which in practice means the owner of the dataspace.

\n
\n
\n

Packages were introduced in LinkedDataHub 5.2. Since 5.10 they are installed declaratively: a dataspace imports a package with a single ldh:import triple in its settings. The dedicated install/uninstall endpoints, and the package Actions menu that drove them, have been removed.

\n
\n

Install a package

\n

Installing a package adds new functionality to your dataspace by importing its ontology and stylesheet. Packages are published under https://packages.linkeddatahub.com/, with their sources in the packages/ directory of the LinkedDataHub-Apps repository.

\n
\n
\n \n \n
\n
\n

Follow these steps to install a package through the web interface:

\n
    \n
  1. Open the end-user dataspace of your dataspace and make sure you are logged in
    2. \n
  2. Click the settings dropdown button in the right section of the navigation bar
    3. \n
  3. Select Dataspace from the dropdown menu to open the Dataspace settings modal
    4. \n
  4. Scroll down to the Packages section, which lists the available packages with their descriptions
    5. \n
  5. Tick the Installed checkbox of the package you want to install
    6. \n
  6. Click Save
    7. \n
\n

The page reloads with the package applied. The checkboxes are inputs of the settings form, so several packages can be installed and uninstalled in a single Save.

\n
\n \n
\n
\n
\n

Uninstall a package

\n

Uninstalling a package removes its ontology and stylesheet from your dataspace. Data you created using the package vocabulary remains but may not display or function correctly without the package.

\n
\n
\n \n \n
\n
\n

Follow these steps to uninstall a package through the web interface:

\n
    \n
  1. Open the Dataspace settings modal as described above
    2. \n
  2. Find the package in the Packages section
    3. \n
  3. Untick its Installed checkbox
    4. \n
  4. Click Save
    5. \n
\n
\n \n
\n
\n
\n

Verify the installation

\n
\n info\n
\n

Installing or uninstalling a package takes effect on the next request — the package ontology joins the dataspace's imports closure and its stylesheet is composed into the dataspace stylesheet. No restart is needed.

\n
\n
\n

After installing a package, verify that it was applied:

\n
    \n
  1. Reopen the Dataspace settings modal and check that the package's Installed checkbox is ticked
    2. \n
  2. Check that the ldh:import declaration was stored by fetching the settings document:\n 
    ldh get \\\n  --accept text/turtle \\\n  \"https://localhost:4443/settings\"
    \n

    The output contains an ldh:import triple with the package URI as its object.

    \n
    3. \n
  3. Check that the package ontology joined the imports closure by querying the ns endpoint — for the taxonomy editor package, the\n skos:Concept constructor becomes visible there:\n 
    curl -k -G \\\n  -E ssl/owner/cert.pem:\"$owner_cert_password\" \\\n  -H \"Accept: application/sparql-results+xml\" \\\n  \"https://localhost:4443/ns\" \\\n  --data-urlencode 'query=ASK { <http://www.w3.org/2004/02/skos/core#Concept> <http://spinrdf.org/spin#constructor> ?constructor }'
    \n

    SPARQL queries fall outside the ldh command set, so this one uses curl with the PEM certificate.

    \n
    4. \n
  4. In the end-user dataspace, check that package-specific classes are offered by the Create expand_more dropdown
    5. \n
  5. If the package includes a stylesheet, verify that its custom UI elements are rendering
    6. \n
\n
\n
\n

Edit the package ontology

\n

On the first request after the import, the package ontology is copied into a document of your dataspace's admin dataspace, under its\n ontologies/ container and named after the package path — for the taxonomy editor, https://admin.localhost:4443/ontologies/editor-taxonomy/.\n That document is the package ontology as far as your dataspace is concerned: its constructors, constraints and views are edited there the same\n way as those of your own namespace ontology, and a change takes effect after the ontology cache is cleared.

\n

The copy is taken once. A newer version of the package does not reach a dataspace that already imported it; to pick it up, delete the\n ontologies/ document, clear the ontology cache, and let the next request materialize the package again — edits made to the document are lost with it.

\n 
ldh delete \"https://admin.localhost:4443/ontologies/editor-taxonomy/\"\nldh admin clear ontology
\n
\n
\n

Customize package behavior

\n

Packages may include custom XSLT stylesheets that affect how data is displayed. You can further customize the behavior by:

\n \n

See the Change layout guide for detailed instructions on stylesheet customization.

\n
\n
\n

Troubleshooting

\n

Installation fails

\n

If the Save or the ldh patch is rejected:

\n
    \n
  • Verify you are logged in with an agent that has write access to the dataspace's settings
    • \n
  • Verify the package URI is correct and dereferenceable, and that its metadata declares lds:ontology and ac:stylesheet
    • \n
  • Review the error message — a rejected settings update reports the constraint violation that caused it
    • \n
\n

Package functionality not visible

\n

If installed package features are not visible:

\n
    \n
  • Reload the page — the stylesheet is composed on the next request, but the browser may still hold the previous one
    • \n
  • Clear the browser cache if stylesheets are not updating
    • \n
  • Verify the package ontology is in the imports closure by querying the ns endpoint as shown above
    • \n
  • Check that you have appropriate permissions to view package resources
    • \n
\n
\n

Read more about how packages work.

\n
"^^ .