Skip to content

mitwelten/mitwelten-deployment-manager

Repository files navigation

Mitwelten Deployment Manager

WebApp to manage deployments of hardware nodes (sensors, cameras, etc.) and related records.

Nodes

A node associates a unique label / ID (like 4242-2323) to a hardware device. The node record stores data on type, technical specifications, serial numbers, and simiar identifiers.

The menu-iterm Nodes and the route /nodes shows a list of all nodes. Use the filter form (open with Filter nodes button or f-key) to narrow down the list. Use the Clear filters button (c-key) to clear the filters. Filter options: Label / ID, node type (like audio), platform (like Audiomoth), wether the not is/was ever deployed.

list-nodes Nodes list view

To view details of a node, click on the corresponding list entry. This view shows all details stored in the node record plus the full URL to directly access those details. Click on the link to copy it to the clipboard.

detail-node Node detail view

To edit a node, click the pencil icon in the left column of the list. Editing a node record only concerns the information related to the node itself, not to its deployment. The edit form can be used to delete the node as well.

To add a new node, use the Add node button (a-key) item or the node/add route. The magic button auto-generates node labels in the correct format.

To deploy a node, click the deploy node button in the left column of the list. This will lead to the deployment add/edit form (see below).

Deployments

A deployment describes the location and timespan in which a specific node is deployed "in the field". An optional description gives context to that deployment. Tags are used to group deployments together. Such a group of nodes could be 4 PoE cameras, A storage node and the 4G accesspoint used to connect those nodes and provide internet connectivity. In that case a tag describing the setup/location briefly would be added to all corresponding nodes.

The menu-item Deployments and the route /deploymnets shows a list of all deployments. Similar to the nodes list, you may use the filter form (open with Filter deployments button or f-key) to narrow down the list of deployments. The fiter options include tags (for finding groups of deployments / nodes), node label / ID, node type and node platform. Use the Clear filters button (c-key) to clear the filters.

To edit a deployment, click the pencil icon in the left column of the list. To add a new deployment, use the Add deployment button (a-key) item or the deployments/add route.

list-deployments Deployments list view

Tags

Tags are used for multiple purposes: To group deployments into units of dependent devices (for example a WiFi Accesspoint, Camera Nodes and an Aggregator Node), and to mark/tag notes on the map (discover.mitwelten.org). The tag list view gives an overview of all existing tags with number of assignments to either deployment or note records.

list-tags Tags list view

Use the filter to narrow down the list by name. The tags names can be edited in this view. Tags that are not associated to any record can be deleted using this view. To add new tags use the corresponding application (i.e. edit/add a deployment or edit/add an entry on the map).

Environments

Environment entries hold numeric characteristics of measurement locations, describing the area near mitwelten deployments.

list-env Environment list view

The menu-item Environments and the route /environments shows a list of all Environment entries. The view can be switch to display a map of all records using the list/map toggle on the top right. To filter the entries, open the filter view using the looking-glass button (f-key) on the top right. Use the Clear filters button (c-key) to clear the filters. To add a new entry, using the Add an environment entry button (a-key) on the top right.

map-env Environment map view

filter-env Filter form for environment entries

Running / Building

  • Run ng serve for a dev server. Navigate to http://localhost:4200/. The application will automatically reload if you change any of the source files.
  • Run ng build to build the project. The build artifacts will be stored in the dist/ directory.