You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be very nice to have some metadata for tools, methods, standards and software, repositories to be displayed on hover or links where a click will take you to.
Therefore a person can click on a thing and see what it is exactly.
Do we have the mining data ready for this?
we could display the corresponding entry from the HMC graph
Ideally it would request this information from some information portal API. Since we do not have this, a deployment instance should have the corresponding metadata with it.
The text was updated successfully, but these errors were encountered:
the HDO ontology (Helmholtz digitization onotology) is not yet officially published, but it will be soon. The current development status can be seen on HOB here.
This could be an interesting feature for future releases.
@hofmannv the HDO is also an interesting aspect one could integrate and I have not thought about this.
I thought more about something like you hover with the mouse over 'zenodo': metadata about what this is gets displayed and if you click on it you get forwarded to the zenodo webpage.
The same for all software, methods, repositories and metadata standards.
Because most people won't know what a certain thing (often Abbreviation) stands for and so they could check it out.
If we would have ad some point an information portal where such information is accessible, one could simply link to that, or fetch data from it.
It would be very nice to have some metadata for tools, methods, standards and software, repositories to be displayed on hover or links where a click will take you to.
Therefore a person can click on a thing and see what it is exactly.
Do we have the mining data ready for this?
we could display the corresponding entry from the HMC graph
Ideally it would request this information from some information portal API. Since we do not have this, a deployment instance should have the corresponding metadata with it.
The text was updated successfully, but these errors were encountered: