# Introduction This documentation should give you a good overview of how [FrontierNav](https://frontiernav.net) works and how you can take advantage of its features. ### What is FrontierNav? FrontierNav is an interactive wiki. It combines features from wikis, [databases](/editing-data/data-tables), [maps](/navigation/interactive-maps) and more into a single unified platform. Being a wiki, the data is contributed by the community and anyone can [make changes](/editing-data/making-changes) to it. For the latest news and updates, follow the project on [Patreon](https://www.patreon.com/frontiernav) and [Discord](https://discordapp.com/invite/crmfAsJ). FrontierNav is in active development so if you have any feedback or suggestions, feel free to share them. ![Xenoblade Chronicles X Wiki's overview page.](https://2168947178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MLQL2YrEAp0s7HxJmP8%2Fuploads%2Fdm07bMphHDzq4nTxdZ82%2FScreen%20Shot%202022-08-02%20at%2023.06.05.png?alt=media\&token=ba55d502-925e-48b5-8f8d-6c13c52eb22a) ### Navigating this documentation If you would rather skip to a specific page, use the navigation along the left and search along the top. Otherwise, follow the links along the bottom. As FrontierNav is in active development, some images, examples, and demonstrations may not be completely accurate but they should still get the general point across. {% content-ref url="/pages/-MUd7z2tUlaxwDQZMDN-" %} [Navigation](/navigation/navigation-bar) {% endcontent-ref %} {% content-ref url="/pages/-MUd7jHqFl\_LrgYE4n-Z" %} [Editing Data](/editing-data/data-model) {% endcontent-ref %} # Questions and Answers Here's a list of general questions and answers which don't belong in any of the other pages. For topic-specific questions, see the relevant topic's page. ### Who maintains FrontierNav? FrontierNav is developed by [Jahed](https://jahed.dev). It's a wiki platform so the data is maintained by the community. ### How do I contact FrontierNav's owner? You can [contact support](mailto:support@frontiernav.net) via email. Alternatively, for public communication, use the relevant Discussions page on the website. ### Can you add a feature for me? Usually, yes, if it fits with FrontierNav's vision. Just let me know. But there is a large pile of feature requests to get through (over 300 as of writing). This means new features will be prioritised depending on how complicated it is, how often it is requested and how interested I am in it. ### How often is FrontierNav updated? FrontierNav uses [continuous deployment](https://en.wikipedia.org/wiki/Continuous_deployment) so it is updated regularly. You can get news of what has changed by following the project on [Patreon](https://patreon.com/frontiernav). The website's data is also [updated continuously](https://frontiernav.net/change-requests) whenever the community [contributes data](/editing-data/change-requests), like a wiki. ### Does FrontierNav have an offline mode? Not at the moment. To provide an offline mode, you will need to download all of the scripts, data, texts, images and videos in advance. That's a lot of data to download. This may be solved in the future with peer-to-peer networking. ### Can I download FrontierNav as an app? You can install FrontierNav as a web app. To do this, visit [the website](https://frontiernav.net), then open your web browser's menu and choose "Install", "Install app", "Add to homescreen" or something along those lines. A standalone native app is not planned. Maintaining a native app on top of the website is a lot of work. ### Does FrontierNav have a light theme? Not at the moment. A lighter theme may be added in the future, but it is not a priority. Supporting both light and dark themes is a lot of work when adding and re-designing features. It doubles the amount of testing to ensure colours are working well together. # Navigation Drawer Along the left side of every page is the Navigation Drawer. It allows you to access common pages where ever you are on the website. ## Home and Wiki Navigation The Navigation Drawer is contextual. When you choose a wiki, it will show navigation for that wiki. If you have not chosen a wiki, it will show the home navigation. ## Collapse Navigation You can collapse the drawer to save horizontal space using the arrow button on the top right. ## Wiki Switcher Along the left side of the navigation drawer is the wiki switcher. A list of wikis from your library is listed here so you can easily switch between wikis. To add more wikis, see: [Wikis and Games](/navigation/wikis#add-a-wiki-to-your-library). ## Demonstration ![Using the Navigation Drawer (Old Interface)](https://2168947178-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MLQL2YrEAp0s7HxJmP8%2F-MYvr8ghlWpsj5Ue4Uki%2F-MYvrkNw_giWI0Yw6ysd%2Ft1coxm8B25.gif?alt=media\&token=715d821c-c596-48dc-ac54-b4a9e4f98345) # Quick Search Use Quick Search from the [Navigation Drawer](/navigation/navigation-bar) to find Entities, Categories and to perform actions. ## Keyboard shortcuts **CTRL + K** opens Quick Search instantly from anywhere. **ArrowUp**, **ArrowDown** or **Tab**, **SHIFT+Tab** and **Enter** lets you navigate and select results. **ESC** closes search. ## Demonstration ![Using Quick Search (Old Interface)](https://2168947178-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MLQL2YrEAp0s7HxJmP8%2F-MLQMv6pjoMK0BulMjEy%2F-MLQNfLbWa6JhCk69ONr%2Fsearch.gif?alt=media\&token=5d576b98-0592-4643-a5c7-5e0684c5a43a) # Wikis and Games FrontierNav is made up of many wikis. Each wiki has its own data, maps, discussions, settings, community and so on. FrontierNav itself is a wiki which points to other wikis covering specific games.
A screenshot of FrontierNav's "Explore" page showing a grid of trending wikis represented as video game box arts. Below each box art is a set of icons and numbers representing the various types of data within each wiki, such as categories, entities, maps and map features.

FrontierNav's "Explore" page showing a list of wikis and data counts.

## Open a wiki To open a wiki, navigate to its page from FrontierNav's overview page or explore page. You can also use the wiki switcher along the left side of the [navigation drawer](/navigation/navigation-bar). ## Add a wiki to your library On the wiki's overview page, set your status to add the wiki to your library. This will let you access the wiki through FrontierNav's home page, your profile, your library and the navigation drawer. ## Create a new wiki To create a new wiki, see: "[Add Wikis](/editing-data/adding-games)". ## Questions and Answers ### Why do some wikis not have any data? FrontierNav's data is community-driven. This means people contribute data voluntarily to help others. If you would like to contribute data, you can. See "[Changes](/editing-data/making-changes)". ## Demonstration ![Xenoblade Chronicles X Wiki's overview page.](https://2168947178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MLQL2YrEAp0s7HxJmP8%2Fuploads%2Fdm07bMphHDzq4nTxdZ82%2FScreen%20Shot%202022-08-02%20at%2023.06.05.png?alt=media\&token=ba55d502-925e-48b5-8f8d-6c13c52eb22a) # Interactive Maps Interactive Maps let you visually navigate games and find locations. ![An interactive map.](https://2168947178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MLQL2YrEAp0s7HxJmP8%2Fuploads%2FuLzJRfdvmkDiThaCrTSJ%2FScreen%20Shot%202022-08-02%20at%2023.02.14.png?alt=media\&token=8228d2c8-16ad-4853-9ab1-b89eb8495c32) ## Quick Search Like with most pages in FrontierNav, you can use [Quick Search](/navigation/universal-search) to quickly access what you're looking for. Doing so with Interactive Maps open will take you to any relevant markers. ## Toggle Markers LeftClick the "Funnel" icon on the top-right of the map to access the Map Legend in the Sidebar. From there, you can toggle specific types of markers. Some maps may have too many markers so they will be hidden by default. You can see how many types of markers are hidden by the number next to the "Funnel" icon. ## Map Notes Sometimes you will want to mark locations of interest that may not be part of the official dataset. A point of interest you want to come back to, a place with good loot, whatever it is. **RightClick** on the place you want to place a map note and use the Sidebar to enter some text. The first line will be used as a label for the marker. ![Placing a Map Note in Dragon's Dogma](https://2168947178-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MLQL2YrEAp0s7HxJmP8%2F-MMM6NKeR8o3ytgAFgKs%2F-MMM7ml-agS7oFxUOavL%2FPeek%202020-10-19%2002-08-map-notes.gif?alt=media\&token=2a729029-b363-40fa-aa26-8259b94e0f54) ## Coordinates You can navigate to any known coordinates by choosing "Go to coordinates" from the top-right dropdown menu. Coordinates need to be in the "X, Y" or "Longitude, Latitude" format. For example, "10.2, 20.5". You can use coordinates copied from any marker page using the "Copy Coordinates" button. ## Edit Maps To learn more about editing maps, see [Edit Interactive Maps](/editing-data/editing-interactive-maps). # Knowledge Graph It can get easy to lose track of how all the data is connected as you navigate. Knowledge graphs let you view and access those connections directly. Data with common connections are clustered together. ## Category Graph By default the Knowledge Graph will show Categories. Opening an Entity under that Category will open the Entity Graph.

Example of a Category Graph.

## Entity Graph Entity nodes are added to the graph gradually as your navigate. Opening a Category will open the Category Graph. To keep the Entity Graph open, open the Category in a separate sidebar with **MiddleClick**.

Exampe of an Entity Graph.

# Deep Query Sometimes data can be spread across multiple pages, so clicking around to find the data you need can be tedious. Deep Query lets you create queries to find the information you need in a single click.

Example of a Deep Query.

