Guides
Coming: import other data
Your information may be in Excel spreadsheets, CSV files, ordinary JSON, PDFs, documents, or another database. You should not need to learn a specialist file format just to bring that information into Legra.
A built-in service for importing these sources is coming. It is not yet available. You can prepare an import now by deciding what the source data means and which facts to bring into Legra.
What needs to happen
Importing useful knowledge involves deciding what the source information means. For example, a spreadsheet might contain a person's name and their employer. To connect that information with other data, an import needs to identify the person, identify the organization, and record the relationship between them.
| Source | Preparation involved |
|---|---|
| Spreadsheets and CSV | Decide what rows and columns represent and how to identify the people, organizations, or other things they describe. |
| Ordinary JSON and database exports | Map fields and records to facts, identifiers, and relationships. |
| PDFs and documents | Extract the relevant information, check its accuracy, and retain a connection to the source. |
Keeping a source file and turning its contents into queryable facts are separate steps. Agree which information to extract, who may access it, and how to check it before accepting the result.
What you can do today
If your source system or an external conversion tool can produce , a standard way to express facts and relationships, you can prepare those files outside Legra and follow Import your own RDF files. Review the mapping and resulting facts before importing them.
The RDF upload commands do not perform the spreadsheet mapping or document
extraction described above. Renaming a CSV or PDF to .ttl does not convert it.
If you need a built-in guided import from these other sources, that service is still coming. To try Legra now without preparing your own files, use the supplied sample in Your first Legra example.