G2 michale satlow_inscriptionsisraelpalestine
- 2. Goals How the Site Works Encoding Standards Technical Details Workflow Linked Data The Future OUTLINE
- 3. Collection, not an edition Public accessibility Enable scholarly analysis/visualization GOALS
- 9. Extensible Markup Language (XML) EpiDoc Standard Metadata About the physical object: material; type; location; find About the text: Language; date; religion Controlled vocabularies Text Diplomatic transcription Edited transcription English translation XML Tagging in Hebrew ENCODING STANDARDS
- 11. <sourceDesc> <msDesc><msIdentifier><idno>sepp0002</idno></msIdentifier><!-- **** <msContents> **** --> <msContents><textLang mainLang="arc"/><msItem class="#dedicatory" ana="#jewish"><p>Galilee. Sepphoris. 400-500 CE. Synagogue. Black and white floor mosaic. Dedication.</p></msItem></msContents><!-- **** <physDesc> **** --> <physDesc><!-- **** <objectDesc> **** --> <objectDesc ana="#floor"><supportDesc><support><dimensions type="surface"><height unit="cm" quantity="38"/><width unit="cm" quantity="38"/></dimensions><p/></support><condition><p/></cond ition> </supportDesc> ENCODING SAMPLE: METADATA
- 12. <body> <div type="edition" ana="#b1" xml:lang="heb" subtype="transcription" xml:id="sepp0004.transcription" corresp="#sepp0004.translation"> <p><supplied reason="undefined"> ?????</ supplied> ????? ???< lb/> <gap reason="illegible"/> ????? ????< lb/> <supplied reason="undefined"> ????</ supplied> ???????< lb/> ???????< lb/> ????? ????? </ p> </div> SAMPLE OF HEBREW TAGGING
- 13. Sharing data EAGLE USING THE EPIDOC STANDARD
- 14. Standards based and automatable Version control: Subversion (moving to Github) Servers hit Subversion once an hour automatically Solr indexed: Preprocesssig (removing Greek accents; interword tags, etc. for indexing/searching) Django interface Data preservation: Brown Digital Repository TECHNICAL DETAILS
- 15. Goal: Make encoding as simple and intuitive as possible Encoders: Template in Oxygen XML Files created in shared Dropbox folder Bibliography in Zotero WORKFLOW: FIRST STAGE
- 20. When completed, files are reviewed, preferably by another encoder After the review, they are uploaded to the development server Subversion Processing to enable searching WORKFLOW: SECOND STAGE
- 21. API (Application Programming Interface) Geographical Objects Visual LINKED DATA
- 22. Pleiades (http://pleiades.stoa.org) <origin> <placeName ref=https://Pleiades.stoa.org/places/687968> <location unit=¡°lat-lon¡±><geo>31.31904988, 35.35230084</geo></location> <region>Judaea</region> <settlement>Masada</settlement> <geogFeat type=¡°locus¡±>113</geogFeat> </placeNeme> </origin> GEOGRAPHICAL LINKING
- 23. What is it? Getty Taxonomy (https://www.getty.edu/research/tools/vocabularies/) E.g., all altar inscriptions in Greek from the third century CE <category xml:id=¡°#altar¡±> <catDesc><ref target=http://vocab.getty.edu/aat/300003725>Altar</ref></catDesc> </category> OBJECTS <catDesc><ref target="http://xxxx">Flagstone</ref></catDesc> </category> <category xml:id="architectural.flagstone"> <catDesc><ref target="http://xxxx">Flagstone</ref></catDesc> </category> <category xml:id="architectural.flagstone"> <catDesc><ref target="http://xxxx">Flagstone</ref></catDesc> </category>
- 24. Drawing on images displayed on other sites E.g., Brooklyn Museum API (http://www.programmableweb.com/api/brooklyn-museum) Annotate, process, analyze VISUAL
- 25. Redesign the site using more geography and images Add richer content encoding (e.g., morphological; names) Analytical tools A site for the integration and analysis of material culture? LARGER VISION
- 26. NEW INTERFACE