## Query Language Deep Query uses SPARQL for its query language. You'll need to familiarise yourself with its syntax. If you get the syntax wrong, the editor will provide hints to help resolve them. * [SPARQL 1.1 Query Language Documentation](https://www.w3.org/TR/sparql11-query/) ## Example Query The below query for Xenoblade Chronicles X lists all collectibles in Sylvalum along with their time and weather conditions. It uses a range of resources and SPARQL features such as: * "Blank nodes" using `[` and `]`for streamlined relationship traversal. * `FILTER` to show only a specific region. * `OPTIONAL`for showing the description when it's available. Without it, it will only show rows with descriptions. {% tabs %} {% tab title="Query" %} ```sparql PREFIX s: PREFIX se: PREFIX sr: PREFIX et: PREFIX e: PREFIX p: SELECT DISTINCT ?collectible ?rarity_name ?time ?weather ?description WHERE { ?collectible se:type et:Collectible . ?collectible p:CollectibleArea-CONTAINS-Collectible [sr:start [p:Region-CONTAINS-CollectibleArea [sr:start ?region]]] . FILTER (?region=e:sylvalum) ?collectible p:Collectible-RARITY [sr:end ?rarity_name] . ?collectible p:Collectible-TIME [sr:end ?time] . ?collectible p:Collectible-WEATHER [sr:end ?weather] . OPTIONAL{?collectible p:description ?description .} } LIMIT 10 ``` {% endtab %} {% tab title="Result" %}
?name?rarity_name?time?weather?description
Taoman AcidRareEarly MorningRainA chemical produced when rainwater reacts with an unknown airborne substance. It's harmless for living organisms, but can dissolve most inorganic matter.
Mizaria CeleryPrimeEarly MorningRainA rare type of celery that arises only from the crevices of deceased fauna soaked by incessant rain. Its taste depends entirely on the type of carcass from which it grew.
CamocloakUniqueEarly MorningRainThe cloth used to make this cloak imitates its surroundings. It looks to have been invented by an advanced civilization that has since gone extinct.
L-002 Dagoo Heat RayPrimeEarly MorningRainA high-energy laser mounted on the White Whale. It has since been decommissioned, but the scars of battle still stain its scorched barrel.
Rainy CricketUniqueEarly MorningRainA giant cricket that sleeps in the sand and rarely ventures above the surface. Aggressive in its short waking hours, it will attack on sight.
Antorus RoseRareEarly MorningRainA rose with petals that can be used as dyes—which can then be combined to form any color on the spectrum. It is said that these vivid colors will never fade.
{% endtab %} {% endtabs %} ## Resource Identifiers All resources inside the database are referenced in SPARQL as "IRIs"; essentially URLs. IRIs are long, so use `PREFIX` to shorten them. For convenience, the default query includes all prefixes. Below is a list of resource types, how to reference them with prefixes, along with some examples. ## Wiki ```sparql PREFIX w: ``` You can find the wiki identifier by the URL while at a wiki. For example `w:xenoblade-chronicles-x` is the Xenoblade Chronicles X wiki. ### Query Multiple Wikis By default `WHERE` uses the current wiki's resources. The below query adds a second wiki to its query using the `SERVICE` syntax. It lists collectibles in Xenoblade Chronicles which are also available in its Future Connected expansion. ```sparql SELECT ?collectible FROM w:xenoblade-chronicles WHERE { ?collectible a et:Collectible . ?collectible p:name ?name . SERVICE w:xenoblade-chronicles-future-connected { [] xcfc_p:name ?name } } ``` You can also use the `FROM NAMED` syntax. ```sparql SELECT ?collectible FROM w:xenoblade-chronicles FROM NAMED w:xenoblade-chronicles-future-connected WHERE { ?collectible a et:Collectible . ?collectible p:name ?name . GRAPH w:xenoblade-chronicles-future-connected { [] xcfc_p:name ?name } } ``` When using multiple wikis, you will need to specify additional prefixes to access that wiki's resources. ```sparql PREFIX xc1_p: PREFIX xc2_p: ``` ## Wiki Resources The IRI for wiki resources are prefixed by the wiki identifier. For the examples below, replace `wiki-id` with the appropriate wiki identifier. For example, Xenoblade Chronicles X's wiki identifier is `xenoblade-chronicles-x` so its resources looks like ``. ## Entity Type, Category, Table ```sparql PREFIX et: ``` You can find the entity type identifier by the URL while at a category page. For example `t:Collectible` is the "Collectible" category. The below matcher will only match entities under the Collectible category. ```sparql ?collectible se:type t:Collectible . ``` ## Property, Column ```sparql PREFIX p: ``` You can find the identifier for each property predicate by hovering over their columns in the database view. For example, all tables have a `Name` column which has a `name` identifier, so its IRI is `` or `p:name`. ## Entity, Row, Page ```sparql PREFIX e: ``` You can find the entity identifier by the URL while at an entity page. Generally, accessing entities directly isn't too useful. If you don't know the entity identifier, you can match a property to find it. ```sparql ?collectible p:name ?name . ``` ## Relationship ```sparql PREFIX r: ``` You can access relationship data similar to entities using properties as predicates. To traverse relationships, use "blank nodes" syntax to avoid creating intermediate variables for relationships. For example, we can go from a collectible, through its weather relationship property and get the weather's name in a single line. ```sparql ?collectible p:Collectible-WEATHER [sr:end [p:name ?weather]] . ``` ## Relationship Type ```sparql PREFIX rt: ``` Generally, you won't need to directly reference relationship types in your query. ## Schema Resources The above resources are used to access wiki-specific resources. To access metadata such as identifiers, timestamps and pointers, you'll need to use schema resources. ## Database Schema 
PREFIX s: <https://frontiernav.net/schema/>
IRIDescriptionExample
s:typeThe schema type of the subject.
s:entityType
s:relationshipType
s:entity
s:relationship
## Entity Schema ```sparql PREFIX se: ```
IRIDescriptionExample
se:idThe entity indentifiere:gem
se:typeThe entity type of this entity.et:Collectible
se:updatedAtWhen this entity was last changed.2025-01-01T00:00:00.000Z
## Relationship Schema ```sparql PREFIX sr: ```
PredicateDescriptionExample
sr:idThe relationship indentifierr:gem__Collectible-RARITY__rare
sr:typeThe relationship type of this relationship.rt:Collectible-RARITY
sr:updatedAtWhen this relationship was last changed.2025-01-01T00:00:00.000Z
sr:startThe start entity of this relationship.e:gem
sr:endThe end entity of this relationship.e:rare
## Entity Type Schema Not yet supported. ## Relationship Type Schema Not yet supported. # 360° Panoramas 360° Panoramas let you view an area of a game as though you were in the game itself. It's a fun way to get a 3D view of locations and explore the game. It also lets you take verticality into account which can be difficult to consider when using top-down [Interactive Maps](/navigation/interactive-maps). ![A 360° panorama.](https://2168947178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MLQL2YrEAp0s7HxJmP8%2Fuploads%2FtiVFbtzWr5amDS8Ln0PF%2FScreen%20Shot%202022-08-02%20at%2023.03.15.png?alt=media\&token=b6b52175-7832-49ca-8cca-39b39749246a) ## Quick Search Like with most pages in FrontierNav, you can use [Quick Search](/navigation/universal-search) to quickly access what you are looking for. Doing so with a Panorama open will take you to any relevant markers. ## Edit Panoramas To learn more about editing panoramas, see [Edit 360° Panoramas](/editing-data/panoramas). ## Demonstration {% embed url="" %} Preview of 360° Panoramas {% endembed %} # Guides Guides provide a way to navigate a wiki's data. There are different types of guides such as interactive guides and community guides. *** ## Community Guides Community guides are textual guides created by members. Like discussions, anyone can create and share a community guide.

A community guide for Baten Kaitos Origins.

### Create a community guide You can create a community guide by going to the "Guides" page and clicking the "+" icon or "Create a guide" menu item along the top of the page. ### Format text See [Format Text](/editing-data/format-text). Search links are especially useful for guides to link to entities and categories. ### Edit a community guide You can edit or remove your own community guides using the three-dot drop-down menu in the top-right of your guide. *** ## Interactive Guides Interactive guides provide alternative interfaces to navigate the wiki. The most common default interactive guides are the [data tables](/editing-data/data-tables) and [interactive maps](/navigation/interactive-maps). Some games have additional interactive guides, such as [Xenoblade Chronicles X's Probe Simulation](https://frontiernav.net/wiki/xenoblade-chronicles-x/visualisations/maps/probe-guides) and [Animal Crossing: New Horizon's Critter Calender](https://frontiernav.net/wiki/animal-crossing-new-horizons/visualisations/calendar). ### Create an interactive guide If you want to create your own interactive guide and integrate it into FrontierNav, contact support and we can work together on it. # Discussions Discussions let you discuss games and entities with the rest of the community much like a forum.

The top-level discussions page.

### Access discussions You can access the latest discussions by clicking the "Discussions" link in the [Navigation Drawer](/navigation/navigation-bar). Which discussions you see depends on where you're accessing the link from: * Accessing discussions from FrontierNav's page will let you view the latest discussions across all games as well as FrontierNav's meta discussions. * Accessing discussions from a game's page will show the latest discussions specific to that game and its entities. * Accessing discussions from an entity's page will show the latest discussions specific to that entity. ### Create a discussion From the relevant discussions page, you can create a new discussion by clicking the "Start a discussion" text box along the top. ### Reply to a discussion From the discussions page, click on the discussion you want to reply to, then click the "Post a reply" text box below it. ### Yeahs and Likes If you like, agree and want to boost a post, you can "Yeah" it using the "Yeah" button along the bottom of the post. You can also "Unyeah" a post you previously yeah'd with the same button. You cannot Yeah your own posts. ### Format text See [Format Text](/editing-data/format-text). ### Discussion titles Unlike most forums, you do not need to give your post a title. If you want a title, use a Heading 1: ``` # Discussion title Discussion body ``` ### Embed videos You can embed videos from popular services like YouTube using the following markup: ``` [](https://www.youtube.com/watch?v=oHg5SJYRHA0) ``` Make sure the video itself can be embedded and isn't age restricted. Otherwise it's better off as a regular link. # Sign-in Signing-in makes you a member and gives you access to FrontierNav's progress tracking and community features.

The sign-in modal dialogue.

