This commit is contained in:
Boris Glavic 2016-04-24 19:39:46 -05:00
parent b86fd557c3
commit 32ab6b610d

View file

@ -48,26 +48,26 @@ While the spreadsheet UI has many advantages, it also has several drawbacks.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\tinysection{Notebook-style UIs} \tinysection{Notebook-style UIs}
%
Systems like iPython expose an interactive, interpreted programming environment through a notebook like interface where the user can mix documentation (text) with code. The output for code blocks is shown directly in the notebook - a feature that is widely used to produce data visualizations. Systems like iPython expose an interactive, interpreted programming environment through a notebook like interface where the user can mix documentation (text) with code. The output for code blocks is shown directly in the notebook - a feature that is widely used to produce data visualizations.
% A notebook UI such as in Jupyther and the visualization provided by workflow systems are much better suited in this regard. However, their disadvantage is that they are not suited well for small modifications to data, exploratory changes, and generalization of operations.
A notebook UI such as in Jupyther and the visualization provided by workflow systems are much better suited in this regard. However, their disadvantage is that they are not suited well for small modifications to data, exploratory changes, and generalization of operations.
\begin{itemize} \begin{itemize}
\item \textbf{Inline documentation of operations.} \item \textbf{Inline documentation of operations.} The notebook enables the user to write documentation and inline it together with the code.
\item \textbf{Supports incremental development of complex curation workflows.} \item \textbf{Incremental development of complex curation workflows.} Notebooks support an analyst to incrementally build a curation workflow by adding and revising operations one at a time. The structure of the workflow is made explicit through the notebook interface as long as the workflow is linear.
\end{itemize} \end{itemize}
However, some operations that are supported well in spreadsheets are harder to express in notebooks. However, some operations that are supported well in spreadsheets are harder to express in notebooks. Furthermore, some disadvantages are shared among both paradigms.
\begin{itemize} \begin{itemize}
\item \textbf{Small modification to data are cumbersome.} Compared to spreadsheets, modifying a few data values of a table requires the user to write code. \item \textbf{Small modification to data are cumbersome.} Compared to spreadsheets, modifying a few data values of a table requires the user to write code.
\item \textbf{No support for mapping curation operation developed for an example over a data collection.} \item \textbf{No support for mapping curation operation developed for an example over a data collection.}
\item \textbf{Non-linear workflows and development with backtracking is not supported well.}
\end{itemize} \end{itemize}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\tinysection{Visualizations} \tinysection{Visualizations}
%
Both spreadsheets and notebook UIs make it very easy for users to create visualizations from data on the fly and show these visualization inline with the data. Also both paradigms allow these visualization to be tweaked and to be refreshed based on change to their inputs. Spreadsheets in particular provide a very easy to use interface for selecting what data should be visualized. Both spreadsheets and notebook UIs make it very easy for users to create visualizations from data on the fly and show these visualization inline with the data. Also both paradigms allow these visualization to be tweaked and to be refreshed based on change to their inputs. Spreadsheets in particular provide a very easy to use interface for selecting what data should be visualized.
% \begin{itemize} % \begin{itemize}