---
id: ch10-hub4everybody
type: spine
title: "Hub4Everybody: from project website to evidence infrastructure"
readingTime: 2
standalone: true
core: false
teaser: "Planned as a universal data repository, in the Beta it is the platform's front door, and its library feeds what JackDaw retrieves."
voice: explorer
parent: null
diagram: fig-hub4everybody
recallQ: "What role does Hub4Everybody play in the PoliRural+ Beta, beyond publishing web pages?"
recallA: "It is the main entry point for documents, outputs and service links, with map management through Micka, HSLayers NG and Layman. Documents added to its library feed the retrieval layer behind JackDaw, so it is also part of the evidence infrastructure."
highlights:
  - "Grew out of the PoliRural Hub, which moved from Liferay to Wagtail CMS"
  - "Map management: Micka (metadata), HSLayers NG (map composition), Layman (layer publishing)"
  - "Its library feeds JackDaw's retrieval; curation and metadata quality now set its value"
  - "Reused in BioClima, INTERESH and, as hybrid local instances, KijaniSpace"
status: accepted
concept: spatial-data-infrastructure
lang: en
lens: generic
depth: standard
formalism: none
visuality: balanced
lengthBand: standard
genre: explainer
state: edited
carriers: prose|diagram
---

**Hub4Everybody** grew out of the PoliRural Hub, whose user portal moved from Liferay to **Wagtail CMS** to make content easier to manage. D1.1 describes it as a generic framework that is "now the base for many new solutions ranging from Web pages to commercial platforms" (D1.1 §2).

## Map management built in

D1.1 names three components (§3.2):
- **Micka**, a metadata catalogue and search engine that handles INSPIRE metadata and harvests from CSW and WMS sources;
- **HSLayers NG**, a framework for interactive web maps that combine WMS, WFS and vector data;
- **Layman**, which publishes layers from desktop GIS or the web, with access control and support for OGC standards.

## Plan and reality

D4.1 planned the Hub as a **universal data repository** that would feed JackDaw, use Magpie for data discovery, analyse texts for named entities and policy changes, and add AI to e-learning (§6.1). In the D4.2 Beta, the Hub is the **main entry point**: a place for communication, publications, documents and service links. It has changed "more in content scope than in platform logic". One part of the plan is now running: documents added to the PoliRural+ library feed the retrieval layer behind [JackDaw](#c/jackdaw), so the Hub is "not only a publication surface, but also part of the evidence infrastructure" (D4.2 §3.1).

The limit is editorial. As the library grows, its value depends on consistent classification, metadata quality and curation. Without them, a bigger repository gets harder to navigate (§3.1).

## Reuse elsewhere

BioClima uses the Hub to publish data, methods and training materials. INTERESH can reuse it for soil-health Living Labs. KijaniSpace relies on hybrid deployments, with local instances or adapted portals where cloud access is unreliable (D4.2 §9.2, §9.3, §9.5).

**Sources:**
- D1.1 Project Web Pages Update, §2 From PoliRural Hub to Hub4Everybody; §3.2 Map management. [PDF](https://www.poliruralplus.eu/docs/139/Attachment_0_53.pdf)
- D4.1 PoliRuralPlus platform design, §6.1 Hub4Everybody Evolution. [PDF](https://www.poliruralplus.eu/docs/162/D4.1_PoliRuralPlus_platform_design_v1.pdf)
- D4.2 PoliRuralPlus Platform Beta, §3.1 PoliRuralPlus Hub / Hub4Everybody evolution; §9.2; §9.3; §9.5. [PDF](https://www.poliruralplus.eu/docs/421/D4.2_PoliRuralPlus_Platform_Beta.pdf)