*** ## Create an account The first time you sign-in, a new account will be created for your email automatically. If you use a third-party which provides a name, your display name will also be set to that name. You can customise your account further in [settings](/navigation/account-settings). ### Verify an email address It's important that you have a verified email address to access your account, even when using third-party identity providers. Usually your email will be verified automatically when you sign in. If it hasn't, go to [settings](/navigation/account-settings) and verify it. *** ## Sign-in with email To sign-in, click the "Sign-in" link on the bottom left of the [navigation drawer](/navigation/navigation-bar). It will open the sign-in modal. Any feature which requires signing-in will also open this modal. From the sign-in modal, enter your email address and a sign-in link will be sent to it. Go to your email inbox and open the link to sign in. {% hint style="warning" %} Treat sign-in links like passwords. If you need to copy it, make sure the website URL you're pasting to starts with "". For apps, make sure you're using the official app. {% endhint %} ### Links on mobile If you're on mobile, clicking the email link might not take you to the correct app. Sign in again from the correct app and instead of clicking the email link, copy it, go back to the app and paste it into the field under "Alternative method" to sign in. ### Quota errors If you receive quota errors when trying to sign-in with email, use a third-party. You can try signing in with email at a later date with the same third-party account's email to link them. *** ## Sign-in with a third-party Alternatively you can use one of the listed third-party identity providers to sign-in. While this can be convenient, make sure you know the email address tied to the account so you can sign-in with email when needed. Go to [settings](/navigation/account-settings) to find your email address. ### Using the same email address If you sign-in with email or multiple third-parties which use the same email address, you will sign-in to the same account. ### Removed third-party providers As third-party policies and usage patterns change, they might be removed as sign-in options. If this happens you can use your third-party account's email to "Sign-in with email" and access the same account. *** ## Sign-out To sign-out, go to [settings](/navigation/account-settings), scroll all the way down and double-click the "Sign-out" button. *** ## Questions and Answers ### Can I sign-in with a password? Not at the moment. To avoid dealing with account hijacking, weak passwords, phishing and general malicious intent, FrontierNav avoids using passwords. # Member Profiles Each member has their own profile page which says a bit about themselves and their activity on FrontierNav. ### Access your profile You can access your profile by clicking your account details along the bottom of the [Navigation Drawer](/navigation/navigation-bar). Depending on where you are, you will see a different page: * Accessing your profile from FrontierNav's home will open your full profile. * Accessing your profile from a wiki page will open your wiki profile.

A full user profile with the "Changes" tab selected

### Access other user profiles You can access other people's profiles by clicking their name. Like accessing your own profile, which page you see depends on where you are. ### Wiki profiles Unlike full profiles, wiki profiles will only show details specific to that wiki. ### Customise your profile You can customise the avatar, colour and details of your profile from the [Account Settings](/navigation/account-settings) page. *** ## Questions and Answers ### Can I use my own avatar? Not at the moment. Instead, everyone is given a choice of 360 unique, randomly generated avatars. In short, it's to reduce the moderation burden so that I can focus on building FrontierNav. This approach also keeps avatars distinct and separate from wiki data. # Account Settings Account Settings provide various ways to modify your account and how you use FrontierNav. Some controls include: * Your display name. * Your avatar and colour. * Your location. * Your biography. * Your online status. * Whether to play sound effects at various points. * Whether to send telemetry data. * The email address you use to sign-in. * View your User ID. * View the app version. * Sign out of your account. ### Access the Account Settings page Along the bottom of the [Navigation Drawer](/navigation/navigation-bar), select "Settings" cog or gear icon next to your account name to access the Settings page. If you end up on [Wiki Preferences](/navigation/game-preferences) instead, following the link along the bottom to get to the Settings page. # Wiki Preferences While on a wiki page, along the bottom of the [Navigation Drawer](/navigation/navigation-bar), select "Settings" cog icon next to your account name to access Wiki Preferences. This will let you customise features such as: * [Track Progress](/navigation/completion-tracking) * [Spoilers](/navigation/spoilers) # Track Progress To help keep track of entities you have already found, you can mark them as "Complete" using various interfaces like the Sidebar and [Context Menus](/navigation/context-menus). ### Complete and Reset Multiple Entities You can complete entities in bulk using [Edit Data Tables](/editing-data/data-tables). [Edit Data Tables](/editing-data/data-tables#mark-multiple-rows) and select "Complete rows" from the toolbar. Similarly to reset multiple completed entities select "Reset complete rows" instead. ![Completing multiple entities using drag and select (old interface).](https://2168947178-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MLQL2YrEAp0s7HxJmP8%2F-MYvZFNqmUkc-9KRw3Zn%2F-MYvZHV4YwdauZqBPO2F%2F7PUEzmSuCH.4.gif?alt=media\&token=e09170d1-02c7-46a8-9a6e-3305a5f4b278) ### Reset All Completed Entities If you want to re-play a game and clear all of your completed entities, you can do so from [Wiki Preferences](/navigation/game-preferences). # Spoilers Some content will be marked as spoilers. By default spoilers are visible. You can hide them per-wiki using [Wiki Preferences](/navigation/game-preferences). ### Progressively show spoilers You can gradually reveal spoilers as you play a game and complete entities. Choose the "Progressively show spoilers" option under [Wiki Preferences](/navigation/game-preferences). For more information on how spoilers work, see [Configure Spoilers](/editing-data/configure-spoilers). {% hint style="warning" %} Spoilers are flagged and maintained by the community. Unless if the wiki says so, do not rely on them to keep spoilers out of sight. {% endhint %} # Context Menus You can **RightClick** certain Entity links to access actions for features such as: * [Track Progress](/navigation/completion-tracking) * [Pop-Out Windows](/navigation/pop-out-windows) ![Using a Context Menu](https://2168947178-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MLQL2YrEAp0s7HxJmP8%2F-MLQMv6pjoMK0BulMjEy%2F-MLQO6p938YHZkcl6bgo%2Fcontext.gif?alt=media\&token=a2f3d5a0-2b10-4db7-b225-2146d0f7cd4e) ## Access Default Right Click Behaviour If you would like to access your browser's default right click behaviour, hold the **CtrlKey+ShiftKey** or **CmdKey** while pressing **RightClick**. # Pop-Out Windows You can **MiddleClick** most links, including search results, to open them in pop-out windows without leaving your current page. ![Using Pop-Out Windows (Old Interface)](https://2168947178-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MLQL2YrEAp0s7HxJmP8%2F-MLQMv6pjoMK0BulMjEy%2F-MLQOKRK_9YIiCwrqtEB%2Fpopout.gif?alt=media\&token=ed5072d6-eb30-4200-9332-f06a0b29c182) ## Access Default Middle Click Behaviour If you would like to access your browser's default **MiddleClick** behaviour, hold the **CtrlKey+ShiftKey** or **CmdKey** while pressing **MiddleClick**. # Danger Buttons Some buttons trigger dangerous actions like deleting your data. These buttons are usually coloured red. To avoid accidental triggers they require a **DoubleClick**. ![Example of a Danger Button](https://2168947178-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MLQL2YrEAp0s7HxJmP8%2F-MLQMv6pjoMK0BulMjEy%2F-MLQO6pA9pV1b1MsW5sF%2Fdanger.gif?alt=media\&token=7180be79-f0bd-444b-a81a-da5206559bb8) # Data Model If you want to start contributing data to FrontierNav, it is worth knowing how the data is structured. FrontierNav uses a graph data model for its data which consists of the following concepts. Depending on where and how they are used, they can use different names but still mean the same thing. * Entity Type (Table, Category, Relation, Schema) * Relationship Type (Inner Table, Nested Table) * Property (Column, Field, Attribute) * Entity (Row, Entry, Page, Tuple, Node, Vertex) * Relationship (Link, Reference, Edge) * Data (Cell, Value) ## Entity Type (Category) Entity Types *define* the structure of Entities using Properties. An Item is an Entity Type, whereas a Small Potion is an Entity. Entity Types are called Categories throughout FrontierNav for familiarity with other wiki software. ## Relationship Type Relationship Types *define* a link between two Entity Types in one direction. So **Enemies drop Items** and **Items are dropped by Enemies** is one Relationship Type as they mean the same thing but are read in opposite directions. The first Entity Type *owns* the Relationship Type, so it can point to as many other Entity Types as it wants. However, the linked Entity Types can only point to the first. So Enemies can drop Items and Weapons, but Weapons can't then be dropped by Treasure Chests. To do that, you will need another Relationship Type owned by Treasure Chests. This limitation was introduced to simplify the model a bit to avoid many-to-many spaghetti. This may change in the future as FrontierNav improves its tooling. ## Property Properties *define* the structure of an Entity's Data. For example, an Item has a **price** which is a **number**. Properties can also *define* the structure of a Relationship's Data. For example, an Enemy drops an Item at a certain **rate**. ### Property Types The types of values Properties can define are currently limited to the following: * Text ("Hello", "A sentence", **string**) * Number (0, 1, 2, 3, **number**) * Boolean (yes/no, true/false, **boolean**) * Relationship (references a RelationshipType) * Tunnel (references a Relationship Property **entrance** and a corresponding Property **exit**) * Useful for re-using data from other Entity Types without having to repeat yourself. * Attachment (references a file like an **image**) ## Entity An Entity is something that *exists* in the game world. A Character, Item, Enemy, Mission are all Entity Types, whereas "The Hero", "Small Potion", "Defeat the Dragon" respectively are Entities. ## Relationship A Relationship *links* two Entities together. Both Entities will refer to the Relationship in their Data to link them together. For example, **Black Dragons drop Dragon Scales**. ## Data Data *describes* an Entity. Where Properties define the structure of Data, Data contains the values. For example, a Small Potion has a **price** of **200** gold. Similarly, Data helps *describe* a Relationship: Black Dragons have an **80%** chance to drop Dragon Scales. # Changes FrontierNav is a wiki, so you can change most of the data it provides. {% hint style="warning" %} All changes are local to your device and only visible to you until you create [Change Requests](/editing-data/change-requests). {% endhint %} ## Communicate First If you are making a large number of changes, you should contact the community to share your ideas. Otherwise, it may result in duplicated effort or invalid data. That does not mean you have to have a conversation, more just an announcement so people are aware and can flag any potential problems. ## Change Model FrontierNav's Change Model is append-only, meaning when you make a change, the next change requires the previous change. This ensures that changes are valid as a whole. You can see the changes you have made by opening the My Changes from the [Navigation Drawer](/navigation/navigation-bar). Your changes are only local to you, no one else can see them unless if you create [#change-requests](#change-requests "mention"). ## Save Changes It is a good idea to regularly save your changes to keep a backup. If anything goes wrong down the line, you can always send the save to an Admin to recover your changes. ## Autosaved Sessions Your open changes are automatically saved every 10 seconds for the current session, up to a maximum of 5 autosaved sessions. After which the oldest session is removed. A new session is created every time you reload FrontierNav. Sessions are not shared across browser tabs. Autosaved Sessions are a safety net in case your web browser crashes or you accidentally close your tab. Do not rely on it too much as web browsers have limited storage. After doing substantial work always Save manually to have a safe copy on your device. ## Load Changes You can load your save to **continue where you left off**. That means any new data since your save will not be available. To apply your changes on top of the latest data, you can extract the save with an archive manager of your choice and load the **changes.json** within it. ## Resolve Conflicts When loading a **changes.json** on its own, your changes are re-applied over the latest published data. This means your changes might conflict if there is new data which your changes might overwrite. For example, you might have created a "Small Potion" entity, but then someone else also made one and published it first. Whenever your changes conflict, you will need to discard them to continue. To avoid losing your changes, you will be given the option to **Save** them, after which you can send them to an Admin to fix. ## Rewind Changes If you make a mistake and want to go back to a previous state, you can open up My Changes, **LeftClick** on the change you want to go back to and **LeftClick** "Rewind". This will reset the data and re-apply all of your changes up to that point and discard the rest. ## Change Requests Changes only exist locally on your device. In order to publish your changes for others to see, you need to create [Change Requests](/editing-data/change-requests). # Change Requests Change Requests are how you contribute data to FrontierNav. They are similar to pull requests on GitHub and merge requests on GitLab.

