Difference between revisions of "Automatic Updates"

From dataZoa Wiki
Jump to: navigation, search
 
(22 intermediate revisions by the same user not shown)
Line 1: Line 1:
Time series are all about change. dataZoa is built to recognize changes and propagate them wherever appropriate.
+
<div class="imgGlyph24 imgConcept"></div> Simple and profound: <b>Everything {{EverythingUpdates}} updates</b> - [[#From_the_Web|data]], [[#Calculations|calculations]], [[#Displays|charts]], [[#Displays|tables]] - <b>automatically</b>.
 
+
<br>
 
==Data==
 
==Data==
 
<div>
 
<div>
Line 6: Line 6:
  
 
===From the Web===
 
===From the Web===
 +
{{Data_from_the_Web_Bullets}}
 +
 +
===Uploaded===
 
<div>
 
<div>
 
<ul>
 
<ul>
<li>When you drag-and-drop data series into dataZoa from other sites around the Web, we monitor for changes and make updates accordingly.</li>
+
<li>Despite all appearances, we do not have magic powers.  When you have uploaded your own data you will need to keep it up to date by updating it or re-loading.</li>
<li>For sites with important and closely watched data release schedules, we sync up as quickly as we can while trying not to be overly demanding.</li>
+
<li><div class="imgGlyph24 imgIdea"></div> If you are officially responsible for some particular data, encourage your colleagues to follow it in dataZoa rather than making copies.  No copies means no confusion.</li>
<li>There are many nuances and details in the updating process, but generally speaking we check for changes everywhere at least once a day.</li>
+
<li><div class="imgGlyph24 imgWarning"></div> Don't forget to preserve your [[About_Series#Series Key|series keys]] if you re-load your data.  That's how your displays and calculations stay up to date.</li>
 
</ul>
 
</ul>
 
</div>
 
</div>
  
===Uploaded===
+
===Updated===
 
<div>
 
<div>
 
<ul>
 
<ul>
<li>Despite all appearances, we do not have magic powers.  When you have uploaded your own data you will need to keep it up to date by updating it or re-loading.</li>
+
<li>When you update existing series in your account manually, the changes are fully propagated.</li>
<li><div class="imgGlyph24 imgIdea"></div> If you are officially responsible for some particular data, encourage your colleagues to follow it in dataZoa rather than making copies!</li>
+
<li>Series keys are naturally preserved.</li>
<li><div class="imgGlyph24 imgWarning"></div> Don't forget to preserve your [[Series_Keys|series keys]] if you re-load your data.  That's how your displays and calculations stay up to date.</li>
+
 
</ul>
 
</ul>
 
</div>
 
</div>
Line 26: Line 28:
 
<div>
 
<div>
 
<ul>
 
<ul>
<li>Changes to data in your account which is not owned by you but is rather shared with you (or followed by you) are fully propagated.</li>
+
<li>Changes to series in your account that are [[About_Series_Sharing|shared with you]], rather than owned by you, are fully propagated.</li>
 
</ul>
 
</ul>
 
</div>
 
</div>
Line 36: Line 38:
 
<li>Whenever you view a dataZoa display, you are seeing the current state of the data, <i>not</i> a copy of how things were at the time it was created.</li>
 
<li>Whenever you view a dataZoa display, you are seeing the current state of the data, <i>not</i> a copy of how things were at the time it was created.</li>
 
<li>That said, dataZoa does <i>not</i> refresh displays that are currently on screen; the on-screen display stays put until you refresh it.</li>
 
<li>That said, dataZoa does <i>not</i> refresh displays that are currently on screen; the on-screen display stays put until you refresh it.</li>
<li><div class="imgGlyph24 imgConcept"></div> dataZoa displays are not static snapshots.  If you embed a dataZoa display into a presentation, the presentation will show the <b>up-to-the-moment</b> state of things.</li>
+
<li><div class="imgGlyph24 imgIdea"></div> Make that presentation just once.  As data changes, last month's presentation then automatically becomes this month's.</li>
<li><div class="imgGlyph24 imgIdea"></div> Make that presentation just once.  Last month's presentation then automatically becomes this month's.</li>
+
<li><div class="imgGlyph24 imgIdea"></div> To archive a display at a particular point in time, hit the PDF button and store a snapshot.</li>
<li><div class="imgGlyph24 imgIdea"></div> If you need to archive a display at some particular point in time, hit the PDF button and store a snapshot.</li>
+
 
</ul>
 
</ul>
 
</div>
 
</div>
Line 44: Line 45:
 
==Calculations==
 
==Calculations==
 
<div>
 
<div>
 +
<ul>
 +
<li><div class="imgGlyph24 imgConcept"></div> dataZoa [[Calculations|calculations]] update automatically.  Change a number anywhere and everything that depends on it changes downstream.</li>
 +
<li>Dependencies can get complicated and that's AOK.  dataZoa keeps track of the multiple parent/child relations for you (yes, even non-traditional situations).</li>
 +
<li>Whenever you view a calculated series, by itself or in a dataZoa display, you are seeing the current state of the data, <i>not</i> a copy of how things were at the time it was created.</li>
 +
<li>When you change a calculation that feeds other calculations, that change flows right through as well.</li>
 +
</ul>
 
</div>
 
</div>
 +
 +
[[Category:Definitions]]

Latest revision as of 12:47, 27 April 2017

Simple and profound: Everything
updates
- data, calculations, charts, tables - automatically.


Data

From the Web

  • When you drag-and-drop data series into dataZoa from other sites around the Web, we monitor for changes and make updates accordingly.
  • For sites with important and closely watched data release schedules, we sync up as quickly as the sites allow.
  • There are many nuances and details in the updating process, but generally speaking we check for changes everywhere at least once a day.

Uploaded

  • Despite all appearances, we do not have magic powers. When you have uploaded your own data you will need to keep it up to date by updating it or re-loading.
  • If you are officially responsible for some particular data, encourage your colleagues to follow it in dataZoa rather than making copies. No copies means no confusion.
  • Don't forget to preserve your series keys if you re-load your data. That's how your displays and calculations stay up to date.

Updated

  • When you update existing series in your account manually, the changes are fully propagated.
  • Series keys are naturally preserved.

Shared from other dataZoa accounts

  • Changes to series in your account that are shared with you, rather than owned by you, are fully propagated.

Displays

  • dataZoa displays are not static snapshots. If you embed a dataZoa display into a presentation, the presentation will show the up-to-the-moment state of things.
  • Whenever you view a dataZoa display, you are seeing the current state of the data, not a copy of how things were at the time it was created.
  • That said, dataZoa does not refresh displays that are currently on screen; the on-screen display stays put until you refresh it.
  • Make that presentation just once. As data changes, last month's presentation then automatically becomes this month's.
  • To archive a display at a particular point in time, hit the PDF button and store a snapshot.

Calculations

  • dataZoa calculations update automatically. Change a number anywhere and everything that depends on it changes downstream.
  • Dependencies can get complicated and that's AOK. dataZoa keeps track of the multiple parent/child relations for you (yes, even non-traditional situations).
  • Whenever you view a calculated series, by itself or in a dataZoa display, you are seeing the current state of the data, not a copy of how things were at the time it was created.
  • When you change a calculation that feeds other calculations, that change flows right through as well.