Skip to main content

Product Ideas Pipeline

1170 Ideas

Viet LePractitioner

Cognite Data Fusion: Explore Assets search and hierarchy view suggestionsImplemented

Search results in the hierarchy view of Explore Assets is difficult to use. It’s almost impossible to find what you are looking for in a very large/deep hierarchy. We are almost always resorting to the list view and disregarding the hierarchy view entirely since even after searching, one finds themselves scrolling and scrolling to find yellow matches. Because the hierarchy view also shows close matches, the view is littered non-exact matches.After finding the asset, you can only view children. There is no way to navigate to the parent from the asset view. It is quite useful for us to find an asset and be able to view the ancestry tree to the root and its children.The ONLY way for us to get the ancestry view of a particular asset goes like: Explore Data → Assets Search Skip Hierarchy view, use List View instead View Details of the Asset, copy the External ID Open Filters Put External ID in filter Finally have a hierarchy view with only the ancestry of a particular Asset I have some suggestions that may help bring some usability into search.  An option to show exact matches only… for times I know exactly what I am looking for. (99% of the time) Similar to Find in a document search, there needs to be a Next and Previous button that auto-focus on the next match. There needs to be a way to navigate up and down the ancestry tree. One can only descend from Asset to Children. It is impossible to navigate from Asset to Parent. Instead of a Children tab, perhaps just show the Lineage/Ancestry of all Assets in this family tree? Perhaps give the option to show how many degrees up and down from the current asset, in case there are hundreds or more in a family. We are not able to search by ID, this would help allow us to find the exact search. Search box results should not reset, such as the user’s position or search text, via actions in an expanded sheet on the right. EX: Have a very large hierarchy. Search for an Asset via text in Hierarchy view (no filters), something that required scroll down to middle of search results, click on it. Its details are expanded in a sheet on the right. Click any Tab in the sheet. (Children, Asset, …) Search text and position in the search results are fully reset.

Convert PDF to SVGClosed

I have quite a few engineering diagrams that have been annotated in CDF and now we need to convert them to SVGs in order for some third party application to read them. The API supports this, but the Python SDK does not, or at least not directly. It is possible to force the behavior, but it requires a cumbersome workaround to “trick” the SDK.The SDK seems to expect that the convert job is the next after detect, in theory this makes some sense, however in reality this is not how it will be done. The process will be to detect annotations, then get them approved, then generate the SVG file. The middle step is a manual and the convert job will be run as a separate pipeline.As shown below, the API supports this by having the feature that we can send in the file and the annotations, the input for the SDK is the output of detect. It is possible to replicate the required input, but it is cumbersome. Is there a way to more simply use the files and the annotations through the SDK to convert the files after the fact?Ideally I would want to do something like this:files = client.files.list(data_set_external_ids=docDataSetExtId)ext_ids = [f.external_id for f in files]flt = AnnotationFilter(annotated_resource_type="file", annotated_resource_ids=[{"externalId": ext_id} for ext_id in ext_ids])annotations = client.annotations.list(flt, limit=-1)# Thisclient.diagrams.convert(files, annotations)# or like thisfor file in files: flt = AnnotationFilter(annotated_resource_type="file", annotated_resource_ids=[{"externalId": file.external_id}]) annotations = client.annotations.list(flt, limit=-1) client.diagrams.convert(file, annotations)# Or even just having the SDK handle all of it in the background (best option for me)# And then the SDK or CDF itself just retrieves all annotations linked to the fileclient.diagrams.convert(external_id=file.external_id) https://cognite-sdk-python.readthedocs-hosted.com/en/latest/contextualization.html#convert-to-an-interactive-svg-where-the-provided-annotations-are-highlightedhttps://api-docs.cognite.com/20230101/tag/Engineering-diagrams/operation/diagramConvert