A merged change request.

## View change requests You can see a list of existing change requests by opening the "Changes" page from the [Navigation Drawer](/navigation/navigation-bar). ## Open change requests After you have [made changes](/editing-data/making-changes), in order to publish them for others to see, you need to create a Change Request. You can do this by opening the "My changes" sidebar from the [Navigation Drawer](/navigation/navigation-bar). Once you have made a change request, you can discard your changes. If you need to recover your changes, you can do so by clicking **Load** on the Change Request. This will apply your changes on top of the latest data, similar to [loading a **changes.json**](/editing-data/making-changes). You can save your changes before discarding them if you prefer to keep your own copy. ### Create request chains After creating a change request, you can continue making changes on top of your previous changes without discarding them. When you make another change request, it will be chained to your previous request. Your previous request will need to be merged first before your new request can be reviewed. ## Review change requests Change requests will be in one of these statuses: * Open: The request is awaiting approval by an admin. * Merged: The request has been accepted and merged. * Closed: The request has been closed after a discussion between the admins and author, and won't be merged. Typically a change request is merged within 12 hours. If your change request hasn't had any status updates after 24 hours, contact support as that we're aware of it. ## Merge change requests Merging change requests involves the following automated steps: 1. Load the current database. 2. Apply the changes in the change request to it. 3. Upload the resulting database. 4. Upload any new attachments in the change request. 5. Update the wiki index to point to the resulting database. {% hint style="info" %} Currently only admins can merge change requests. In the future, game-specific admins and editors will be given access too to reduce workload and provide more flexibility similar to other wiki platforms. {% endhint %} # Edit Data Tables Data Tables are the primary interface for editing data. ![A data table.](https://2168947178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MLQL2YrEAp0s7HxJmP8%2Fuploads%2FbnsOJWc3miXTnpkuEhel%2FScreen%20Shot%202022-08-02%20at%2023.04.49.png?alt=media\&token=ccca5de4-41be-4601-82c9-a51cd563fa51) ## Presentation Data Tables are organised as follows based on the [Data Model](/editing-data/data-model): * Table are Entity Types * Rows are Entities * Columns are Properties * Data are Cells. * A Relationship is a Cell under a Relationship Type Column. ## General Usage Use [Quick Search](/navigation/universal-search) to navigate to different Tables and create new ones. **LeftClick** a Column Heading to sort the Rows based on that Column. **RightClick** a Column Heading to configure the property, such as: * Rename column * Edit description * View column identifier * Sort by this column * Hide the column values from the sidebar * Change the order of relationships * Delete column **RightClick** a Row to configure the entity, such as: * Delete row * Move row (currently not supported) **LeftClick** any Cell, then **CTRL + E** to create a new Row. ## Mark Multiple Rows You can mark multiple Rows to perform bulk operations such as removing and filling. **Hold LeftClick + Drag** to mark multiple Rows. **LeftClick** a Cell, then **SHIFT + LeftClick** another Cell to mark a range of Rows. **LeftClick** a Cell, then **CTRL + SHIFT + LeftClick** another Cell to unmark a range of Rows. **LeftClick** the Row Number Cell to mark/unmark a single Row. ## Fill Multiple Cells To speed up data entry, you can: 1. Mark multiple Rows (see above) 2. Select an unmarked Cell 3. Click "Fill" in the toolbar to update the marked Rows with the value of the selected Cell. 4. Unmark the Rows if you want to. Note: The selected Cell cannot be among your marked Rows. For Relationships, filling will add all of the Relationships from the selected Cell to the marked Rows. It won't remove any Relationships. If a Relationship already exists, Fill will fail to avoid inconsistent updates. This will result in a partial fill as the Rows before the failure will be updated. Use [Changes](/editing-data/making-changes#rewind-changes) to unfill those Rows if you want to. ## Drag and Drop Files Some cells, such as Attachments (Images, Files), support drag-and-drop from your File Manager so you do not need to hunt down files you already have open. ![Adding a Preview Image using Drag and Drop.](https://2168947178-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MLQL2YrEAp0s7HxJmP8%2F-MMM6NKeR8o3ytgAFgKs%2F-MMM6hupo8LaxkQYKWYB%2Fdraganddrop.gif?alt=media\&token=fa4132bb-286a-4258-8706-5e3643c503b6) ## Drag and Drop Files to Multiple Cells If you want to drag and drop multiple files across multiple rows on the same column to save time, you can. First [#mark-multiple-rows](#mark-multiple-rows "mention") then select your files in the same order and drag and drop to the first cell. The order you marked rows and selected files must match. When dealing with lots of files select the first item, hold shift, then select the last time. This will select all items in the order they appear between the two items. This is known as Shift-Click. So you can do the following: 1. Sort your table in the same order as the files. 2. Use Shift-Click on the table to select multiple rows. 3. Use Shift-Click on your files to select multiple files. 4. Drag and drop your selected files onto your selected rows. # Edit Sidebars The layout of the Sidebar for any given Entity is based on the order and configuration of its Properties. You can modify the order using the Entity Type Editor, and you can change each Property by using [Data Tables](/editing-data/data-tables) and pressing **RightClick** on a column heading. ## Standard Entity Properties Some Properties come standard with every Entity. These have fixed positions on the Sidebar and can not be moved. These are: * Name (text) - Always in the heading. * Thumbnail (attachment) - Always in the heading. * Icon (attachment) - Not visible in sidebar. Only used in tags and map markers. ## Rename Properties You can rename a Property's name to be more human friendly. Unlike IDs, Property names do not have to be unique. ## Hide Properties You can hide Properties from the Sidebar by marking them as Hidden. This is useful for Properties that are used for aiding editors such as data-mined identifiers. ## List Relationship Properties By default, Relationship Properties will be shown as: * A single row if there is only one relationship. * Multiple Entity Rows if there is more than one relationship. * Hidden if there are no relationships. To ensure the Sidebar always renders Entity Rows for a Property, even if there is only one, mark it as a List. ## Order Relationships By default, Relationships in a List are ordered by the target Entity's **name** Property. You can change this to any other Property, in either ascending or descending order. ## Relationship Rates For relationships with rates, such as item drop rates or enemy spawn rates, if you provide those rates as follows, they will be displayed differently to regular relationships. * Add a relationship property called "Rates" with an "Object" type. * For values, set them as `[{"rate": 25 }]` where "25" is the rate in percentage (i.e. 25%).

An example of Relationship Rates, showing collectible drop rates of a collection point in Xenoblade Chronicles 2.

# Edit Overviews An overview is the textual content shown on an Entity's overview page. Being plain text, they provide a more traditional wiki experience.

Editing an overview.

