Dashboard

The start tip: which jobs to create first

On a new installation the Dashboard opens with a start tip: four ways to begin — try one library, discover every site or OneDrive, prepare the migration from rules, discover or migrate from a list. Under them:

Business Intelligence: a line that links down to the Dashboard's Business Intelligence section, where it all comes together — what content there is, what has been migrated and what has not.
Digital operational resilience: a Migration job that runs every night keeps an independent, current copy, copying only what changed — drawn as a week of runs — and Run now for the day the copy cannot wait for its next run.
Job Import: a job made by hand beside a Job Import, and the import in five steps — pick the scope, set the rules once, run it, a job for every library, all of them in Power BI.

Each blue ? in it offers the common questions of its own topic in the help panel, and Open the Jobs tab goes straight to where the jobs are created. The tip is at most 24 cm tall; in a narrow window it scrolls within itself.

The tip stays until it is closed with Close this start tip. A confirmation asks first; closing it hides it for you only — the other administrators still see it — and the notification that follows leads to Reopen the start tip on the Settings tab. See Which jobs to create first

Job figures

Six tiles below the file figures count the jobs, three to a row, each with its number and the status it counts as a quiet pill — grey while the tile counts none: Running jobs, Ready jobs and Jobs on hold, then Deferred jobs, Disabled jobs and Finished jobs. Disabled jobs counts the jobs switched off, whatever their status; Finished jobs counts the Finished jobs, whose last run is over. Click a tile to open those jobs on the Jobs tab — Disabled jobs opens it with Readiness set to Disabled.

Rest the pointer on Running jobs, Ready jobs or Jobs on hold for what their Migration and Test Migration jobs would move, estimated: files, versions and volume, and how many jobs were counted at the average. Each job counts with its latest Discovery figures, or else with what its latest finished migration moved, or else at the average job. The tiles themselves show only the count and the status; Deferred jobs has no estimate.

Archived jobs are left out of every count, as the Jobs tab leaves them out, so a tile and the tab it opens agree. Rest the pointer on a tile to see how many archived jobs it leaves out; the Jobs tab shows them when its Arch. filter does.

Rest the pointer on a tile or a figure for its card: what it counts, the exact numbers, and what is left out as archived.

Runs

Under the tiles, Runs counts the runs the Run History tab lists, archived ones left out. Its switches choose which runs — Latest for each job's latest, and the modes and results — and are the Run History tab's own filters: a click on the number opens the tab with them set, listing exactly the runs counted. Its blue ? brings up the questions about it.

See Count and filter runs on the Dashboard

File figures

Four figures, two to a row at the top under the heading Files, jobs and runs — Discovered and Migrated, then Test migrated and Issues — the one heading over the file figures, the job tiles and the Runs box, with the Dashboard's blue ? after it — each with its icon, its number, its label and the total volume beside it, and the number of versions in a line under them. From 1,000 up a number shows short — 637.2M, 5.4K; rest the pointer on a figure for its card, with the exact figures and what moves them; volumes on the figures, the job tiles and their cards show two decimals. Click the figure to pin its card: it stays, with a button that opens the jobs of its mode on the Jobs tab, whatever their status — on Migrated and Test migrated also the jobs that restore (or test a restore) and those runs, on the Run History tab; Issues opens the File Issues tab.

Discovered, Test migrated and Migrated come from the BI data: SMART Migration counts the files in its BI tables and reports the totals to the app after every run, and again once deleted runs are purged. Each file is counted once, in the File status of the last run that handled it — as the Power BI report shows it — so the three figures move together:

Figure	What it counts
Discovered	The files found and not migrated yet: those in the File status `Discovery Report`. It goes up when a Discovery finds new files, down when files are migrated or test migrated, and up again when a migrated file has changed at its source and a Discovery finds it.
Test migrated	The files in the File status `Test Migration`: tried against their destination by a Test Migration, not moved — and the files in the File status `Test Restore`, compared with their source by a Test Migration with Restore on, not copied back, added together. Its card shows the two apart, under Test migrated and Test restored. A file migrated afterwards moves on to Migrated.
Migrated	The files in the File status `Migration`, each once — however often, or to however many destinations, it was migrated — and the files in the File status `Restore`, copied back from Nextcloud to their source by a restore run (see Restore), added together. Its card shows the two apart, under Migrated and Restored.
Issues	The issues recorded against the runs, as the File Issues tab lists them — counted by the app itself.

