Handling of Ography DATA in TAPAS Reader

Vertical Tabs

Reader
<?xml version="1.0" encoding="UTF-8"?>
<?xml-model href="http://www.tei-c.org/release/xml/tei/custom/schema/relaxng/tei_all.rng" type="application/xml" schematypens="http://relaxng.org/ns/structure/1.0"?>
<?xml-model href="http://www.tei-c.org/release/xml/tei/custom/schema/relaxng/tei_all.rng" type="application/xml"
	schematypens="http://purl.oclc.org/dsdl/schematron"?>
<TEI xmlns="http://www.tei-c.org/ns/1.0">
   <teiHeader>
      <fileDesc>
         <titleStmt>
            <title>TAPAS Sample File: TAPAS Reading Interface Handling of Ography DATA</title>
         </titleStmt>
         <publicationStmt>
            <publisher>Northeastern University TAPAS project</publisher>
            <availability>
               <ab>
                  Freely available for download and redistribution for educational, non-commercial use.
               </ab>
            </availability>
         </publicationStmt>
         <sourceDesc>
            <p>Born Digital</p>
         </sourceDesc>
      </fileDesc>
      <profileDesc>
         <particDesc><!-- Personography and Orgography data may go here as well as linked externally as demonstrated in body; may contain personography and orgography -->
            <listPerson><!-- personography data -->
               <!-- repeat '<person></person>' container for each new entry -->
               <person xml:id="pers_jane_doe">
                  <persName>Jane Doe</persName>
                  <birth when="2017-01-01">
                     <placeName ref="#location_name">Birthplace</placeName>
                  </birth>
                  <death notBefore="2017"/>
                  <education><orgName>Name of Institution</orgName></education>
                  <langKnowledge>
                     <langKnown tag="en">first language</langKnown>
                  </langKnowledge>
                  <nationality><placeName>United States</placeName></nationality>
                  <occupation from="2017">Subject of a TAPAS Personography template</occupation>
                  <residence from="2017-01" to="2017-02">
                     <placeName ref="#place_residence_1">Place of Residence 1</placeName>
                  </residence>
                  <residence from="2017-02" to="2017-03">
                     <placeName ref="#place_residence_2">Place of Residence 2</placeName>
                  </residence>
                  <event when="2017-02" where="#place_residence_1">
                     <p>Something cool happened...</p>
                  </event>
                  <trait type="eye_color">
                     <label>eye color</label>
                     <desc>green</desc>
                  </trait>
                  <state type="marital_status">
                     <label>marital status</label>
                     <desc>partnered</desc>
                  </state>
               </person>
            </listPerson>
            <listOrg><!-- Orgography data -->
               <!-- reapeat '<org></org>' container for new entry -->
               <org xml:id="org_name">
                  <orgName>Northeastern University</orgName>
                  <desc>A North American private university located in Boston, Massachusetts.</desc>
                  <listOrg>
                     <org xml:id="org_dsg">
                        <orgName>Digital Scholarship Group</orgName>
                        <desc>A community of digital scholars, practitioners, and developers who educate and support the Northeastern Community in using digital resources and technologies for designing, implementing, and managing digital scholarly projects</desc>
                     </org>
                     <org xml:id="org_tapas">
                        <orgName>The TEI Archiving, Publishing, and Access Service</orgName>
                        <desc>A digital project platform and repository for the public to store, publish, and research TEI data. </desc>
                     </org>
                  </listOrg>
               </org>
            </listOrg>
         </particDesc>
      </profileDesc>
   </teiHeader>
   <text>
      <body>
         <div>
            <head>Introduction</head>
            <p>This document demonstrates how the TAPAS reading interface handles internal and external ography data.</p>
         </div>
         <div>
            <head>General Notes about Linking</head>
            <p>You can allow front-end user to dynamically call on -Ography data in two ways through the TAPAS Reader:</p>
            <p>(1) by generating a link to -Ography data stored in the tei header. To do accomplish this, we use, for example, <![CDATA[<persName>]]> with @ref to desired anchor ID in header. As this is an internal link, we only need to use a "#". For example, to grab data from  internally stored personography data on Jane Doe in this file's header, we wrap <![CDATA[<persName>]]> around the named reference "Jane Doe" with her unique ID: <![CDATA["pers_jane_doe"]]>.</p>
            <p><![CDATA[<persName ref="#pers_jane_doe">Jane Doe</persName>]]></p>
            <p>TRY IT: Click <persName ref="#pers_jane_doe">Jane Doe</persName> to learn more about her. </p>
            <p>(2) by linking to an external -Ography file. You may also upload your -Ography files into your TAPAS project as "Support" Records. <note>(*Note: all Support Records must be uploaded prior to Primary Records to ensure proper association. Step 1: Upload your -Ography files first; Step 2: then, upload your primary encoded file(s).</note> Here we use a similar setup, but as we are linking to data outside the primary file, we need to include the full path to the reference file:</p>
            <p><![CDATA[<persName ref="/tapas-commons/files/personography.xml#pers_jane_doe">Jane Doe</persName>]]></p>
            <p>We identify the project (/tapas-commons) within which both files live, and include full path to -Ography file (/files/tapas-personography) followed by the referenced entry (#pers_jane_doe):</p>
            <p>TRY IT: Click <persName ref="/tapas-commons/files/personography.xml#pers_jane_doe">Jane Doe</persName> to learn more about her. </p>
         </div>
         <div><head>Sample Ography files in TAPAS Commons</head>
            <list>
               <item><ref target="/tapas-commons/files/tapas-personography">TAPAS Template Personography</ref></item>
               <item><ref target="/tapas-commons/files/tapas-placeography">TAPAS Template Placeography</ref></item>
               <item><ref target="/tapas-commons/files/tapas-orgography">TAPAS Template Orgography</ref></item>
               <item><ref target="/tapas-commons/files/tapas-bibliography">TAPAS Template Bibliography</ref></item>
            </list>
         </div>
         
      </body>
   </text>
</TEI>
TAPAS Sample File: TAPAS Reading Interface Handling of Ography DATA Northeastern University TAPAS project Freely available for download and redistribution for educational, non-commercial use.

Born Digital

Introduction

This document demonstrates how the TAPAS reading interface handles internal and external ography data.

General Notes about Linking

You can allow front-end user to dynamically call on -Ography data in two ways through the TAPAS Reader:

(1) by generating a link to -Ography data stored in the tei header. To do accomplish this, we use, for example, <persName> with @ref to desired anchor ID in header. As this is an internal link, we only need to use a "#". For example, to grab data from internally stored personography data on Jane Doe in this file's header, we wrap <persName> around the named reference "Jane Doe" with her unique ID: "pers_jane_doe".

<persName ref="#pers_jane_doe">Jane Doe</persName>

TRY IT: Click Jane Doe to learn more about her.

(2) by linking to an external -Ography file. You may also upload your -Ography files into your TAPAS project as "Support" Records. 1 (*Note: all Support Records must be uploaded prior to Primary Records to ensure proper association. Step 1: Upload your -Ography files first; Step 2: then, upload your primary encoded file(s). Here we use a similar setup, but as we are linking to data outside the primary file, we need to include the full path to the reference file:

<persName ref="/tapas-commons/files/personography.xml#pers_jane_doe">Jane Doe</persName>

We identify the project (/tapas-commons) within which both files live, and include full path to -Ography file (/files/tapas-personography) followed by the referenced entry (#pers_jane_doe):

TRY IT: Click Jane Doe to learn more about her.

Jane Doe

2017-01-01

sometime after 2017

2017-02

Something cool happened...

first language

2017–presentSubject of a TAPAS Personography template

2017-01–2017-02 2017-02–2017-03

partnered

green

Jane Doe

2017-01-01

Jane Doe A photo of Jane Doe from spring 2016

sometime after 2017

2017-02

Something cool happened...

Jane Doe A photo of Jane Doe from spring 2016

first language

2017–presentSubject of a TAPAS Personography template

2017-01–2017-02 2017-02–2017-03

partnered

green

Toolbox

Themes:

TAPAS Sample File: TAPAS Reading Interface Handling of Ography DATA Northeastern University TAPAS project Freely available for download and redistribution for educational, non-commercial use.

Born Digital

Jane Doe Birthplace Name of Institution first language United States Subject of a TAPAS Personography template Place of Residence 1 Place of Residence 2

Something cool happened...

green partnered
Northeastern University A North American private university located in Boston, Massachusetts. Digital Scholarship Group A community of digital scholars, practitioners, and developers who educate and support the Northeastern Community in using digital resources and technologies for designing, implementing, and managing digital scholarly projects The TEI Archiving, Publishing, and Access Service A digital project platform and repository for the public to store, publish, and research TEI data.
Introduction

This document demonstrates how the TAPAS reading interface handles internal and external ography data.

General Notes about Linking

You can allow front-end user to dynamically call on -Ography data in two ways through the TAPAS Reader:

(1) by generating a link to -Ography data stored in the tei header. To do accomplish this, we use, for example, <persName> with @ref to desired anchor ID in header. As this is an internal link, we only need to use a "#". For example, to grab data from internally stored personography data on Jane Doe in this file's header, we wrap <persName> around the named reference "Jane Doe" with her unique ID: "pers_jane_doe".

<persName ref="#pers_jane_doe">Jane Doe</persName>

TRY IT: Click Jane Doe to learn more about her.

(2) by linking to an external -Ography file. You may also upload your -Ography files into your TAPAS project as "Support" Records. (*Note: all Support Records must be uploaded prior to Primary Records to ensure proper association. Step 1: Upload your -Ography files first; Step 2: then, upload your primary encoded file(s). Here we use a similar setup, but as we are linking to data outside the primary file, we need to include the full path to the reference file:

<persName ref="/tapas-commons/files/personography.xml#pers_jane_doe">Jane Doe</persName>

We identify the project (/tapas-commons) within which both files live, and include full path to -Ography file (/files/tapas-personography) followed by the referenced entry (#pers_jane_doe):

TRY IT: Click Jane Doe to learn more about her.