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.

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

(greek_conversion) EpiDoc and CTS conversion of Greek in this repo #1399

Open
lcerrato opened this issue Mar 27, 2023 · 78 comments
Open

(greek_conversion) EpiDoc and CTS conversion of Greek in this repo #1399

lcerrato opened this issue Mar 27, 2023 · 78 comments

Comments

@lcerrato
Copy link
Collaborator

standing issue for ongoing work

@lcerrato
Copy link
Collaborator Author

tlg0028 next batch

@lcerrato
Copy link
Collaborator Author

bumped URNs tlg0028

@lcerrato
Copy link
Collaborator Author

tlg0029 bumped

@lcerrato
Copy link
Collaborator Author

tlg0030 underway
@AlisonBabeu The TLG numbers for these speeches seem to vary from the ones we have. Not sure if there is anything we want to do about that or just let it be.

@AlisonBabeu
Copy link
Collaborator

hey @lcerrato this issue came up recently last summer PerseusDL/catalog_data#189 and we had disscussed it back in 2015. I think we ultimately decided to leave Hyperides with the non TLG numbering because of all the legacy linking and other issues. I'm still on the fence about what to do.

@lcerrato
Copy link
Collaborator Author

As long as you knew about it. More than I can say for myself these days!

@AlisonBabeu
Copy link
Collaborator

It is one of those things I know about and then forget for about five years!

@lcerrato
Copy link
Collaborator Author

bumped tlg0030 urns

@lcerrato
Copy link
Collaborator Author

lcerrato commented Mar 31, 2023

tlg0034 work: bumped URN

@lcerrato
Copy link
Collaborator Author

lcerrato commented Apr 3, 2023

tlg0035 work

@lcerrato lcerrato reopened this Apr 3, 2023
@lcerrato
Copy link
Collaborator Author

lcerrato commented Apr 3, 2023

bumped URNs tlg0035

lcerrato added a commit that referenced this issue Sep 30, 2024
@lcerrato
Copy link
Collaborator Author

lcerrato commented Oct 1, 2024

@AlisonBabeu
tlg0527 batch. how should the source description read? this the current version

<sourceDesc>
           <biblStruct>
              <monogr>
                 <author>Rainbow Missions, Inc.</author>
                 <title>World English Bible</title>
                 <editor>Rainbow Missions, Inc.;  revision of the American Standard Version of 1901</editor>
                 <imprint>
                    <pubPlace>http://ebible.org/bible/web</pubPlace>
                 </imprint>
              </monogr>
           </biblStruct>
        </sourceDesc>

@AlisonBabeu
Copy link
Collaborator

hi @lcerrato I've never been entirely certain on this one, but I might go with:

<biblStruct>
<monogr>
<title>World English Bible</title>
<editor>Michael Paul Johnson</editor>
<edition>Revision of the American Standard Version of 1901</edition>
<imprint>
<publisher>Rainbow Missions, Inc.</publisher>
<date>2000-2024</date>
</imprint>
</monogr>
<ref target="http://ebible.org/bible/web">The World English Bible</ref>
</biblStruct>

I've tweaked it after reading through the FAQ on the website, which credits Michael Paul Johnson as the main editor/translator and I don't think author is appropriate for Rainbow MIssions, rather than publisher, so I moved them within the imprint. I was less sure about the date that Perseus first used this version, but went to 2024, since this is an actively maintained website. I also moved the website link to the ref target.

I was least certain about where to put the " <edition>Revision of the American Standard Version of 1901</edition>
I wasn't sure if that should be a note or an edition statement. Not sure if this is even remotely helpful!
I

@lcerrato
Copy link
Collaborator Author

lcerrato commented Oct 1, 2024

@AlisonBabeu
I think it will work! Thank you!

@lcerrato
Copy link
Collaborator Author

lcerrato commented Oct 1, 2024

@AlisonBabeu
We do have a pub place in the catalog (Longmont, CO). Is that still valid?

@AlisonBabeu
Copy link
Collaborator

AlisonBabeu commented Oct 1, 2024

hi @lcerrato I wasn't entirely sure about that, I used that because it was the place listed in the VIAF record for Rainbow Missions Inc. (https://viaf.org/viaf/125688604/#Rainbow_Missions).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants