For states, regions and tourism boards
Every level works in its own area, and all of them benefit from the shared data. Maintain data directly in the hub or run it next to your existing system.
A hierarchy like real tourism
State -> region -> town -> business: every level is a tenant of its own and sees its own part. The separation is enforced in the database (row level security), not just in the interface. A state sees all regions, a region its towns, a tourism board its entries.
Editing events and POIs
For tourism boards without their own content system, the hub is the leading system. You maintain events and POIs directly, with roles and approval. What your editors maintain always beats imports in the golden record. You can already maintain images with their rights information; tours in the editorial interface will follow.
Mixed operation with feratel
Still using feratel? No problem. Technically, the editorial interface is just another source with the highest priority. Data from feratel and your own entries are merged in the golden record, field by field and with provenance.
Duplicates and review tasks
When the same mountain hut comes from several sources, entity resolution detects it and merges the records. When it is unsure, you get a review task and decide yourself.
Switching help
There is an import from destination.one for switching. You do not have to re-enter existing content.
What is coming
- AI-assisted capture (planned): From programme booklets or event lists, AI suggests draft entries. You review and approve.
- Self-service for businesses and organisers (planned): Businesses enter their own details, you keep control over approval.