%%This is a very basic article template.
%%There is just one section and two subsections.
\documentclass[a4paper,10pt,utf8]{article}
\usepackage{amsmath}
\usepackage[utf8]{inputenc}
\usepackage{euler}
\usepackage{epsf}
%\usepackage{german} 
\usepackage{hyperref}
\usepackage{makeidx}
\usepackage{graphicx}


\begin{document}
\title{Usage eScidoc Plattform at the MPIWG\\ (1. Phase)}
\author{Dirk Wintergrün - Version 0.3}
\date{\today}
\maketitle
\abstract{This document describes the intended use of eScidoc at the MPIWG. In
the first phase two fields of application will be developed: First, the use as
repository for the XML documents and the organisation of the workflows for
their production; second, eScidoc wil be used to generate a general metadata
repository and access point for all electronic documents of the MPIWG }


\tableofcontents


\section{Usage 1: XML-Repository}

\subsection{Goals}
The application shall manage the whole workflow of the production of XML
transcriptions starting from image files ending in an xml transcription of the
document.

\subsection{Szenarios}
The repository shall:
\begin{itemize}
  \item give an overview over the production administrative status of all
  documents.
 
  	\begin{itemize}
        \item new (with images / without images),
        \item transcribed / no xml,
        \item transcribed / xml.
      \end{itemize}
  At every state of the workflow, versioning and releasing of documents is
  possible, i.e. new images or texts can be added, submitted and released. 
  \item give access to the xml-texts via an URL
  \item make it possible to upload new versions of texts (either in XML or
  DE-specs version)
\end{itemize}

\subsection{Managing the production process}
The sequence of events shall be realised as shown in diagram
\ref{useCaseTextProduction}.%
%\usepackage{graphics} is needed for \includegraphics
\begin{figure}[h]
\begin{center}
\includegraphics[height=20cm]{usecaseXML.png}  
  \caption[use case - text production]{Use case: text production}
  \label{useCaseTextProduction}
\end{center}
\end{figure}


\subsection{eSciDoc (meta) data structure}\label{dcfields}
Starting point of the meta data entry is the meta data either as required for
index.meta file, if images are already existing at the foxridge (see
\url{XXX})or bibliographical metadata following the system as described in
\url{YYY}.



\subsubsection{DC part}
The required DC part of the metadata is derived automatically  from the
bibliographical metadata.

\subsubsection{PID}
To each document a (MPIWG) persistent identifier will be automatically attached
(see \ref{pids}).

\subsubsection{administrative Metadata}\label{adminMetadata}
Administrative Metadata is kept in the escidoc-xml record as ownd md-record:

\begin{verbatim}
<escidocMetadataRecords:md-records 
xlink:type="simple" xlink:title="Metadata Records of Item escidoc:37144" 
xlink:href="/ir/item/escidoc:37144/md-records">
	<escidocMetadataRecords:md-record name="mpiwg-admin"
    md-type="MPIWG"    schema="http://example.com/generic/" 
	xlink:type="simple" xlink:title="mpiwg-admin" 
	xlink:href="/ir/item/escidoc:37144/md-records/md-record/mpiwg-admin">
  
       <mpiwg:admin xmlns:mpiwg="http://www.mpiwg-berlin.mpg.de/ns/mpiwg">
             <mpiwg:workflow>new</mpiwg:workflow>
              <mpiwg:imageFolder>
				/permanent/archimedes/borel_demot_010_la_1670/010-01-pageimg
			  </mpiwg:imageFolder>
               <mpiwg:comment></mpiwg:comment>
       </mpiwg:admin>

</escidocMetadataRecords:md-record>

\end{verbatim}

\begin{itemize}
  \item workflow: status of the object within the workflow
             \begin{itemize}
               \item new
 				\begin{itemize}
              		\item book to be digitized
              		\item we have a digitized version
                 \end{itemize}
                 \item sent for transcription
				  \begin{itemize}
                   \item sometimes: sample sent for transcription
                   \item missing images
					\end{itemize}
\item transcription
	  \begin{itemize}
\item sent, with DESpecs version, sometimes with Special Instructions in plain text, rtf, doc or pdf
\item queries and replies (including corrections and additional special instructions, and sometimes corrections of the special instructions) in the same formats
\item checking the sample, re-worked samples
\item we receive the complete text
	        
      \end{itemize}
      \item xml
\begin{itemize}
      \item raw
      \item minimal post-processingwell-formed xml
      \item valid xml against a particular schema
      \item proofread and ready for publishing
\end{itemize}
\end{itemize}
  \item imageFolder: path to the images on foxridge
  \item comment: Administrative comment for this version
\end{itemize}

\subsection{Datastreams}
All versions of the fulltexts (xml/DE-specs) are managed and kept within
eScidoc.\\

The index.meta and the images are referenced within eScidoc and kept at
foxridge.

\subsubsection{Transcription}
All fulltext are oganised in one datastream  (XML and DE-specs).\\

To distinguish between XML and DE specs a additional machanism should be added,
so that is http://foo.com/esicdoc/es:63463634/components/es:245255252 is the
datastream url of the fulltext.
http://foo.com/esicdoc/es:63463634/components/es:245255252/xml gives you the
content if it is xml otherwise it returns an error, analog with DE.

\subsubsection{Additional Files}
It should be possible to add specific related files to the item, e.g. special
instruction for the transcription or handling of this file. Theses files should
be components of this files.

Files to be used for more then one file become an item.
\subsubsection{Relations}
The link to the used DE-spec and/or xml-Schema/relax-ng/DTD is realised by
relations whereby the DE-spec or xml-Schema/relax-ng/DTD are stored as seperate
items.
\subsection{Collections}
In the first version of the XML storage system their exists only one collection
``XML-texts.''\\

In the next version it should be possible to create collections and attach
documents to collections using a web front end.

\subsection{Web access}
\subsubsection{Administrative overview}

On one web site an overview is given over all documents in the workflow. It is
possible to sort the documents by the DC fields\ref{dcfields}and the
administrative meta data \ref{adminMetadata}. Entries can also be filtered by
the administrative meta data. From this site new versions of documents can be
added, and texts can be uploaded.


\subsection{Acces via editors eclipse/oxygen/jedit/emacs}
It should be possible to download and update xml-files using editors like
jedit, oxygen or exlipse.

\begin{verbatim}
!!!Which priority?!!!
\end{verbatim}

\subsection{User Management / Rights}
Users have to be added to the system manually. Username and Password are the
same as in the institutes LDAP.

Only authorised users upload and
change data.\\

Withdrawl of data is only possible for administrators.\\

Data which is released can be accessed by everyone, without password. 

\section{Usage 2: access point for XML resources}
TO BE DONE
\subsection{PIDs}\label{pids}


\section{Additional namespaces}
\subsection{MPIWG Namespace: http://www.mpiwg-berlin.mpg.de/ns/mpiwg}
All administrative metadata covered by the mpiwg namespace.
\subsection{Project specific namespaces}
Metadata which is specific for a project shall be in a project specific
namespace.
\paragraph{VLP: http://www.mpiwg-berlin.mpg.de/ns/vlp}

\section{Status}
Currently:
\begin{itemize}
  \item runs only local
  \item Add texts to the management if index.meta exist at foxrudge
  \item  upload von Texts via Webfront
  \item submission and release via Webfront
\end{itemize}

Next steps:
\begin{itemize}
  \item deploy test version on euler
  \item User management, login of LDAP Users
  \item Assigning of steps in the workflow + comments
  \item Filter and sort list (title, author, workflow status)
  \item Evaluate plug-ins for oxygen, eclipse
\end{itemize}
\end{document}
	