add paratext systemId elements to metadata 2.1.1

[ericpyle]

In metadata 2.1.1:

<systemId type="paratext">
    <projectType>Auxiliary</projectType>
    <basedOn>
           <name>engWEB14</name>
            <id>9879dbb7cfe39e4d5d6f7f9dbd0c6414691a036e</id>
    </basedOn>
</systemId>

Where optional <projectType> can be Standard|Daughter|StudyBible|StudyBibleAdditions|BackTranslation|Auxiliary|TransliterationManual|TransliterationWithEncoder|ConsultantNotes|GlobalConsultantNotes|GlobalAnthropologyNotes

Where optional <basedOn> has required <name> (lenGe2String) and required <id> (ptId)`

In text metadata 1.5:

<systemId type="paratext"  
projectType="Auxiliary" 
basedOnName="engWEB14"
basedOnId="9879dbb7cfe39e4d5d6f7f9dbd0c6414691a036e"></systemId>

[ericpyle]

see also #8 (review) (under ## add new elements to text metadata 2.0 under to capture alternative project types)

[ericpyle]

@klassenjm how should we proceed on this to unblock Lois who is trying to upload to DBL a (transliteration) project that has already been uploaded? (https://thedigitalbiblelibrary.org/entry?id=19b20027201977c5)

1. I can remove (at least partially) my restriction in Paratext from uploading projects with a basedOn text.
2. We can prioritize fixing 1.5 and 2.1.1 to support basedOn elements to capture metadata for these types of uploads.

[klassenjm]

My current thoughts:

That we not support upload of the following as regular DBL entries (resource only uploads excepted):

• StudyBibleAdditions
• ConsultantNotes
• GlobalConsultantNotes
• GlobalAnthropologyNotes

It would be very nice if we could retain basedOn. What do we capture there? The PT project GUID? a name? If we could capture the GUID and see if that was already an entry in DBL - and then set up a relation in the DBL metadata -- would that be good? (I think so -- but I don't feel like I want to come across as though it's a requirement yet).

[mvahowe]

@ericpyle @klassenjm Could we do this on the wishlist so we have some hope of finding the discussion when we come to make the decisions? https://github.com/ubsicap/dbl-archive-validation/blob/master/v2/2_1_1/wishlist.md

[klassenjm]

Yes

[ericpyle]

@klassenjm I know that Biblica and others were hoping we'd support Auxiliary, so they have a workflow that supports forking active projects before uploading it to DBL. I don't remember where that discussion landed given that PT Registry does not host those projects, except that perhaps the PT uploader could potentially borrow the needed metadata from basedOn (unless that just is not workable in all cases).

also fwiw, DBL already has GlobalAnthropologyNotes as resourceOnly. Certainly the PT uploader should have certain precautions about projects that typically get uploaded, but resourceOnly does allow non-typical projects. We aren't technically running the same schema validation for resourceOnly uploads, but at the same time we are using the same metadata structure for transporting metadata with resourceOnly uploads.