search

DISSINET / InkVisitor

An open-source, browser-based front-end application for the collection of complex structured data from textual resources in history and the social sciences into a RethinkDB database for further analysis.
BSD 3-Clause "New" or "Revised" License
10 stars 3 forks source link

Change import behaviour when importing entities of some type into a new deploy #1987

Open davidzbiral opened 8 months ago

davidzbiral commented 8 months ago

We don't want connections to break. If you import Cs and As, then also import entities they link to in Refs and Metaprops and meta Relations. This in Persecutio is bad - WordNet reference (V entity) was lost: obrazek Correct behaviour is probably new UUID, but same string in the Value label, no?

adammertel commented 8 months ago

@jancimertel this was already fixed in the import script, right?

adammertel commented 8 months ago

@davidzbiral What about a situation when a C has a P entity inside a meta prop. In such a case, this P entity is being imported as well. But should the P entity get the a ref to the R: DISSINET Database (DDB1)? EDIT: Probably this situation never happens - C and A entities are not directly linked to anything else than C and A through props and relations (?)

davidzbiral commented 8 months ago

@adammertel Good that you are thinking about this. If an entity is referenced from meta props, (meta) relations or (meta) references, then it should be imported, but the script should produse a log notifying this, and the owners (old and new) should get the list of entities (uuid & label) thus imported.

Regarding the UUID of the old deploy: exactly, such an entity should get a new UUID, but be referenced to the old one in the same way that you are using for Cs and As, i.e. through adding a Reference, and the UUID as character string in the V label.