Importing a TIME_INTERVAL column in Data Laboratory CSV import doesn't enable dynamic features
Bug #659017 reported by
Mathieu Bastian
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Gephi |
Fix Released
|
Wishlist
|
Eduardo Ramos | ||
| 0.7 |
Fix Released
|
Wishlist
|
Unassigned | ||
Bug Description
Thought the use-case of having several TIME_INTERVAL column exists, it would be preferable to restrain to the default one.
When a TIME_INTERVAL is imported for nodes or edges:
- Create the column with the default name (from DynamicModel) if it doesn't exist
- Replace existing data if the column exists
See also bug 654030
Revision history for this message
| Axel Bruns (a-bruns) wrote | #1 |
| Changed in gephi: | |
| status: | Confirmed → Fix Committed |
| Changed in gephi: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Just to add some more detail to this - this goes back to a my original bug report:
In the Gephi Data Laboratory, it's already possible to import CSVs of nodes and edges into Gephi that include time interval columns (in the correct internal Gephi formatting, e.g. "<[10.0, Infinity]>" or "<[1.0, 10.0); [20.0, Infinity]>" - and during the import process, these columns can be declared to contain data of the TimeInterval type.
However, even if the column is set to be of the TimeInterval type, Gephi doesn't do anything with it: the time interval sliders / filters won't act on it...
Axel