Three volumes. The cards of Discovered, Test migrated and Migrated give File volume (current) — the current files' own volume — Version volume — their version history — and Total volume, the two together, which is the volume under the label.
Last reported. The card says when SMART Migration last reported the BI data, and how many deleted runs it still has to purge.
Deleted runs not purged yet. When you have deleted Discovery, Test Migration or Migration runs that found files, and SMART Migration has not purged them yet, the box of Discovered, Test migrated or Migrated says so in red on a line of its own — 1 deleted run not yet purged — and its card says the same: the figure is not up to date, as it still counts their files, and changes once SMART Migration has purged them and reported the BI data again. A deleted run that found no files changes no figure and is not counted. Issues gets the same line for the deleted runs that hold file issues.
Archived runs count. An archived run stays in the BI data, so its files are in the three figures.
Nothing else is counted. The figures are only what SMART Migration reports — never added up from Run History — so they are 0 until its first report, and the card then says Not reported yet.

Migration progress

Migration progress, at the top beside the figures, shows what the Migration and Test Migration jobs that are Ready or Running have to move, and how far the running ones have come. A disabled job is left out: no claim takes it.

What is ready for processing is the files, versions and volume each job's last Discovery run counted — the latest run in that mode that finished with the result Ok or Warning. Run a job in Discovery first, then switch its mode to Migration, and its figures carry over.
Three bars — Files, Versions and Volume — fill with what the running jobs have reported so far, measured against those figures. SMART Migration reports the figures as the run works, so the bars move while it runs. Volumes read with two decimals — 1.56 MB, 2.35 GB — and one under a megabyte in KB (924 KB), or as < 1 KB.
Measure from, beside its box, picks what the bars cover. All jobs, the default, counts every Migration and Test Migration job that has ever run a migration, with what its runs moved, together with the Ready and Running ones — the whole migration so far. Ready and Running jobs only is the work still in hand. Selected running job measures one job alone: click its row in Running jobs, or choose Measure progress of this job in its ⋯ menu, and the bars follow the row you click; the job's run message under them names it. Or pick a finished run's start — every finished Migration and Test Migration run is listed, the latest first, 200 at a time as you scroll — and every job that has run since then counts. The choice is remembered in your browser.
A job without a Discovery run is counted at an estimate: with what its last finished Migration moved, or else as the average job — the average of what the Discovery runs counted and what those finished migrations moved. Each bar says how much of its total is estimated (incl. ≈ 61,103 estimated), fills what has been moved and draws the rest up to 100 % in dots, as it is only as good as the estimate; a mark at the end of the Migration progress heading counts these jobs; rest the pointer on it for a card that explains the rule, with the average and the jobs behind it. As such jobs finish, their own figures replace the estimate and join the average. Only while no job has figures to average are they left out of the totals, and the mark turns amber; its card then names the jobs left out. The bars still show: each gives what has been moved so far, with no total after it, over a full, dotted bar, and a line under them says there is no progress information to measure against. Such a job cannot be measured precisely: Progress for jobs without a Discovery run explains how far the estimate can be off, and how to get exact figures.
The forecast, in the box under the bars, below a count of the jobs measured by Discovery, sized by a finished migration and counted at the average: Time left at the average pace, Finished about at the running jobs' current rate, and Throughput in MB per hour, on average per job and now. Rest the pointer on it for a card that explains how each is worked out and why a migration can take longer than you expect. What a migration involves, and what sets its speed explains it in full.
When nothing is left to follow — no job in the selection is Running and every bar is full — the bars stand alone with a line saying no job is running: no forecast box, no estimate mark.

Why the bars can go back

With Ready and Running jobs only, a job that finishes leaves both what is ready and what is done, so the bars measure the work still in hand. The other choices under Measure from keep the finished jobs in: then the bars only grow. A job's runs since the start picked are added up — an incremental run moves only what changed — but a job never counts for more than its own figures: a file moved twice is one file migrated, so a job whose runs have moved everything its Discovery counted is complete, at 100 %. Migrated among the figures counts each file once, from the BI data, so it need not match what the bars say was moved.

Running jobs and their progress

Running jobs lists every job SMART Migration is working on, with its mode, status, group, result so far, duration, files, versions, volume and latest message. Before a run has a result, the Result column shows the runs mark in green while its session log holds no error or warning, yellow once it logs a warning, and red once it logs an error; rest the pointer on it for the counts. Click the mark, or the result once there is one, to open the run's details.