## Overview editor To edit an overview, click the "Edit" link next to the overview's heading. Here you can edit and preview the text. Once you apply the change, it will be added to your [Changes](/editing-data/making-changes). To publish your changes, you can create [Change Requests](/editing-data/change-requests). ## Overview storage Overviews are stored as Text Attachments. If an Entity Type does not already contain an Overview property, one is create automatically when an overview is edited. ## Default overview When an Entity doesn't have an overview value, a generic sentence is shown instead. # Edit Interactive Maps ## Presentation Maps are organised as follows: * Maps represent other Entities like Areas and Regions. * Map Tiles and Map Images represent Maps. Maps can have multiple of them. * Maps contain Map Features, such as points on the map. * Map Features indicate the location of specific Entities, their target. ## Create Maps Follow these steps to create a simple map: * Choose a game. * Go to "Interactive Maps" * Click "Create a map". It might be under the 3-dot dropdown. * Provide a "Name" and "Image" * Add the map. This will create a Map with a Map Image. Map Images are single large images. For large maps greater than 1MB, you will want to use Map Tiles instead as they load faster. ### Create Map Images As described above, Map Images are single large images. To ensure your Map Images are optimised: * If the map is pixel art or uses flat colours, use PNG. Otherwise use JPG. * Make sure the map has a black background with no transparency. * Use the map's native resolution. Do not make the map bigger or smaller than its original size. Users can zoom in as much as they want if they need a closer look. ### Create Map Tiles If you would like to create Map TIles contact an Admin and send over the image you want to convert. ### Group Maps To group maps together on the map list page: 1. Go to the "Map" table. 2. Click "Edit table" in the toolbar. 3. Change the "Group Property" to the column/property you want to group by. 4. Click "Save changes" at the bottom. This is useful if you want to group maps by area or region so that they are easier to find and navigate. ### Configure Coordinates Coordinates use the follow axis: * Longitude and X is the horizontal axis. * Latitude and Y is the vertical axis. By default, a map will use real world longitude and latitude coordinates for the map where: * (-180,-180) is the south-west corner. * (+180,+180) is north-east corner. The default coordinate reference system (CRS) uses a globe-like projection, so the values on a straight line will be curved, not linear. This is fine for most maps as the specific values don't really matter as long as the map features are in the right place. If a game has a known linear in-game coordinate system for its maps and you know its size and offsets, you can change FrontierNav's coordinate system to match. * If it doesn't already exist, add a "CRS Size" number column to the "Map" table. * Set the value for each map to the game's world size. * Use the width or height of the world, whichever is largest. * By default, north-east coordinates are positive. In games where north-east coordinates are negative, use a negative value to reverse the direction of the axis. As an example, Tears of the Kingdom's full map images are 36000x36000, its mini-map images are 10800x10800. However both use the same 12000x12000 coordinate system, where (-6000,-6000) is south-west and (+6000,+6000) is north-east. So the CRS Size is 12000. If a game's map does not centre on (0,0), you can apply an offset to match. * If they don't already exist, add a "CRS Offset X" and "CRS Offset Y" number column to the "Map" table. * Set their values for each map to match the game's coordinates. {% hint style="warning" %} ### Updating CRS for Existing Maps Any CRS changes will automatically update all existing Map Feature coordinates assigned to the Map so that they remain in the same location. However it will not update coordinates for any existing map notes and links. To avoid this: 1. Create a new Map with the same CRS values as the old map. 2. Move all of the old maps Map Features to the new map. 3. Update the new maps CRS values. 4. Keep the old map so it can still be used by existing map notes and links with the old CRS values. {% endhint %}

"Capital of Mysteria" has inverted coordinates and an offset centre. (CRS Size: -36000, CRS Offset X: 4070, CRS Offset Y: -740)

## Create Map Features **RightClick** anywhere on a Map to place a Custom Marker. From there, you can create a Map Feature and choose an Entity to target. The Target Entity will open when the Map Feature is clicked. ### Customise Map Features Point map features will use its target's Icon and Hue properties by default. When no Icon is available, it will use a plain coloured circle. To use an existing icon from a different property or relationship, change the target's type configuration. See [Edit Sidebars](/editing-data/editing-sidebars). To set an icon using the default configuration, create an "Icon" column with an "Attachment" type set to "Image" on the target table. Then upload icon images to the column. ### Text map features To show plain text instead of an icon, change the Map Feature's "Shape" property to "text" using Data Tables. {% hint style="info" %} Currently only Point features are available. In the future other types of features like Lines, Polylines and Polygons will be made available. {% endhint %} {% hint style="warning" %} ## Legacy Maps The maps for Xenoblade Chronicles X (not Definitive Edition) do not support editing from the Maps view as they are tailor-made. These will be migrated once community editable Maps are able to provide a similar user experience. {% endhint %} # Edit 360° Panoramas ## Presentation Panoramas are organised as follows: * Panoramas represent a single point on a Map. * Map Tiles and Map Images represent Maps. Maps can have multiple of them. * Panoramas contain Panorama Features, such as points of interest. * Panorama Features indicate specific Entities, their target. ## Create Panorama Images Creating in-game panorama images can be tricky depending on the game. See this blog post: * [Generating 360° Video Game Panoramas](https://jahed.dev/2021/12/05/generating-video-game-panoramas/) by Jahed ## Create Panorama Features **RightClick** anywhere on a Panorama to place a Custom Marker. From there, you can create a Panorama Feature and choose an Entity to target. The Target Entity will open when the Panorama Feature is clicked. # Configure Spoilers FrontierNav can [Spoilers](/navigation/spoilers#progressively-show-spoilers) as entities are completed. View the video below to see how to configure data to take advantage of this. {% embed url="" %} Configuring Spoilers {% endembed %} {% hint style="warning" %} Spoiler columns can also be checkboxes. This is a historical feature which will be removed eventually. Using relationships is preferred as you can tie progression together as seen in the video above. {% endhint %} # Format Text You can format most textual content using [Markdown](https://commonmark.org/help/). ## Embed videos You can embed videos from popular services like YouTube: ``` [](https://www.youtube.com/watch?v=oHg5SJYRHA0) ``` Essentially, any link without text will be embedded. Make sure the video itself can be embedded and isn't age restricted. Otherwise it's better off as a regular link. ## Search links You can create links which open [Quick Search](/navigation/universal-search) with the given text pre-filled: ``` [Search text]() ``` Essentially, any link without a URL will open search. This is useful when you want to link to entities and types without needing to worry about specific IDs. ## Markdown reference
TypeOr… to Get
*Italic*_Italic_Italic
**Bold**__Bold__Bold
# Heading 1Heading 1
=========

Heading 1

## Heading 2Heading 2
---------

Heading 2

[Link](https://jahed.dev)[Link][1]
⋮
[1]: https://jahed.dev		Link
> Blockquote Blockquote
* List
* List
* List		- List
- List
- List
  • List
  • List
  • List
1. One
2. Two
3. Three		1) One
2) Two
3) Three
  1. One
  2. Two
  3. Three

Horizontal rule:


---

Horizontal rule:

***

Horizontal rule:

