User Discussions > Other Discussion

Additional system levels?

(1/3) > >>

Jim:
One of my projects early this summer is to streamline the site update process.  It takes about 45 minutes to run a full site update now from launch to completion, but there's a lot of redundant work done and redundant data stored that was introduced when we added the three levels of highway systems: active, preview, and devel.

Before I get too far into this, I'd like to make sure we're happy with these three levels, and with the way systems in each level are treated.  Is there any further refinement of the levels that would be useful?

As a reminder, here's how the levels work now:

active: completed systems, no datacheck errors, any change that would affect users with entries in their list files will be reported in the updates log, by default these are the only systems shown in maps and stats

preview: completed systems still in final review, should have no datacheck errors before being promoted to this status, changes can be made that would affect users with entries in their list files with no updates log entry, shown in maps and stats only when specifically requested

devel: systems in development, either still incomplete, with datacheck errors, or with questions about whether the system belongs in the project at all, never included in maps and stats (other than the highway browser)

Currently, one chooses whether to include preview systems in maps and stats when viewing pages on the site by specifying a query string parameter to select a database.  My plan is to consolidate back into a single database, so new query string parameters will be used to determine whether preview systems are to be included.  This will require some hopefully straightforward changes to PHP code behind many of the web pages.

Any thoughts, requests, suggestions related to this?



 

oscar:
I thought that preview systems could still have Datacheck errors, since they're still being worked on and that work might add new errors (especially visible distance, for segments whose endpoints are tweaked in the editing process), to be resolved before activation.

usaak, a preview system I'm still working on (next round of updates coming soon), has a lot of Datacheck errors which I was not planning to cross off until just before activation. Some will disappear in the editing process, while others will be replaced with new ones.

Jim:

--- Quote from: oscar on May 29, 2016, 04:17:52 pm ---I thought that preview systems could still have Datacheck errors, since they're still being worked on and that work might add new errors (especially visible distance, for segments whose endpoints are tweaked in the editing process), to be resolved before activation.

usaak, a preview system I'm still working on (next round of updates coming soon), has a lot of Datacheck errors which I was not planning to cross off until just before activation. Some will disappear in the editing process, while others will be replaced with new ones.

--- End quote ---

This is a really good point.  Especially the visible distance errors, which might change as routes get finalized.  I think the "serious" errors like duplicate labels should be addressed before promotion to preview.

yakra:
Happy with the three levels and the way they are treated. I have no suggestions or requests for further refinement.

Jim:
Thinking more tonight about how to proceed on this, and wanted to throw some things out there for possible discussion.

For pages that list stats, continue to color code by active and preview entries in tables, but leave out devel entries entirely.  For stats summaries, include numbers for both active only and active+preview (when preview systems exist).

For maps, have a switch (checkbox? QS parameter?) that allows for preview systems to be included or not.  Systems in devel would never be included except in highway browser maps.

In user log files, messages would be like those currently in devlogs, with no messages for matching entries in active or preview systems.  The "inactive" message will be replaced with "in development" or similar.

Navigation

[0] Message Index

[#] Next page