From eb206048f8b042159dc02d2c926e5702e8078ce9 Mon Sep 17 00:00:00 2001
From: John Swinbank <swinbank@astron.nl>
Date: Sat, 7 Jan 2023 19:36:12 +0100
Subject: [PATCH] Add material on accessing ESAP
---
contents/1-intro.tex | 6 ++----
contents/2-vision.tex | 2 +-
contents/7-access.tex | 16 ++++++++++++++++
.../{7-conclusions.tex => 8-conclusions.tex} | 0
4 files changed, 19 insertions(+), 5 deletions(-)
create mode 100644 contents/7-access.tex
rename contents/{7-conclusions.tex => 8-conclusions.tex} (100%)
diff --git a/contents/1-intro.tex b/contents/1-intro.tex
index 26cbc7d..f8d1bf7 100644
--- a/contents/1-intro.tex
+++ b/contents/1-intro.tex
@@ -22,9 +22,7 @@ Specifically, we will consider:
\item{To what extent the prototype meets the requirements which were specified in \citetitle{ESCAPE-D5.2} \autocite{ESCAPE-D5.2}?}
-\item{To what extent the prototype meets the needs currently being expressed by the \gls{ESCAPE}-affiliated \glspl{ESFRI}, as expressed through the use cases collated by the project?}
-
-\item{To what extent have \gls{ESFRI} or other services have been successfully integrated with \pgls{ESAP}?}
+\item{To what extent have \gls{ESFRI} needs been met by the \pgls{ESAP} development effort?}
\item{What are the future plans for \pgls{ESAP} development as the \gls{ESCAPE} project comes to its conclusion?}
@@ -38,4 +36,4 @@ In \cref{sec:vision} we the overall vision for the \pgls{ESAP} system: what did
The second part of this document moves on to asses how successful that vision and implementation have been in addressing user --- and in particular \gls{ESFRI} --- needs.
In particular, \cref{sec:requirements} tabulates the documented requirements and compares them to delivered product, while \cref{sec:esfri} describes how some of the major \gls{ESCAPE} project \gls{ESFRI}s are engaging with and building upon the work carried out by \gls{WP}5.
-Finally, we consider potential future enhancements in \cref{sec:future}, and provide a summary of the results of this analysis is presented in \cref{sec:conclusions}.
+Finally, we consider potential future enhancements in \cref{sec:future}, discuss the availability of \gls{ESAP} and its integration with \gls{EOSC} in \cref{sec:access}, and provide a summary of the results of this analysis is presented in \cref{sec:conclusions}.
diff --git a/contents/2-vision.tex b/contents/2-vision.tex
index c7bdedd..8c92bb2 100644
--- a/contents/2-vision.tex
+++ b/contents/2-vision.tex
@@ -35,7 +35,7 @@ Using the \pgls{ESAP} toolkit, \gls{ESCAPE} project partners can make assist use
\begin{center}
\includegraphics[width=0.66\textwidth]{figures/ESCAPE/esap-interfaces.pdf}
\end{center}
-\caption{The relationship between major \glsentrytext{ESAP} components, described in the text, and a selection of the services provided by various other \gls{ESCAPE} work packages.}
+\caption[The relationship between major ESAP components]{The relationship between major \glsentrytext{ESAP} components, described in the text, and a selection of the services provided by various other \gls{ESCAPE} work packages.}
\label{fig:vision:interfaces}
\end{figure}
diff --git a/contents/7-access.tex b/contents/7-access.tex
new file mode 100644
index 0000000..ce90a76
--- /dev/null
+++ b/contents/7-access.tex
@@ -0,0 +1,16 @@
+\section{Accessing \glsentrytext{ESAP}}
+\label{sec:access}
+
+\subsection{\glsentrytext{ESAP} as a Service}
+
+As described in \cref{sec:vision}, the \gls{ESCAPE} project itself does not directly provide an instance of \gls{ESAP} that is targeted at end users.
+Rather, \gls{ESAP} is distributed a toolkit that is provided for the use of \glspl{ESFRI} and other data and service providers who wish to provide a science platform to their user community.
+We anticipate that these individual \gls{ESAP} instances will be managed and deployed as part of the \gls{EOSC}.
+
+\subsection{The \glsentrytext{ESAP} codebase}
+
+The \gls{ESAP} codebase is a core part of the \gls{ESCAPE} project output.
+As such, before the conclusion of the project, it will be registered with the \gls{ESCAPE} \gls{OSSR} and thereby preserved for posterity within the context of the \gls{EOSC}.
+
+The development code repositories for \gls{ESAP}, together with documentation and other resources, will continue to be hosted at ASTRON, the Netherlands Institute for Radio Astronomy, for the foreseeable future.
+The primary point of entry for this material is \url{https://git.astron.nl/astron-sdc/escape-wp5/esap-api-gateway/-/wikis/home}.
diff --git a/contents/7-conclusions.tex b/contents/8-conclusions.tex
similarity index 100%
rename from contents/7-conclusions.tex
rename to contents/8-conclusions.tex
--
GitLab