`Inline code` with backticks Inline code with backticks
```
# code block
print '3 backticks or'
print 'indent 4 spaces'
```		····# code block
····print '3 backticks or'
····print 'indent 4 spaces'
# code block
print '3 backticks or'
print 'indent 4 spaces'
# Import Data When you have a lot of external data to input at once, it might be easier to organise it in a spreadsheet or use a script. In those cases, you can import the resulting CSV or JSON directly into FrontierNav. ![Importing a CSV that creates new rows for any unmatched names. (Old interface)](https://2168947178-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MLQL2YrEAp0s7HxJmP8%2F-MLhFk6tzYE7yLYPtej8%2F-MLhHKqrGMNh6XNnh9Ed%2Fimportskillram.gif?alt=media\&token=d8622953-5b5b-4ce4-88d1-d4ebfecffda8) ## Prepare an import Before trying to import anything, use [Edit Data Tables](/editing-data/data-tables) to make sure you have created all the Entity Types and Properties that you plan to import. You might want to [Changes](/editing-data/making-changes#save-changes) in case your import doesn't go to plan or you can [Changes](/editing-data/making-changes#rewind-changes). ### Supported File Formats #### CSV CSVs are a file format that most spreadsheet software can export to so check your "Save As..." or "Export" options and choose "CSV". You MUST have column headings. ``` Name,Price Potion,20 Sword,500 ``` #### JSON If you're using scripts, you can export to an array of JSON objects. ``` [ { "name": "Potion", "price": 20 }, { "name": "Sword", "price": 500 } ] ``` ### Prepare relationship data Often a single spreadsheet column can have multiple values. For example:
EnemyItem Drops
Enemy 1Potion, Sword
Enemy 2Potion, Antidote, Sword
It's best to split these spreadsheet columns up before importing them. So you can have "Item Drop 1", "Item Drop 2", "Item Drop 3". | Enemy | Item Drop 1 | Item Drop 2 | Item Drop 3 | | ------- | ----------- | ----------- | ----------- | | Enemy 1 | Potion | Sword | | | Enemy 2 | Potion | Antidote | Sword | You can then apply multiple Relationship setters to combine them under a single Relationship property. Columns with no value will be safely ignored. If you do not want to do this manually, you can use a spreadsheet formula like `SPLIT(B2, ", ")`. ## Start an import To start an import: 1. Go to the table you want to import data to. 2. Click the triple dot dropdown menu on the top right and choose "Import data". 3. Choose a file and you will be presented with a form. ![The default import form](https://2168947178-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MLQL2YrEAp0s7HxJmP8%2F-MLhieTy6olR7x64tvlY%2F-MLhm4g-xowFoZ_U0Uol%2FScreenshot%20from%202020-11-09%2016-12-47.png?alt=media\&token=c1affac9-50f2-4919-bffd-e13faafbd072) This form may look complicated at first glance. Essentially the import process will: 1. Go through each row of your data sequentially. 2. **Match** each row to an Entity. 3. **Set** properties on the matched Entity from the given columns. First select the Entity Type to import into. After that, select the criteria to **match** an Entity to a row in your file. Finally, **set** the matched Entity's properties to columns in that row. Once you are ready, press the "Import" button. Once you are happy with the import, remember to [Change Requests](/editing-data/change-requests#open-a-change-request). ### Create or ignore unmatched entities If a row does not match any entity, by default it will be **ignored**. You can choose to **create** an Entity instead. However, if doing so, you need to **set** a unique Name property. The import will fail if there is no Name. ### Create or ignore unmatched relationships If you are **setting** Relationships to an Entity and it does not match an existing Relationship, by default it will be **ignored**. You can choose to **create** a new Relationship instead. Unlike entities, you do not need a Name to create a Relationship, but a target Entity must **match**. If you want to **create** the target Entity too, you must **match** a unique Name otherwise it will be ignored. Existing relationships are not removed by default. You can choose to **replace** all existing relationships with the new relationship. ### Handle errors If a row fails to import, an error will be shown and the import will immediately stop. No changes from the import will be applied. # Add Wikis If you would like to contribute data to a wiki that doesn't exist yet, you can create it just like making any other [Changes](/editing-data/making-changes) on FrontierNav. Once your change is merged, a new wiki will be created. To get started, take a look at [FrontierNav's Game Table](https://frontiernav.net/wiki/frontiernav/visualisations/tables/types/Game) and [Edit Data Tables](/editing-data/data-tables). # Organise Data As mentioned previously, FrontierNav uses a graph [data model](/editing-data/data-model). However, as graphs are extremely flexible and lack restrictions, it helps to view the data in a [relational model](https://en.wikipedia.org/wiki/Relational_model) like a spreadsheet. That is why [Data Tables](/editing-data/data-tables) are the primary interface for editing data. Initially, adding data is simple: You create tables and add columns to store values. However, as you introduce relationships between tables, you may end up at a point where you need to think about how you want the data to be organised so that everything is linked in an intuitive way for people to navigate. If you have worked with Relational Databases before, like [PostgreSQL](https://en.wikipedia.org/wiki/PostgreSQL) or [MySQL](https://en.wikipedia.org/wiki/MySQL), then this should be familiar. If not, it is easy to get started. Think of it like a puzzle that you need to untangle. This process is known as [normalisation](https://en.wikipedia.org/wiki/Database_normalization). It takes practice but like most things, the more you do it, the easier it gets. ## Useful Links * [Graph](https://en.wikipedia.org/wiki/Graph_\(abstract_data_type\)) on Wikipedia * [Graph Database](https://en.wikipedia.org/wiki/Graph_database) on Wikipedia * [Relational Model](https://en.wikipedia.org/wiki/Relational_model) on Wikipedia * [Database Normalisation](https://en.wikipedia.org/wiki/Database_normalization) on Wikipedia # Terms of Use These Terms of Use ("Terms of Use", "Terms") apply to our websites and apps (our "Services"). Our Services includes websites at frontiernav.net, and software provided under the FrontierNav brand. ## Our Services FrontierNav is dedicated to encouraging the growth, development, and distribution of free content, and to hosting the full content of these community-driven projects ("Projects") for the public free of charge. However, we act only as a hosting service provider, maintaining the infrastructure and organizational framework. This infrastructure and framework allow our users to build the Projects by contributing and editing content themselves. They also allow our users to reuse that content. As used throughout the rest of the Terms of Use, our services consist of: The Project Websites we host, technological infrastructure that we maintain, and any technical spaces that we host for the maintenance and improvement of our Projects. Because of our role, there are a couple of things you should be aware of when considering our relationship to you, the Projects, and other users: ### We do not take an editorial role Because the Projects are collaboratively edited, the vast majority of the content that we host is provided by users, and we do not take an editorial role. This means that we generally do not monitor or edit the content of the Project Websites, and we do not take any responsibility for this content. Similarly, unless we have expressly stated otherwise, we do not endorse any opinions expressed via our services, and we do not represent or guarantee the truthfulness, accuracy, or reliability of any submitted community content on the Projects. ### You are responsible for your own actions You are legally responsible for your edits and contributions on the Projects, your reuse of content on the Projects, and your use of our services more generally. For your own protection you should exercise caution and avoid taking any actions that may result in criminal or civil liability under any applicable laws. For clarity, applicable law includes at least the laws of the United Kingdom. For other countries, this is determined on a case-by-case basis. Although we may not agree with such actions, we warn users—particularly the editors, contributors, and authors—that non-UK authorities may seek to apply other country laws to you, including local laws where you live or where you view or edit content. We generally cannot offer any protection, guarantee, immunity or indemnification against the application of such laws. ## Privacy Policy We ask that you review the terms of our [Privacy Policy](https://docs.frontiernav.net/privacy-policy), so that you are aware of how we collect and use your information. ## Content We Host * You may find some material objectionable or erroneous: Because we host a wide array of content that is produced or gathered by fellow users, you may encounter material that you find offensive, erroneous, misleading, mislabeled, or otherwise objectionable. We therefore ask that you use common sense and proper judgment when using our services. * The Projects' content is for general informational purposes only: Although our Projects host a great deal of information that may pertain to professional topics, this content is presented for general informational purposes only. It should not be taken as professional advice. Please seek independent professional counseling from someone who is licensed or qualified in the applicable area in lieu of acting on any information, opinion, or advice contained in one of the Project Websites. ## Refraining from Certain Activities The Projects hosted by FrontierNav only exist because of the vibrant community of users like you who collaborate to write, edit, and curate the content. We happily welcome your participation in this community. We encourage you to be civil and polite in your interactions with others in the community, to act in good faith, and to make edits and contributions aimed at furthering the mission of the shared Project. Certain activities, whether legal or illegal under the applicable law, may be harmful to other users and violate our rules, and some activities may also subject you to liability. Therefore, for your own protection and for that of other users, you may not engage in such activities on, or otherwise using, our Projects. These activities include: ### Harassing and Abusing Others * Engaging in threats, stalking, spamming, vandalism, or harassment; * Transmitting chain mail, junk mail, or spam to other users; * Posting or modifying content with the intention to seriously harm others, such as deliberate inducements to self-harm, or deliberate triggering of epilepsy. ### Violating the Privacy of Others * Infringing the privacy rights of others under the laws of the United Kingdom or other applicable laws (which may include the laws where you live or where you view or edit content); * Soliciting personally identifiable information for the purposes of harassment, exploitation, or violation of privacy, or for any promotional or commercial purpose not explicitly approved by FrontierNav; and * Soliciting personally identifiable information from anyone under the age of 18 years, or under the age of majority where you are if higher than 18 years, for an illegal purpose or violating any applicable law regarding the health or well-being of minors. ### Engaging in False Statements, Impersonation, or Fraud * Intentionally or knowingly posting content that constitutes libel or defamation under the laws of the United Kingdom. * Posting or modifying content with the intent to deceive or mislead others. * Attempting to impersonate another user or individual, misrepresenting your affiliation with any individual or entity, hiding your affiliation with any individual or entity when disclosure is required by these terms or local Project policy, or using the name or identifiers of another person with the intent to deceive. * Engaging in fraud. ### Committing Infringement of Intellectual Property Rights * Infringing copyrights, trademarks, patents, or other proprietary rights under the applicable law. ### Misusing Our Services for Other Illegal Purposes * Posting child pornography or any other content that violates applicable law concerning child pornography or child sexual abuse material, or encouraging, grooming, or advocating for others to create or share such material. * Posting or trafficking in obscene material that is unlawful under applicable law. * Using the services in a manner that is inconsistent with applicable law. ### Engaging in Disruptive and Illegal Misuse of Facilities * Posting or distributing content that contains any viruses, malware, worms, Trojan horses, malicious code, or other device that could harm our technical infrastructure or system or that of other users. * Engaging in automated uses of the Project Websites that are abusive or disruptive of the services, violate acceptable usage policies where available, or have not been approved by FrontierNav. * Disrupting the services by placing an undue burden on an API, Project Website or the networks or servers connected with a particular Project Website. * Disrupting the services by inundating any of the Project Websites with communications or other traffic that suggests no serious intent to use the Project website for its stated purpose. * Knowingly accessing, tampering with, or using any of our non-public areas in our computer systems without authorization. * Probing, scanning, or testing the vulnerability of any of our technical systems or networks unless all the following conditions are met: * Such actions do not unduly abuse or disrupt our technical systems or networks. * Such actions are not for personal gain (except for credit for your work). * You report any vulnerabilities to the relevant developers (or fix it yourself);. * You do not undertake such actions with malicious or destructive intent. ## Account Security You are responsible for safeguarding your own password and other security credentials, and should never disclose them to any third party. ## Trademarks Although you have considerable freedoms for reuse of the content on the Project Websites, it is important that, at FrontierNav, we protect our trademark rights so that we can protect our users from fraudulent impersonators. Because of this, we ask that you please respect our trademarks. All FrontierNav trademarks belong to FrontierNav, and any use of our trade names, trademarks, service marks, logos, or domain names must be in compliance with these Terms of Use. All other trademarks referenced in the Projects are the property of their respective owners. Reference on the Projects to any products, services, processes or other information, by trade name, trademark, manufacturer, supplier, or otherwise does not constitute or imply endorsement, sponsorship, or recommendation thereof by us or any other affiliation. ## Licensing of Content To grow the commons of free knowledge and free culture, all users contributing to the Projects or Project Websites are required to grant broad permissions to the general public to redistribute and reuse their contributions freely, so long as that use is properly attributed and the same freedom to reuse and redistribute is granted to any derivative works. In keeping with our goal of providing free information to the widest possible audience, we require that when necessary all submitted content be licensed so that it is freely reusable by anyone who may access it. You agree to the following licensing requirements: ### Text to which you hold the copyright When you submit text to which you hold the copyright, you agree to license it under [Creative Commons Attribution-ShareAlike 4.0 International License ("CC BY-SA 4.0")](https://creativecommons.org/licenses/by-sa/4.0/deed.en). Reusers must comply with this license. The only exception is if the Project edition or feature requires a different license. In that case, you agree to license any text you contribute under the particular license prescribed by the Project edition or the feature. Please note that these licenses do allow commercial uses of your contributions, as long as such uses are compliant with the terms of the respective licenses. Where you own Sui Generis Database Rights covered by CC BY-SA 4.0, you waive these rights. As an example, this means facts you contribute to the projects may be reused freely without attribution. ### Attribution Attribution is an important part of these licenses. We consider it giving credit where credit is due – to authors like yourself. When you contribute text, you agree to be attributed in any of the following fashions: * Through hyperlink (where possible) or URL to the Project to which you contributed (since each Project has a change history that lists all contributors, authors and editors); * Through hyperlink (where possible) or URL to an alternative, stable online copy that is freely accessible, which conforms with the relevant license, and which provides credit to the authors in a manner equivalent to the credit given on the Project Website; or * Through a list of all authors (but please note that any list of authors may be filtered to exclude very small or irrelevant contributions). ### Importing text You may import text that you have found elsewhere or that you have co-authored with others, but in such case you represent and warrant that the text is available under terms that are compatible with CC BY-SA (or, as explained above, another license when exceptionally required by the Project edition or feature). For a list of compatible licenses, see [Creative Commons](https://creativecommons.org/share-your-work/licensing-considerations/compatible-licenses/). You agree that, if you import text under a CC license that requires attribution, you must credit the author(s) in a reasonable fashion. Where such credit is commonly given through change history, it is sufficient to give attribution in the change request summary, which is recorded in the change history, when importing the text. The attribution requirements are sometimes too intrusive for particular circumstances (regardless of the license), and there may be instances where the FrontierNav community decides that imported text cannot be used for that reason. ### Non-text media Non-text media on the Projects are available under a variety of different licenses that support the general goal of allowing unrestricted reuse and redistribution. When you contribute non-text media, you agree to comply with the requirements for such licenses, and also comply with the requirements of the specific Project edition or feature to which you are contributing. ### No revocation of license Except as consistent with your license, you agree that you will not unilaterally revoke or seek invalidation of any license that you have granted under these Terms of Use for text content or non-text media contributed to the Projects or features, even if you terminate use of our services. ### Re-use Reuse of content that we host is welcome, though exceptions exist for content contributed under "fair use" or similar exemptions under applicable copyright law. Any reuse must comply with the underlying license(s). When you reuse or redistribute a page developed by the FrontierNav community, you agree to attribute the authors in any of the following fashions: * Through hyperlink (where possible) or URL to the page or pages that you are reusing (since each Project has a change history that lists all contributors, authors and editors); * Through hyperlink (where possible) or URL to an alternative, stable online copy that is freely accessible, which conforms with the license, and which provides credit to the authors in a manner equivalent to the credit given on the Project Website; or * Through a list of all authors (but please note that any list of authors may be filtered to exclude very small or irrelevant contributions). If the text content was imported from another source, it is possible that the content is licensed under a compatible CC BY-SA license (as described in "Importing text," above). In that case, you agree to comply with the compatible CC BY-SA license. In addition, please be aware that text that originated from external sources and was imported into a Project may be under a license that attaches additional attribution requirements. Users agree to indicate these additional attribution requirements clearly. Depending on the Project, such requirements may appear, for example, in a banner or other notations pointing out that some or all of the content was originally published elsewhere. Where there are such visible notations, reusers should preserve them. For any non-text media, you agree to comply with the applicable license under which the work has been made available. When reusing any content that we host, you agree to comply with the relevant attribution requirements as they pertain to the underlying license or licenses. ### Modifications or additions to material that you reuse When modifying or making additions to text that you have obtained from a Project Website, you agree to license the modified or added content under CC BY-SA 4.0 or later (or, as explained above, another license when exceptionally required by the specific Project edition or feature). When modifying or making additions to any non-text media that you have obtained from a Project website, you agree to license the modified or added content in accordance with whatever license under which the work has been made available. With both text content and non-text media, you agree to clearly indicate that the original work has been modified. If you are reusing text content in a Project, it is sufficient to indicate in the page history that you made a change to the imported text. For each copy or modified version that you distribute, you agree to include a licensing notice stating which license the work is released under, along with either a hyperlink or URL to the text of the license or a copy of the license itself. ## DMCA Compliance FrontierNav wants to ensure that the content that we host can be reused by other users without fear of liability and that it is not infringing the proprietary rights of others. In fairness to our users, as well as to other creators and copyright holders, our policy is to respond to notices of alleged infringement that comply with the formalities of the Digital Millennium Copyright Act ("DMCA"). Pursuant to the DMCA, we will terminate, in appropriate circumstances, users and account holders of our system and network who are repeat infringers on our Projects and services. However, we also recognize that not every takedown notice is valid or in good faith. In such cases, we strongly encourage users to file counter-notifications when they appropriately believe a DMCA takedown demand is invalid or improper. For more information on what to do if you think a DMCA notice has been improperly filed, you may wish to consult the [Lumen Database website](https://lumendatabase.org/). If you are the owner of content that is being improperly used on one of the Projects without your permission, you may request that the content be removed by filing a notice under the DMCA. To make such a request, please email us at . Alternatively, you may make a request to our community, which often handles copyright issues faster and more effectively than the process prescribed under the DMCA. In that case, you can post a discussion explaining your copyright concerns. Before filing a DMCA claim, you also have the option of sending an email expressing your concerns to . ## Third-party Websites and Resources You are solely responsible for your use of any third-party websites or resources. Although the Projects and Project Websites contain links to third-party websites and resources, we do not endorse and are not responsible or liable for their availability, accuracy, or the related content, products, or services (including, without limitation, any viruses or other disabling features), nor do we have any obligation to monitor such third-party content. ## Management of Websites The community has the primary role in creating and enforcing policies applying to the different Project editions. At FrontierNav, we rarely intervene in community decisions about policy and its enforcement. It is possible to notify us of illegal content, or content that violates our Terms of Use (including all policies and other documents incorporated by reference) for other reasons by contacting us directly. However, you can typically make a request directly to the Project's community: this may be more efficient, and is more consistent with our Projects' aim to empower the user community. If you contact FrontierNav with a problem, we will typically explore whether and how existing community-led mechanisms can investigate and, where appropriate, resolve it. In an unusual case, the need may arise, or the community may ask us, to address an especially problematic user or especially problematic content because of significant Project disturbance or dangerous behavior. In such cases, we reserve the right, at our sole discretion (or where legally compelled), to: * Investigate your use of the Projects or our services (a) to determine whether a violation of these Terms of Use, Project edition policy, or other applicable law or policy has occurred, or (b) to comply with any applicable law, legal process, or an appropriate governmental request; * Detect, prevent, or otherwise address fraud, false or unverifiable information, security, or technical issues or respond to user support requests; * Refuse, revert, disable, or restrict access to contributions of any user who violates these Terms of Use; * Ban a user from editing or contributing or block a user's account or access for actions violating these Terms of Use, including repeat posting of unlawful material under applicable law in line with human rights principles; * Take legal action against users who violate these Terms of Use (including reports to law enforcement authorities); and * Manage otherwise the Project websites in a manner designed to facilitate their proper functioning and protect the rights, property, and safety of ourselves and our users, licensors, partners, and the public. Those moderation activities may be informed or performed by software (such as traffic flood ("Denial of Service") protection). In those cases human review is normally available, upon request. In the interests of our users and the Projects, in the extreme circumstance that any individual has had their account or access blocked under this section, they are prohibited from creating or using another account on or seeking access to the same Project, unless we provide explicit permission. Without limiting the authority of the community, FrontierNav itself will not ban a user from editing or contributing or block a user's account or access solely because of good faith criticism that does not result in actions otherwise violating these Terms of Use or community policies. The community and its members may also take action when so allowed by the community or policies applicable to the specific Project edition, including but not limited to warning, investigating, blocking, or banning users who violate those policies. You agree to comply with the final decisions of dispute resolution bodies that are established by the community for the specific Project editions (such as arbitration committees); these decisions may include sanctions as set out by the policy of the specific Project edition. Especially problematic users who have had accounts or access blocked on multiple Project editions may be subject to a ban from all of the Project editions. In contrast these Terms of Use, policies established by the community, which may cover a single Project edition or multiple Projects editions, may be modified by the relevant community according to its own procedures. If you believe we have not satisfactorily acted on a problematic content report, or if you have been subjected to a moderation action that you wish to challenge, you may be able to submit an appeal. Other information about routes of appeal may also be explained to you at the time, or in Project-specific help pages. We reserve the right to suspend (temporarily, or permanently) our handling of reports or other correspondence from users or third parties, whether about allegedly illegal or otherwise problematic content or conduct, or requesting appeals against moderation actions, if such correspondence was made in bad faith, repetitive, unfounded, and/or abusive. In appropriate circumstances, your email address may even be blocked on our email system(s). For less serious cases (e.g. up to three polite emails about one or more meritless complaints), this is likely to be temporary. More frequent or more abusive communications are more likely to lead to permanent measures. ## Termination Though we hope you will stay and continue to contribute to the Projects, you can stop using our services any time. In certain (hopefully unlikely) circumstances it may be necessary for either ourselves or the community or its members to terminate part or all of our services, terminate these Terms of Use, block your account or access, or ban you as a user. If your account or access is blocked or otherwise terminated for any reason, your public contributions and a record of your activities on or in relation to the Projects (including any correspondence you have sent us) will be unaffected (subject to applicable policies), and you may still access our public pages for the sole purpose of reading publicly available content on the Projects. In such circumstances, however, you may not be able to access your account or settings. However, regardless of any other provision in these Terms of Use, we reserve the right to suspend or end the services at any time, with or without cause, and with or without notice. Even after your use and participation are banned, blocked or otherwise suspended, these Terms of Use will remain in effect with respect to relevant provisions. ## Disputes and Jurisdiction We hope that no serious disagreements arise involving you, but, in the event there is a dispute, we encourage you to seek resolution through the dispute resolution procedures or mechanisms provided by the Projects or Project editions and FrontierNav. If you seek to file a legal claim against us, you agree to file and resolve it exclusively in the United Kingdom. You also agree that the laws of the United Kingdom will govern these Terms of Use, as well as any legal claim that might arise between you and us (without reference to conflict of laws principles). You agree to submit to the personal jurisdiction of, and agree that venue is proper in, the courts located in the United Kingdom, in any legal action or proceeding relating to us or these Terms of Use. To ensure that disputes are dealt with soon after they arise, you agree that regardless of any statute or law to the contrary, any claim or cause of action you might have arising out of or related to use of our services or these Terms of Use must be filed within the applicable statute of limitations or, if earlier, one (1) year after the pertinent facts underlying such claim or cause of action could have been discovered with reasonable diligence (or be forever barred). ## Disclaimers At FrontierNav, we do our best to provide educational and informational content to a very wide audience, but your use of our services is at your sole risk. We provide these services on an "as is" and "as available" basis, and we expressly disclaim all express or implied warranties of all kinds, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, and non-infringement. We make no warranty that our services will meet your requirements, be safe, secure, uninterrupted, timely, accurate, or error-free, or that your information will be secure. We are not responsible for the content, data, or actions of third parties, and you release us, our directors, officers, employees, and agents from any claims and damages, known and unknown, arising out of or in any way connected with any claim you have against any such third parties. No advice or information, whether oral or written, obtained by you from us or through or from our services creates any warranty not expressly stated in these Terms of Use. Any material downloaded or otherwise obtained through your use of our services is done at your own discretion and risk, and you will be solely responsible for any damage to your computer system or loss of data that results from the download of any such material. You agree that we have no responsibility or liability for the deletion of, or the failure to store or to transmit, any content or communication maintained by the service. We retain the right to create limits on use and storage at our sole discretion at any time with or without notice. Some jurisdictions do not allow the types of disclaimers in this section, so they may not apply to you either in part or in full depending on the law. ## Limitation on Liability FrontierNav will not be liable to you or to any other party for any direct, indirect, incidental, special, consequential or exemplary damages, including but not limited to, damages for loss of profits, goodwill, use, data, or other intangible losses, regardless of whether we were advised of the possibility of such damage. In no event shall our liability exceed one thousand U.S. dollars (US$1,000.00) in aggregate. In the case that applicable law may not allow the limitation or exclusion of liability or incidental or consequential damages, the above limitation or exclusion may not apply to you, although our liability will be limited to the fullest extent permitted by applicable law. ## Modifications to these Terms of Use Because it may be necessary to modify these Terms of Use from time to time, we will provide notice of such modifications via the Project websites. However, we ask that you please periodically review the most up-to-date version of these Terms of Use. Your continued use of our services after the new Terms of Use become official constitutes an acceptance of these Terms of Use on your part. For the protection of FrontierNav and other users like yourself, if you do not agree with our Terms of Use, you cannot use our services. ## Other Terms These Terms of Use do not create an employment, agency, partnership, joint control or joint venture relationship between you and us, FrontierNav. For the purposes of European Economic Area law, United Kingdom law, or other laws that involve a similar concept, you are not acting "under the authority of" FrontierNav when you use the services. If you have not signed a separate agreement with us, these Terms of Use are the entire agreement between you and us. If there is any conflict between these Terms of Use and a signed written agreement between you and us, the signed agreement will control. You agree that we may provide you with notices, including those regarding changes to the Terms of Use, by email, regular mail, or postings on the Projects or Project Websites. If in any circumstance, we do not apply or enforce any provision of these Terms of Use, it is not a waiver of that provision. You understand that, unless otherwise agreed to in writing by us, you have no expectation of compensation for any activity, contribution, or idea that you provide to us, the community, or the Projects or Project editions. Notwithstanding any provision to the contrary in these Terms of Use, we (FrontierNav) and you agree not to modify the applicable terms and requirements of any free license that is employed on the Projects or Project editions when such free license is authorized by these Terms of Use. If any provision or part of a provision of these Terms of Use is found unlawful, void, or unenforceable, that provision or part of the provision is deemed severable from these Terms of Use and will be enforced to the maximum extent permissible, and all other provisions of these Terms of Use will remain in full force and effect. ## Contact Us If you have questions or suggestions about these Terms of Use, please email us at . We appreciate you taking the time to read these Terms of Use, and we are very happy to have you contributing to the Projects and using our services. *** Text is available under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/deed.en). Adapted from [Wikimedia Foundation Terms of Use](https://foundation.wikimedia.org/w/index.php?title=Policy:Terms_of_Use\&oldid=366676) licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/deed.en). # Privacy Policy This Privacy Policy ("Privacy Policy", "Policy") explains how FrontierNav ("FrontierNav", "we", "us", "our"), collects, uses, and shares information we receive from you through the use of our websites and apps (our "Services"). Our Services includes websites at frontiernav.net, and software provided under the FrontierNav brand. ## Definitions "Personal Information" is information that could be used to personally identify you such as your real name and email address. "Third parties" are individuals, entities, websites, services, products, and applications that are not controlled, managed, or operated by FrontierNav. ## Information We Receive From You ### Account Information & Creation When you create an account on our Services, you will need to provide Personal Information such as your email address. This is used to identify and access your account. If you choose to use a third party sign-in provider, those third parties will on your behalf provide your email address along with additional information such as a profile name and photo which is used to populate your initial public profile. ### Your Contributions When you make a contribution to our Services you are creating a public record. This includes your profile, discussions, change requests, lists and notes. ## Information We Receive Automatically The device and software you use to access our Services may automatically send information such as the type of device you are using, the type and version of your software, your language preference and your IP address. ### IP Addresses When you use our Services, we automatically receive the IP address you are using to access the Internet. Your IP address can be used to infer your service providers and geographical location. ## Information We Collect We may collect some types of information using common technologies such as scripts, web beacons, cookies, and local storage. This includes information about your use of our Services. ## How We Use Information We Receive From You We and our service providers use your information for legitimate purposes. This includes: * To help you share your knowledge with the world and add new features to our Services. * To arrange access to your account and provide you with related service. * To send administrative information to you, such as changes to our policies. * To provide to you custom content, notices and settings and to enhance your experience with our Services. * To use your public contributions, either aggregated with the public contributions of others or individually, to create new features or data-related products for you or to learn more about how our Services are used. * To fight spam, identity theft, malware and other kinds of abuse. * To optimize our Services. * To test features to see what works, understand how users interact with the our Services, track and study use of various features, and analyze trends. ## When May We Share Your Information? ### To Protect You, Ourselves & Others We will access, use, preserve, and/or disclose your Personal Information if we reasonably believe it necessary to satisfy a valid and legally enforceable warrant, subpoena, court order, law or regulation, or other judicial or administrative order. We, or particular users with certain administrative rights as described below, need to use and share your Personal Information if it is reasonably believed to be necessary to enforce or investigate potential violations of our Terms of Use, this Privacy Policy, or any of our Services policies. We may also need to access and share Personal Information to investigate and defend ourselves against legal threats or actions. We may disclose your Personal Information if we believe that it is reasonably necessary to prevent imminent and serious bodily harm or death to a person, or to protect our organization, employees, contractors, users, or the public. We may also disclose your Personal Information if we reasonably believe it necessary to detect, prevent, or otherwise assess and address potential spam, malware, fraud, abuse, unlawful activity, and security or technical concerns. ### If Our Services Are Transferred If we are involved in a merger, acquisition, financing due diligence, reorganization, bankruptcy, receivership, purchase or sale of assets, or transition of service to another provider, then your information may be sold or transferred as part of such a transaction, as permitted by law and/or contract. In the event that ownership of all or substantially all of our Services changes, or we go through a reorganization (such as a merger, consolidation, or acquisition), consistent with our legitimate interest, we will continue to keep your Personal Information confidential, except as provided in this Policy, and provide notice to you via our Services before any Personal Information is transferred. ### To Our Service Providers We use third-party service providers to help run or improve our Services for you and other users. We give access to your Personal Information to these providers as needed to perform their services for us or to use their tools and services. Some of these service providers will have their own policies which are provided by them when they are accessed. ### Because You Made It Public Any information you post publicly on our Services is just that – public. For example, if you put your mailing address on your profile, that is public, and not specifically protected by this Policy. Please think carefully about your desired level of privacy before you disclose Personal Information on your profile or elsewhere. Unless this Policy says otherwise, you should assume that information that you contribute to our Services, including Personal Information, is publicly visible and can be found by search engines. Like most things on the Internet, anything you share may be copied and redistributed throughout the Internet by other people. Please do not contribute any information that you are uncomfortable making permanently public, like revealing your real name or location in your contributions. ### With Your Permission We may share your Personal Information for a particular purpose, if you agree. ## How Do We Protect Your Personal Information? We strive to protect your Personal Information from unauthorized access, use, or disclosure. We use a variety of physical and technical measures, policies, and procedures (such as access control procedures, network firewalls, and physical security) designed to protect our systems and your Personal Information. Unfortunately, there is no such thing as completely secure data transmission or storage, so we cannot guarantee that our security will not be breached (by technical measures or through violation of our policies and procedures). ## How Long Do We Keep Your Data? Once we receive Personal Information from you, we keep it for the shortest possible time that is consistent with the maintenance, understanding, and improvement of our Services, and our obligations under applicable law. In most instances, Personal Information is deleted, aggregated or de-identified after 90 days. Non-Personal Information may be retained indefinitely as appropriate. ## Your rights If you would like to request to access, update or restrict/object to the processing of Personal Information, or receive a copy of your Personal Information for purposes of transmitting it to another organization, you may contact us. We will respond to your request consistent with applicable law. Please note also that you may be able to exercise some of these rights without our intervention. For example, if you are signed-in, you can access and update some of your information from your account settings page and choose some of the information that we collect. ## Changes to This Privacy Policy Because things naturally change over time and we want to ensure our Privacy Policy accurately reflects our practices and the law, it may be necessary to modify this Privacy Policy from time to time. We reserve the right to do so. We ask that you please review the most up-to-date version of our Privacy Policy. Your continued use of our Services after any effective date of a subsequent version of this Privacy Policy constitutes acceptance of this Privacy Policy on your part. ## Contact Us If you have questions or suggestions about this Privacy Policy, or the information collected under this Privacy Policy, please email us at . We appreciate you taking the time to read this Privacy Policy, and we are very happy to have you contributing to the Projects and using our services. *** Text is available under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/deed.en). Adapted from [Wikimedia Foundation Privacy Policy](https://foundation.wikimedia.org/w/index.php?title=Policy:Privacy_policy\&oldid=366672) licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/deed.en).