LV-Database and LV-Forening
Purpose
Section titled “Purpose”After reading this page you know what LV-Database and LV-Forening each do, and which information passes between them.
LV-Database — the events and the game
Section titled “LV-Database — the events and the game”LV-Database is one product that runs as several installations: one per association, each with its own database, its own keys and its own domain. LV-Live is Legendernes Verden’s installation. Legendernes Verden hosts the installations; each association configures its own in the browser.
The system consists of a core that is always there (players, characters, abilities and professions, roles and permissions, settings) and modules that each installation turns on and off — for example events, check-in, tickets, campsite booking, one-shots and a public website. See Modules.
The game world (races, abilities, terms, custom fields …) comes from a template and can be adjusted afterwards, so the system fits both campaigns and one-shots. See Templates.
LV-Forening — the association
Section titled “LV-Forening — the association”LV-Forening is the association’s administrative system: member register and membership fees, accounting and bookkeeping (including ticket sales), and the volunteer list. Today it is used by Legendernes Verden. An association that does not use LV-Forening can run LV-Database without it: membership and volunteers can be kept in LV-Database itself.
How they work together
Section titled “How they work together”The two systems share no database. They exchange data through fixed, versioned agreements, and only what is needed:
| What | Direction | Why |
|---|---|---|
| Members (name, e-mail, Wix member id and membership periods) | LV-Forening → LV-Database | Membership status on players, and the membership requirement for tickets |
| Volunteer list and meal sign-up | LV-Forening → LV-Database | Volunteers’ tickets, meal sign-up and set-up posts |
| Volunteer attendance | LV-Database → LV-Forening | The association can see who turned up |
| Sales feed: ticket sales with amounts and a pseudonym for the buyer | LV-Database → LV-Forening | Ticket sales are booked automatically; the MobilePay payment carries a fixed reference |
LV-Forening owns the member register; LV-Database fetches a copy every 15 minutes and keeps using the most recently fetched data if LV-Forening does not answer. Phone numbers, dates of birth, addresses and payment details are never sent. The buyer in the sales feed is a pseudonym (playerRef), not a name.
The connection is set up under Integrations.
Common misunderstandings
Section titled “Common misunderstandings”- “We need LV-Forening to use LV-Database.” No. LV-Forening is an optional integration.
- “LV-Database is the website.” LV-Database can have a public website (the Website module), but it is first and foremost the system behind it: the player portal and the administration.