My changes : /atelier/db/{db}/changes and /changes/scan
The question this screen answers
"What has moved in this database since the last copy of production?" After three weeks of experiments, nobody remembers. This page reads it back for you.
What has moved since the last copy: every change, dated and attributed.
The page sets the frame
At the top, the reference date: either the last pull-down of production, or the creation of the database. Everything counted is counted from that date, and the screen says so explicitly so that no figure floats free.
The scan does the work, /changes/scan
The summary is not computed in advance: it loads after the page appears, which is why you see "Reading the database…". The portal walks through every model in the database to spot what has changed; allow a few seconds. That reading is strictly read-only: it changes nothing, it counts.
How the sorting is done
The portal does not arbitrarily decide what is configuration and what is operating data. It works it out from your database:
- a set whose records nearly all come from an installed module is configuration;
- a set that grows with day-to-day activity is operating data.
The sorting is a suggestion, not a verdict. The figures behind it are shown alongside, precisely so that you can contradict it when you know your trade better than the tool does.
This is also the page Camille opens before every go-live: she checks that nothing unexpected has been touched. One tab is enough, and the link sits right inside the go-live screen.
In closing
After three weeks of experimenting, nobody remembers what they changed. This screen reads it back for you, from a date stated in full, so that no figure floats when the time comes to decide.
Commenting is not enabled on this course.