Berlin: Difference between revisions
Importing NeoWiki demo data |
Importing NeoWiki demo data |
||
| Line 1: | Line 1: | ||
NeoWiki follows the Property Graph model. |
|||
| ⚫ | |||
NeoWiki Subjects have NeoWiki Statements that are simple property value pairs. Unlike Wikibase Statements, |
|||
| ⚫ | |||
the data model does not force the presence of Qualifiers, References, and Rank. |
|||
does not make sense for such statements. Even so, this page demonstrates the core capability. |
|||
| ⚫ | |||
{{#table:Population}} |
|||
You do this by adding one Subject for what would have been a Wikibase Statement. This has the additional benefit |
|||
that your Wikibase Statement equivalent has a Schema, which allows you to force said equivalent into a specific |
|||
shape. For instance, you can require that your Population records have a Date, a Measurer, and a list of References. |
|||
| ⚫ | |||
Neo4j has excellent native support for properties on relations. NeoWiki already supports this in its backend, but we |
|||
data in an (editable) table. |
|||
do not have a UI for it yet. Properties on relations are perfect for when the qualified value is a subject. For instance, |
|||
if you have a Person (ie John Doe) that Works For (property) a Company (ie Professional Wiki), their "Works For" relation |
|||
could have start date, end date, and compensation properties. |
|||
Latest revision as of 10:58, 27 January 2026
NeoWiki follows the Property Graph model.
NeoWiki Subjects have NeoWiki Statements that are simple property value pairs. Unlike Wikibase Statements, the data model does not force the presence of Qualifiers, References, and Rank.
Because NeoWiki supports adding as many Subjects to a single page, it is possible to emulate Wikibase Statements. You do this by adding one Subject for what would have been a Wikibase Statement. This has the additional benefit that your Wikibase Statement equivalent has a Schema, which allows you to force said equivalent into a specific shape. For instance, you can require that your Population records have a Date, a Measurer, and a list of References.
We did not optimize for this use case yet. In particular, nice UIs are missing, such as showing the Population data in an (editable) table.