Impact 2024: The Industrial Data and AI Conference for and by Users | Nominate Speakers Now for a Ch...
When creating interactive engineering diagrams on the Cognite web UI, we have the option to select between standard and advanced model.It would be beneficial to have the possibility to combine this with customized entity matching and be able to choose from available feature types (such as "simple", "bigram" etc.).This option would be just as, if not more, useful as the advanced detection model.
Currently, when uploading files through the CDF web UI we have the option to provide the dataset ID.It would be nice to replace the textbox with a dropdown showing the dataset names we could select from (similarly to other places on the web UI where the dataset can be filtered). It is a bit annoying to have to search the dataset first, copy the ID and paste it to the textbox.Some more ideas to consider:dropdown or search-box to select label(s) as well, common for a group of files to be uploaded option to provide metadata key + values, common for the group of files to be uploaded option to set the filename (or the filename + some common suffix) as the external ID for each file from the group of files to be uploaded, or set to an arbitrary string if it is just a single file
On the ‘Interactive Engineering Diagrams’ page in the Cognite web UI we can see the list of diagrams pending approval. It would be nice to see the list of approved diagrams too, and to be able to filter for approved vs. pending.I noticed that if both the:Pending interactive engineering diagram Interactive engineering diagram labels are added (through the APIs) to a diagram then it will show up in the list. Refer to the screenshots below.I’m assuming this may be a bug, because a diagram shouldn’t have both labels at the same time. So once a contextualization is approved, it will have only the Interactive engineering diagram label and it should show up in the list.
Is it a good practice to execute transformations from a Cognite Function?Our team implemented a Cognite Function which executes transformations on tables from Cognite RAW. We chose this solution as we wanted to parametrize the SQL query of the transformation, essentially applying a different filter on raw tables every time.Also, it would easier for the end user, e.g. a plant operator, to provide a JSON input to the function then to edit the query every time in multiple locations. E.g., if the JSON is:{ "plant": "Plant.1", "equipment": "equipment.1"}the user can just change the ID for the plant and equipment. Furthermore, these values can be validated by the function before making the replacements in the query and executing the updated transformations.Let me know your thoughts!
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.