this is for holding javascript data
Julien Emile-Geay edited Discussion.tex
almost 9 years ago
Commit id: b3357d24a25f68fb421dc5086150caf0f19e8f8d
deletions | additions
diff --git a/Discussion.tex b/Discussion.tex
index ffcb4e1..cdab87c 100644
--- a/Discussion.tex
+++ b/Discussion.tex
...
\item[Individual records] \\
A number of the form $I_1.I_2$, where $I_1$ is an integer associated with a publication (e.g.\cite{Thornalley_2009}) and $I_2$ is a counter updated every time a modification is made to the data or metadata.
\item[Data compilations ]
A number of the form $C_1.C_2.C_3$, where $C_1$ is an integer associated with a publication
(e.g.\cite{PAGES2k_2013}) \citep[e.g.][]{PAGES2k_2013} and $C_2$ is a counter updated every time a record is added or removed, and $C_3$ is a counter updated every time a modification is made to the data or metadata in an individual record.
\end{description}
We are presently implementing a large-scale test of the LiPD framework by using it as the primary data archive for Phase 2 of the \href{http://www.pages-igbp.org/workinggroups/2k-network/intro}{PAGES 2k global temperature database}. Consequently, the described framework for describing the proxy data is fairly mature and field-tested. LiPD's relatively complex structure is in fact the simplest container we could devise that would accommodate the wide diversity of constraints provided by the >5,000 records in the database. However, it may not be universal, and we welcome suggestions for increased generality.
...