Before, when importing files, it used to create a collection, like “Protobuf Import” for AT import.
If importing multiple time the same file, it keep it in the same collection, same object, all good.
Now, each time we import something, it create a new collection.
If I import 2 times the “test.json” file, I’ve 2 collections, each with an object “test.json”.
This multiplies unnecessary collections and the risk of duplicate (or more) objects.
5mn and I’ve already a trash space :
It’s really preferable to have only one “Import” collection (or one per type, but that’s also open for discussion).
If you nedd some metadata must be visible, why not use relation? Hop, a view and I have files imported by date or by source.
It’s the default name given to it. You can just rename them
I like the name (or have no problem with it )
But why 1 import = 1 collection?
What is the problem with one collection for all imports? Or one per import type like before?
How to reproduce
(just to be sure to speek about the same thing)
- import a json containing a note named “Testing”
- Observe : you have this note into a “Protobuf” collection
- import this json again
- Observe : you have now 2 note “Testing” into 2 different collection “Protobuf”
- import again, modify and import, import it in a zip with other files, reimport because you’ve forgot something reimport because import bug, etc
- Observe : you are sooo many “Protobuf” collection and sooo many “Testing” files. Good luck
(My space now after some test : more collection than object )
A +1 for a rollback (yes, so +2 from me )
Just because it’s now a pain to test imports…
moved out of the nightly zone