Feature #2642
open
CSV importer - selectable, inverse and references to vocabularies
Description
- Selectable
- Inverse (for ActorRelation )
- References to vocabularies (ex: PARTHENOS, OFOS, ...)
In case of 'Inverse' I think would be better populate with a relation ( ex: inverse of 'mother of' is 'son of' or 'daughter of' (uuf .. list ot relations !!))
Updated by Alexander Watzinger 2 months ago
- Description updated (diff)
- Category set to Data import/export
- Status changed from New to Acknowledged
- Target version set to 9.2.0
Thank you Enric for this information.
Selectable
This is a relatively new feature. It is also not part of the model and only used for data entry but we might be able to add it to imports.
Inverse (for actor relation)
It might be possible to solve this with the "right" direction at the import data but we will look into it.
References to vocabularies (ex: PARTHENOS, OFOS, ...)
According to the manual, this should be possible (see import) but Bernhard might know more about it.
Currently we are in the middle of a complete rewrite (see #2464) which we plan to release at the end of the year and this might have to wait because of it.
But I added it on the roadmap for later.
About the suggestion 'mother of' is 'son of' or 'daughter of' .. we strongly advise to not use it in that way but instead use "parent of/child of", "sibling of", ...
Gender/sex information should be at the person and not be duplicated in their relations for various reasons.
Updated by Alexander Watzinger 2 months ago
- Start date changed from 2025-10-15 to 2025-01-27
- Follows Feature #2464: OpenAtlas major version 9.0.0 added
Updated by Bernhard Koschiček-Krombholz 2 months ago
Enric, you really put the import to a huge test!
Alex said already everything.
For the Reference systems you can see this entry.
You also have to always keep in mind the order you import the data. Most time it is best to first import Types, then References (Edition, Bibliography, Ext. References), and then the rest.
But, I’m really curious now — how many entries are you importing, and in what format is your data?
Updated by Enric Rodellas 2 months ago
Bernard,
My answer could be too large and disturb this Feature.
I will send a more detailed answer to your mail https://www.oeaw.ac.at/acdh/institute/team/staff-members/bernhard-koschicek-krombholz
- When I was young I was cow milker. I'm proud of. Now I'm 64
- I have been working in Information Technology for 44 years (Cobol, C, C++, perl, SQL, java, VisualBasic, javascript and finally 25 year with Python)
- Specifically I have been working in Geographic Information Systems for 38 years (QGIS, ESRI, Smallworld, GRASS, etc)
- In my free time I collaborate with projects related to history (for example: Spain Civil War > milions of persons, Middle Age)
- I appreciate very, very much your goal to facilitate implementation of CIDOC CRM. A user friendly match between theorical model and technology
- I'm (trying of) to set a DB about Middle Age of my wife thesis where I have to insert some thousands of records, and I need to insert programmatically. (for instance biblio (600 records) and sources (1800 records) are in Zotero) and there are thousand of persons and relations and events.
- I found very practical to use SQL to populate OpenAtlas DB, but I understand the risk.
- I would prefer (instead of CSV) to have an API (an OpenAPI) for populate the DB. (CSV is manual, I have do action one file per one file)
- I'm preparing a lot of data (persons, places, sources, events) to populate OpenAtlas.
- I'm very concerned about symmetry of import and export of data. (dump otion is near, but really is a backup of DB. its not the same)
- Feature 2551 is very important for me. After that I would request for inverse operation: I have a CIDOC CRM file and I want import (by API) all data)
... I can continue wiht a hundred of notes but you have work