Hi Flo,
The HDF5 DataPlugin is a Data Store type of DataPlugin, rather than the data file type that is ready for use with the DataFinder. To use the HDF5 DataPlugin directly, you need to create a new Data Store in the DIAdem NAVIGATOR that points to a particular *.h5 data file and knows to use the HDF5 DataPlugin to read it. The result will be that the entire tree view in the DIAdem NAVIGATOR is then used to show just the extended hierarchy in this one *.h5 file. This is what is meant by a Data Store in DIAdem. You can drag the last few hierarchy levels into the Data Portal to load them.
In practice most customers are eager to view their *.h5 data files normally, such that the DIAdem NAVIGATOR shows the Windows folder structure, and they can use the DataFinder to index and query the content of their *.h5 data files. This is possible, but it requires the extra step of creating a post-processing DataPlugin that uses the Data Store HDF5 DataPlugin to read the *.h5 data files and then maps their contents to the 3 level TDM schema that DIAdem and the DataFinder expect. The logic of that hierarchy condensing is defined in the post-processing DataPlugin, and you also have the ability to rename nodes and properties and filter which ones appear in the TDM schema delivered.
If you will post one of your *.h5 data files, I'll be happy to take a look. I have a pretty standard post-processing DataPlugin that works most of the time for customer *.h5 data files.
Brad Turpin
DIAdem Product Support Engineer
National Instruments