Select a running job to read its run message in a box under Migration progress, headed by the job's mode and title: what SMART Migration reports the job is doing right now, and any error or warning it has logged, in red or yellow. Each is one line, cut short where it is long; rest the pointer on it for the whole message. The run message is for information only — it gives no time left or percentage; the bars and the forecast under Migration progress do. Rest the pointer on Run message for a card that explains it. While no running job is selected — or SMART Migration Server is not running — the box is hidden.
Double-click a running job to go to the Run History tab with its latest run open and the list filtered to the job's runs.
Copy the progress and messages puts that text on the clipboard, for a ticket or a message to a colleague.
The row menu opens the run's Details here on the Dashboard, opens the job on the Jobs tab or its run on the Run History tab, or cancels the job.

The Power BI report

Power BI, beside Migration progress at the top, lists every Power BI file (.pbix) in the SmartBI folder of the SMART Migration Reports team folder for download — SMART BI.pbix as someone refreshed it in Power BI Desktop and uploaded it to Nextcloud, and any other a user uploaded there — each with its size and when it was uploaded, with a link to the folder in Files and a link to Power BI Desktop, which is free. Its Architecture link shows the Business Intelligence section, which explains the report, and scrolls down to it.

The Business Intelligence section is hidden until you ask for it: the Architecture link, the start tip's Business Intelligence link and Show the BI architecture on the Settings tab show it. Once shown, it stays until you click the red Close the BI architecture button in its yellow banner; a confirmation asks first. Showing and closing it is your own: the other administrators decide for themselves.

The Business Intelligence section opens with what SMART BI.pbix is — the Power BI report on what SMART Migration records for every run: every file found or moved, once, with its status — and that Power BI Desktop, which opens it, is free: no licence fee for anyone who opens or refreshes it. Under it are the same picture of the reporting database and the report file as on the Getting Started tab — where database access is needed and where it stops — The data foundation is your Run History — what the report holds, and how to keep it tight and relevant by deleting the runs that should not be in it — how the file is made, the business value of the reports, a card for each question people ask about the file, and why Power BI is used for the templates while any BI tool can read the PostgreSQL reporting database. See Refresh, upload and share SMART BI.pbix

After the blue ? on the Power BI heading, a small mark shows the state of the Business Intelligence data; rest the pointer on it for the explanation. A green Up to date means the report can be refreshed now. When Run History rows have been deleted, a red mark says how many deleted runs are not yet purged: SMART Migration has not yet removed them from the reporting database. When a run's title, description, tags or group has been changed, an amber mark says how many changed runs are not yet updated: SMART Migration has not yet written the change into the reporting database. When both wait, both marks show, side by side. Refresh the report once it is green again, or it still shows the data as it was.

Before a server has connected

On a fresh install, before a SMART Migration server has connected, the Dashboard shows its figures at zero, and Offline at the top right says no server has been in touch yet. The Getting Started tab lists the steps to get one running, starting with a partner on the Support tab, who provides the server installer and the trial licence key. See Set up SMART Migration for the app

Theme and language: the two buttons in the tab bar

At the far right of the tab bar, above the Dashboard's green band, two blue buttons set how the app looks to you. Both are your own choice, and both apply to this app alone: Nextcloud and its other apps keep your own theme and language.

The theme button names the theme the app is shown in now, Light theme or Dark theme, and opens a menu of four: Follow my Nextcloud theme, Follow the browser setting (the light or dark mode of your computer, followed as it changes), Light and Dark. The two that follow something say under their name whether it is light or dark at the moment. A pick applies at once, and the colours chosen under Language, theme and colours on the Settings tab apply in every theme.
The language button names the language the app is shown in — English, Deutsch, Français or Nederlands — and lists each with its flag. Pick another, or Follow my Nextcloud language, and the page reloads in it.

Both are the same choices as on the Settings tab. See Settings

One Dashboard for the whole team

Every administrator sees the same figures, the same running jobs and the same Power BI files: they are counted from the shared jobs and runs. What you choose on the Dashboard is your own.

Yours alone: the app's theme and language, the Latest, mode and result switches, the migration progress scope, your pins and the filters of the tables.
Shared with everyone: a notification dismissed from the Dashboard leaves every administrator's Dashboard, and Delete dismissed notifications acts for all of them.

See Working together: what is shared and what is yours

See also