Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Wedged publication 42321 (P.Amh. 2, 186) due to unknown APIS class #112

Open
ryanfb opened this issue Oct 8, 2018 · 1 comment
Open

Wedged publication 42321 (P.Amh. 2, 186) due to unknown APIS class #112

ryanfb opened this issue Oct 8, 2018 · 1 comment

Comments

@ryanfb
Copy link
Member

ryanfb commented Oct 8, 2018

Looking into these now. 42321 belongs to Philip J. Katz, concerning P.Amh. 2, 186 has the following as an APIS identifier (as unknown.apis.2014-0001, which is what causes it to fall through the boards on submit):

<?xml version="1.0" encoding="UTF-8"?><TEI xmlns="http://www.tei-c.org/ns/1.0">
   <teiHeader>
      <fileDesc>
         <titleStmt>
           <title>Tax Receipt</title>
         </titleStmt>
         <publicationStmt>
            <authority>APIS</authority>
           <idno type="apisid">morgan.apis.1</idno>
           <idno type="TM">39337</idno>
         </publicationStmt>
         <sourceDesc>
            <msDesc>
               <msIdentifier>
                 <idno type="invNo">Amh. Gr. Pap. 186</idno>
               </msIdentifier>
               <msContents>
                 <summary>Tax-receipt written in a small hand with numerous abbreviations. Seventh or eighth century A.D. Complete. 6 lines.</summary>
                 <msItemStruct>
                   <textLang mainLang="grc">Greek</textLang>
                 </msItemStruct>
               </msContents>
               <physDesc>
                  <objectDesc>
                     <supportDesc>
                       <support>9.5 x 7.9 cm</support>
                       <condition>
                        </condition>
                     </supportDesc>
                     <layoutDesc>
                        <layout>
                        </layout>
                     </layoutDesc>
                  </objectDesc>
               </physDesc>
               <history>
                  <origin>
                    <origDate notBefore="0600" notAfter="0799">VII or VIII</origDate>
                    <origPlace>unknown</origPlace>
                  </origin>
                  <provenance>
                    <p>Bib ID 286896. Morgan Library Accession Number Amh. Gr. Pap. 186. Lord Amherst Tyssen-Amherst, 1st Baron Amherst of Hackney; purchased by J. Pierpont Morgan (1837-1913) in 1912; J.P. Morgan (1867-1943).</p>
                  </provenance>
               </history>
            </msDesc>
         </sourceDesc>
      </fileDesc>
      <profileDesc>
         <langUsage>
            <language ident="en">English</language>
            <language ident="la">Latin</language>
            <language ident="el">Greek</language>
         </langUsage>
         <textClass>
            <keywords scheme="#apis">
              <term>Taxes</term>
              <term>Receipt</term>
              <term>
                <rs type="genre_form">Documentary</rs>
              </term>
              <term>
                <rs type="genre_form">Papyrus</rs>
              </term>
            </keywords>
         </textClass>
      </profileDesc>
      <revisionDesc>
        <change when="2014-12-22T11:47:09-05:00" who="http://papyri.info/editor">Automated creation from template</change>
      </revisionDesc>
   </teiHeader>
   <text>
      <body>
         <div type="bibliography" subtype="citations">
            <listBibl>
              <bibl>citation</bibl>
            </listBibl>
         </div>
      </body>
   </text>
</TEI>

No changes have been made to the HGV record, and we don't have an APIS board/folder for the Morgan: https://github.com/papyri/idp.data/tree/master/APIS

Any ideas on what we should do with this publication?

Originally posted by @ryanfb in #62 (comment)
@hcayless
Copy link
Member

hcayless commented Oct 9, 2018

I'd be in favor of outsourcing this sort of thing to TM, except there's not a good path for getting the info into TM. This is probably worth having a discussion with Josh about.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ryanfb @hcayless