Skip to content

Instantly share code, notes, and snippets.

@D-K-E
Last active February 23, 2017 17:10
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save D-K-E/4986b8c10d45b6a298ef659de1bd81fb to your computer and use it in GitHub Desktop.
Save D-K-E/4986b8c10d45b6a298ef659de1bd81fb to your computer and use it in GitHub Desktop.
Talk presented in Caf'Ephe, February Paris on Zotero ANEEM group.
\documentclass{beamer}
\mode<presentation>
\setbeameroption{hide notes}
\usepackage{fontspec}
\usepackage{listingsutf8} %Xml'i latexe aktarmak için
\lstset{language=Python}
\usetheme{Warsaw}
%\usecolortheme{beaver}
%\usecolortheme{whale}
%\usecolortheme{lily}
% --------------------------
% Theme by Gonzalo Medina taken from SO:
% http://tex.stackexchange.com/questions/57477/beamer-dark-theme
% --------------------------------------------------
\setbeamercolor{normal text}{fg=white,bg=black!90}
\setbeamercolor{structure}{fg=white}
\setbeamercolor{alerted text}{fg=red!85!black}
\setbeamercolor{item projected}{use=item,fg=black,bg=item.fg!35}
\setbeamercolor*{palette primary}{use=structure,fg=structure.fg}
\setbeamercolor*{palette secondary}{use=structure,fg=structure.fg!95!black}
\setbeamercolor*{palette tertiary}{use=structure,fg=structure.fg!90!black}
\setbeamercolor*{palette quaternary}{use=structure,fg=structure.fg!95!black,bg=black!80}
\setbeamercolor*{framesubtitle}{fg=white}
\setbeamercolor*{block title}{parent=structure,bg=black!60}
\setbeamercolor*{block body}{fg=black,bg=black!10}
\setbeamercolor*{block title alerted}{parent=alerted text,bg=black!15}
\setbeamercolor*{block title example}{parent=example text,bg=black!15}
% ------------------------
\setmainfont{FreeSerif}
\title{Ancient Near East and Eastern Mediterranean Multidisciplinary Group: A
Collaborative Bibliography}
\date{February 2017 - Caf'Ephe}
\author{
Doğu Kaan Eraslan \newline {\url{dogu-kaan.eraslan@etu.ephe.fr}}
}
\institute[EPHE-PSL]{EA 4519 - Ecole Pratique des Hautes Etudes - Paris Science
\& Lettres}
\logo{
{\includegraphics[scale=0.25]{./logo-ephe.png}}
{\includegraphics[scale=0.20]{./logo-psl.png}}
}
\begin{document}
\frame{\maketitle}
\section{Zotero}
\begin{frame}
\frametitle{Definitions}
\begin{itemize}
{\item{Zotero: An open source reference manager, maintained by Roy
Rosenzweig Center for History and New Media}}
{\item{Reserved Tags: Tags that should be used only within their defined
scope}}
{\item{Note Types: Type of notes that a reference can have.}}
{\item{Relations: Links established between references that contain same
full text-edition. Ex. a new edition of a text that is previously
published, or a fragment of a work conserved within another work}}
{\item{Collections: Entities under which the references are grouped}}
\end{itemize}
\end{frame}
\section{Group/Collaborative Bibliographies}
\subsection{CB vs Library}
\begin{frame}
\frametitle{Collaborative Bibliographies vs Libraries ?}
\begin{itemize}
{\item{Related vs Available}}
{\note[item]{Collaborative Bibliographies provide a bibliography that related to
the subject.
Whereas the libraries provide what is readily available/consultable.}}
{\item{Fast evolving}}
{\note[item]{Collaborative Bibliographies are fast evolving entites, because
most of the time it is easy to interract with them, since they provide the
reference in easily interchangeable format.}}
{\item{Normative in their field}}
{\note{Since collaborative bibliographies gather the joint work of scientists
from all over the world, they tend to be normative in their field. They
serve as a point of reference for other projects.}}
\end{itemize}
\end{frame}
\subsection{CB vs Institutional Services}
\begin{frame}
\frametitle{Collaborative Bibliographies vs Institutional Services ?}
\begin{itemize}
{\item{Not mutually exclusive}}
{\note{They are not mutually exclusive entities. An institution can provide
a collaborative bibliography service}}
{\item{More control over the information}}
{\note[item]{A good feature of Collaborative Bibliographies is that they
promise more control over the information with less hassle from
bureaucracy, with simple tools, due again to the easily interchangeable
format of the reference data.}}
{\item{Less control over the information}}
{\note[item]{It is a little to easy to change and/or erase the information,
but the damage that can be caused from these practices can be minimised
by closed membership policies, and some authentication proceedures for
bulk additions}}
\end{itemize}
\end{frame}
\section{Guidelines for ANEEMM-G Bibliography}
\subsection{Collections}
\begin{frame}
\frametitle{Collections}
\begin{itemize}
{\item{Regional Division}}
{\note[item]{These divisions are mostly based on historiography of the
disciplines rather than actual territorial divisions. They should never
be understood as a character that qualifies the work within. I chose
this regional division of the collections, because they seemed as the
only stable markers that can contain a diachronic body of works in a
coherent manner.}}
{\item{Ambigous Regions}}
{\note[item]{If a work can be attributed to several regions, do not hesitate
the add the work to several collections. If you have no idea about where
to add, add it to the Terra-Incognita collection.}}
\end{itemize}
\end{frame}
\subsection{Reserved Tags}
\begin{frame}
\frametitle{Reserved Tags}
\begin{itemize}
{\item{editio-princeps}}
{\note[item]{First edition of a primary source, that is a publication that
includes a full text edition that has not published previously.}}
{\item{primary-source}}
{\note[item]{A publication that includes a full text edition that may or may not
previously published.}}
{\item{secondary-source}}
{\note[item]{A publication that refers to a text edition.}}
{\item{Non-Reserved-Tags}}
{\note[item]{Up to user, it can be in any language concerning anything.}}
\end{itemize}
\end{frame}
\subsection{Note Types}
\begin{frame}
\frametitle{Note Types}
\begin{itemize}
{\item{primary-source-list}}
{\note[item]{List of primary sources that are completly included in the document}}
{\item{secondary-source-list}}
{\note[item]{List of primary sources that are refered by the document.}}
{\item{comments}}
{\note[item]{A list contaning anonymous comments about the work in question.
The comments has to include a date, hour, minute in the following
format: 2017-02-22T22:53. In the long run this should provide an
alternative to citation numbers concerning the reception of a work.
Members are encouraged to exchange views about
a certain work(s). Think of this section as the maidan of the work. Any
language is accepted in comments.}}
\end{itemize}
\end{frame}
\begin{frame}
\frametitle{Relations}
\begin{itemize}
{\item{1-1: Diachronic}}
{\note[item]{1-1 diachronic relations of text editions should be represented
with relations section of zotero. Ex. a series of editions of a certain
inscriptions can be linked with each other with this feature.}}
{\item{1-n: Fragmentary}}
{\note[item]{1-n fragmentary relations concerning the text editions can be
used to represent. Ex. A tablet used in an edition of a literary text, or
an edition of a royal inscription that has been constituted by consulting
different fragments of the same found and published in different regions
and periods.}}
\end{itemize}
\end{frame}
\section{Contributing}
\subsection{Small Additions}
\begin{frame}
\frametitle{Small Contribution}
\begin{itemize}
{\item{Small Contribution = up to ~1000-2000}}
{\note[item]{Small Adition is around ~1000, at least that much wouldn't be
too much of a toll to the gui of Zotero}}
{\item{Usual drag and drop system provided by Zotero's Graphical User
Interface.}}
{\item{Automatic Synching is allowed.}}
\end{itemize}
\end{frame}
\subsection{Bulk Contribution}
\begin{frame}
\frametitle{Bulk Contribution}
\begin{itemize}
{\item{Bulk Contribution = 4000+}}
{\note[item]{A contribution that passes around 4000 can be a considerable toll
to the gui of Zotero, this can in turn create problems in your programme.
You should not use drag and drop method to add this much reference to the
group.}}
{\item{Zotero: Web API}}
{\note[item]{The recommended medium for doing bulk contributions, but requires very
basic level programming experience. Those who would prefer this method for
interracting with the database would need to have an api-key for adding
documents. Those keys can be obtained from me. The documentation detailing
the different scenarios for interractions is also pretty comprehensive, so
you should have no problem once you have the api-key.
I have also written some python scripts to facilitate the transformation of
the data to the Zotero server compliant format, which is a json with zotero
fields as dictionary keys. If you know javascript, you can use the official
converters of Zotero which are much more robust than what i have written.}}
{\item{Open Access Only}}
{\note{For bulk contributions, the provider should be able to justify that the
data comes from open access sources, and not from commercial bibliograpies}}
{\item{No automatic synching}}
{\note[item]{Since bulk contributions usually take more time to complete, there
is a higher risk that something might go wrong during the uploading of the
data. Disabling automatic synching ensures that data stays with the version
number of the broken upload and not a new version number which you would
attributed during the automatic synching after the broken upload.}}
{\item{Backup all the library}}
{\note[item]{It is up to the contributors to make a local copy of the library
before every major upload. Just in case...}}
\end{itemize}
\end{frame}
\begin{frame}
\frametitle{ANEEM-G}
\begin{itemize}
{\item{The url:
{
\url{
https://www.zotero.org/groups/ancient_near_east_and_eastern_mediterranean_multidisciplinary_group_a_collaborative_bibliography
}
}}}
{\item{Statistics: 50079 works of which: }}
\begin{itemize}
{\item{35432 concerns mesopotamia}}
{\item{13545 concerns egypt}}
{\item{575 concerns levant}}
{\item{195 concerns anatolia}}
{\item{330 concerns persia}}
\end{itemize}
\end{itemize}
\end{frame}
\end{document}
% Local Variables:
% TeX-engine: xetex
% End:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment