I'd really like to see how smle is developing... can you guys run a live demo at this point? Or maybe provide a Dockerfile (see enviroCar/enviroCar-website-ng#20) to try it out locally?

/Daniel

Within the menue "Edit/View":
If a user is not logged in, then he/she should not have the possibility to edit the description.

Hence, the button "Edit sensor description could/should be hidden completely.". Currently when not logged in, I can click on that button and alter the sensor description using the edit-view. Although the changes cannot be made persistent, this step should not be allowed at all.

When I use the Web browsers "return"/"go backwards in history" function on any routed view, then the application crashes and does not work anymore.

Hi, Im trying to run smle from master branch, I get this error. I've tried many different things but I'm not sure what is causing this issue. Can you please help ?
Errors ___
ERROR in node_modules/@helgoland/core/node_modules/@angular/core/core.d.ts(12351,86): error TS1110: Type expected.
node_modules/@helgoland/core/node_modules/@angular/core/core.d.ts(12351,92): error TS1005: '=' expected.
node_modules/@helgoland/core/node_modules/@angular/core/core.d.ts(12351,94): error TS1005: ')' expected.
node_modules/@helgoland/core/node_modules/@angular/core/core.d.ts(12351,95): error TS1128: Declaration or statement expected.
node_modules/@helgoland/core/node_modules/@angular/core/core.d.ts(12351,96): error TS1128: Declaration or statement expected.

This is just a small improvement.

When creating a new SensorML document, by template, you have the chance to automatically generate a new unique identifier instead of entering a manual value.

If you do NOT do that and leave the field empty, the subsequent edit view of the document allows to enter an identifer manually. It would be nice, if the user gets the chance to let the system generate a new unique identifier within this view also.

The same improvement applies to creating a completely new description (without template). Within the edit view users can create a new identifer, but have to enter a manual value. Again, it would be nice if the system provides a "Generate" button here.

When running the smle I get this error:
in node_modules/@helgoland/caching/src/cache-interceptor.d.ts(4,81): error TS2307: Cannot find module '@helgoland/core'.

In the "Edit/View" menue, when I single click on the arrow of the dropdown, the browser already selects the first element and shows the edit view.
However, when I hold the left mouse button down and hover into the list of available sensor descriptions and then release it, I can select the item I arbitrarily.

By single-clicking, just the dropdown list should appear instead.

I am using Chrome btw.

When changing to menue "Create from Template" the application crashes with error "Error: Uncaught (in promise): Error: Error in ./Templates class Templates - inline template:6:26 caused by: Cannot read property 'identifier' of undefined".

I am unable to select, filter or browse any template.

On the landing page, when I click any of the displayed descriptions an edit view opens, where I can enter stuff.

On the top right of that edit view the "Close" button does nothin when clicking it.

I guess it should hide that edit window and return to the overview of all descriptions, right?

I experience different behaviour when clicking multiple times on the menu buttons.

E.g. when editing a new SensorML document using "Create from template menu" (click on menu, choose template, start editing properties not matter the hierarchy level) and then re-hit the "Create from Template" button the system discards the editing document and goes back to the inital view of the menu, where I can choose the template.

When I do the same using the "New" menu (hit "New", start editing a new SensorML instance), and then re-hit "New", nothing happens. I just remain in the edit view of the created SensorML document.

This behaviour is inconsistent. At least both menu buttons should have the same behaviour. I suggest to change the behaviour of the "New" button. From my POV it should discard all current edits and provide the user with the option to create a whole new document.

An optional improvement of both button behaviour would be to first ask uses whether they are really sure to discard the current document while editing. Otherwise an accidental hit on any of these buttons (actually, here all buttons could be imrpoved inclduing "View/Edit" and "Delete") will cause a loss of all performed steps creating/editing a SensorML document.

When I inspect elements of a SensorML document within the tree structure, I experience a strange collapse behaviour.

E.g. reconstruct the following state of collapsed elements of the sensor description with id "0eea5ed4-792c-69de-0e57-f555f3db6ff9"

Now when I only intend to collapse the element "uuid", nearly everything else collapses as well as shown in the second screenshot:

Is that on purpose? E.g., when clicking on "uniqueID", this only collapses section "uniqueID", which is the expected behaviour.

A new comer needs to know that an example folder exists which he can see and test. Other details would be required too.

When adding contact information to a SensorML document, the system fails when publishing the document as it requires the definition of an "Online Ressource" (attribute "Linkage").

Path is "Contact List --> Resonsible Party --> Contact (Contact Info) --> Online Ressource"

Is it really required?