Add ability to distinguish manually posted entities in dataset
Not planned
Currently when we manually (re)post entities to datasets, the entities looks just like the entities posted by a pipe. In my project it's quite common having to do some manually posting to fix data anomalies. Some times we get questions about what happened "that day" and so forth. After a few months, it can in some cases be hard to distinguish if the entity update was done by sesam or by one the consultants.
I know we could add our own "system attribute" to the entity, but then that would require everyone to remember to insert it every time they do this. We would also have to add it in any scripts we're using to fix larger volumes.
-
Official comment
We'll extend the dataset repost entity UI so that it add a new $ property to the entity before reposting. The user can then choose to remove it before reposting.
Comment actions -
We have decided not to prioritize this at the current time. One can always add such a property manually. The challenge is that downstream pipes may be affected by the newly added property, e.g. if they use the "keys", "items" and "values" functions . To make that work they need to be made non-sensitive to such changes.
Please sign in to leave a comment.
Comments
2 comments