What resources are NOT in Paratext 8?

Question

There are many resources that are in ParaTExt 7.5 that are not in ParaTExt 8 yet (as of March 7, 2017). I have not yet found a comprehensive list of what those resources are, nor have I found explicit information about when those resources will become available in the DBL. Things like Translation Notes really should be there, folks! Can anyone tell us what’s going on with this, and what the hold-up might be? Thanks.

Answer 1

The items in this list that have “No” in the “Available in PT8” column:
https://app.smartsheet.com/b/publish?EQBCT=d45dc942d6d54ec2be58fb4868f9f9d7

Comments

The Area coordinators were asked (e.g. Kent for Africa, anon848905 for Americas). Yes, the Hausa Bible is on the list.

anon397352

---

This sheet is authoritative and we are constantly working to update it.

---

I’d like to challenge the thinking that “We cannot upgrade because most of our resources are not available.” I initially thought that way, but I’ve come around to agree that it’s not all that burdensome to resize PT7 and PT8 windows to share the screen, and have them automatically scroll in sync. It comes down to a cost-benefit analysis. If the hassle of managing resources in a different program (PT7 or TW Logos) is outweighed by the new features of PT8 (and I believe it is by FAR), why let it be a barrier?

---

What size screen are you working on, and how many monitors do you use? It’s not hassle free to open up two versions of Paratext and resize them for those who have more conventional laptop displays. My MTT won’t even open TW and Paratext together. He really wants the resources and the drafting window to be open only in one program. For the sake of “buy in”, it’s a hard sale to convince folks that having to open up two programs to do what they used to be able to do with just one is “progress”. Many of the good features that PT8 has are in the area of project management. That would help me manage the project, but that doesn’t really impact the drafting process in significantly better ways that would be evident to our MTT. So, if I want the benefit of those good management tools in PT8, it can’t be at the cost of making drafting more of a hassle for the MTT.

---

+3 for this; thank you for expressing it clearly. A number of the MTTs I work with are still struggling with setting up and using a Combined Text Window, even after 5 years of PT use: If that window gets closed somehow they don't remember how to get it back. We can not make their computer's program/window management any more complicated than it is.

Answer 2

Thanks. But, does anyone know the reason why those resources aren’t available yet? I find it particularly puzzling that SIL resources like TN aren’t available. Why roll out a new software version that gives less in the way of resources? Does anyone know when those resources will be available?

Comments

I cannot give a complete answer, because many organizations are involved, but the crux of the matter is that all resources in Paratext 8 come from the Digital Biblical Library (DBL). There is a back log of converting and uploading resources into the DBL. Eventually, all the SIL owned resources will be uploaded to the DBL and made available to those who need them. Other resources with other copyrights holders will have their own process. Having all resources and active translations tied to the DBL will be a new way of working. All the Bible translation organizations and copyright holders are still adjusting to this new system. Paratext 8 is much more than an upgrade to the user interface of Paratext, but is a movement to a system that uses many more cloud-based systems like the DBL and the Paratext registry.

---

The license for the resources in Paratext 7 ran out for a number of texts which meant we couldn’t keep using them without renegotiating anyway.
Secondly the Paratext 7 licenses gave you access to all or nothing. Giving someone a Paratext license meant giving them access to the resources too. Now the new model gives rights holders more flexibility.
The new system makes adding a new Paratext resource as simple as checking a box in the DBL. But it isn’t the developers who will be checking the boxes.

---

If we have a resource which we’d like to put on DBL and share with a wide audience, allowing it to be downloaded by anyone within a specific organization or even anyone using Paratext, is it possible for us to do that?

Obviously (I hope), in these cases we are either the copyright holder or have permission from the copyright holder.

---

So do you mean that we have to stop using some of the resources we now have in Paratext 7? If so, what resources are you talking about?

---

anon716631, I don’t think in 7 the developers had any way of limiting who had access to a resource once it was released. Thus the license was in effect eternal. They’re using the upgrade to 8 to correct that problem, but don’t really have a way to retroactively correct it in 7. So you will continue to have access to 7 resources for as long as you’re willing to use the old program.

Actually, this brings up something I meant to mention before.

I think there is some confusion here regarding the word ‘resources’. As I see it, there are two different kinds of resources.

There are ‘official’ resources; the Paratext team negotiates the agreement with the publishers and places those resources in the DBL, giving permission for editing to whomever the publisher authorizes.

On the other side, I think there are also things which here I’ll call ‘local’ resources. These are completed or inactive projects which are uploaded via send/receive and shared with one or more teams, currently by adding individuals as members of the project. This requires work by the administrator of the project and (in my context) also raises some security concerns since people can see who the other users of the resource are.

For example, a third party did a translation in a LWC in our country and allowed me to convert it to USFM and share it with a number of teams doing translations in similar languages. In my mind this is a ‘resource’. My question above is about this; can we take this ‘local resource’ and upload it to the DBL? I’m 99% sure the translator would allow this, and would check with him before doing it. However, using the DBL, in the future if someone else wanted access to the resource they could simply search for it using the Download/Install Resource dialogue and wouldn’t need to write me asking for access. If sharing via the DBL is a new feature, I think it is a wonderful addition to the Paratext program.

---

I feel the similar confusion on what we mean by a resource. Any project can also in the future use Send/Recieve to give people an access to their work. You need not to download the text into the DBL in order to do it.

As for the DBL, I think, the system as it now stands, does not mean that when a projects is downloaded to the DBL any PT 8 user can get access to it. The content owner always defines in some level who can and who cannot access her or his text. Thus, “in the future if someone else wanted access to the resource they could simply search for it using the Download/Install Resource dialogue” is valid only if you have given this kind of a permission to “someone” in question.

---

Maybe I wasn’t completely clear in my comment.

I don’t particularly like the PT7 way of sharing what I consider ‘local resources’. Yes, I can upload them with a S/R, but it requires ongoing work on my part to add new users. More importantly, people may want to use the resource but not know it’s available or that they should contact me.

What I’m hoping is that I will be able to share this ‘local resource’ in PT8 not using the S/R dialogue, but instead by uploading it to DBL. What I’m asking is if that is possible, and if it is, how to do it.

---

In order to download something to the DBL you need to be a “DBL archivist”, ie. authorized to do downloading. Authorization means also skills to do it. If you would like to get these rights, you need to talk to the DBL administration, I believe.

---

Here is an online form that may be used if you want to upload a resource to the DBL: https://docs.google.com/a/sil.org/forms/d/e/1FAIpQLSfLaOHQaKaY4TmBiKkGqtHyLI9UlDgiNSiEqCeEb2aC_f-rOg/viewform
But in SIL it is my understanding that DBL submissions have to go through the SIL DBL Curator.

---

Hi,

It’s been good to see this discussion. It highlights some of the facts and issues about resources in Paratext 8 quite well. As dhigby shared, a major goal in the PT8 + DBL effort has been to clarify permissions for use of content as resources in Paratext, to make it easier to make content available (and to update content on user’s machines), and to make additional content available. The restriction is that the content needs to be in DBL.

Responding to the matter of local vs official resources – Send/Receive is not really the intended the way to distribute content for resource use. Official resources in Paratext are intentionally locked down much more than a shared project. This is really a maintenance problem too, and for most cases it is the managing organisation who needs to grant permission.

Regarding getting content in DBL – Yes, there is a more centralized approach (but both UBS and WBT have more than one person helping with this). The requirements for placing projects in DBL are much greater than adding someone to the project with Send/Receive. A project must pass a certain set checks, and have an additional set of metadata associated to it (which will all come from the Registry in PT8). It is not that the process is necessarily hard, but that it has tighter requirements. Generally speaking, what goes into DBL (for the most part) must be ‘publishable’ quality (even if the project is only partially complete). In many ways this is a very good thing - because the content can be shared with partners, and because the content is a solid model (in terms of markup / syntax as well as content).

jmkla

---

Here is the response I got from the SIL DBL Curator when I asked her about DBL submissions:

If you want to get a text into the DBL, you will need to give me access to consultant-checked, final files for texts as small as individual books or as large as the full Bible through a Paratext Send/Receive. You will also need to supply me with the metadata that should accompany the text. A Resource submission must go through the same schema check during upload as a regular text, so must pass the same requirements.

Process:

1. Run Basic Checks (please use Paratext 7.6 if possible, as you will catch more problems)
2. Create a Project Canon (Project/Project Canon - you may need to hold down the Shift key). Add only the books to the Canon that you want to see published in the DBL, even though there may be additional incomplete books in your project.
3. Make sure that all of the books have abbreviation, short name, long name listed in the Scripture Reference Settings. If you have cross references to books that are not in your Project Canon, the names of those books need to be noted in the Scripture Reference Settings.
4. In Project Properties and Settings, make sure that the “Language” dropdown lists the correct language name, and the “Language Identifier” is the iso code for that language.
5. Add me, Lois Gourley, as an Administrator or Archivist to your project, and do a Paratext Send/Receive.

6a. Complete the metadata information at https://docs.google.com/a/sil.org/forms/d/e/1FAIpQLSfLaOHQaKaY4TmBiKkGqtHyLI9UlDgiNSiEqCeEb2aC_f-rOg/viewform for each new project that you are authorized to submit to be shared with our Library Card Holders through the DBL.
6b. Complete the Request to Share form at https://docs.google.com/a/sil.org/forms/d/e/1FAIpQLScV6cmJvWpTG1X0N-srSBPwapG0tmKBYWHZAPdy1Rm3K6Rz2Q/viewform for texts you would like to share as resources.
6c. Complete the Resource Request form found at https://docs.google.com/a/sil.org/forms/d/e/1FAIpQLSdcyW8cmxgr_SG6dKb6I2C5CmRTt7iI-LE1h5M6M95I25DWig/viewform for texts that are owned by other organizations that you would like them to share.

Once I see that a new project is listed on a spreadsheet that is populated by the above mentioned form (6a), I will run Basic Checks to make sure everything is in order, and then will upload to the DBL and will license to YouVersion and Bible Search (and any other Library Card Holder you specify).

If one of your Area/Entity’s texts is already in the DBL, and you have completed the Request to Share form (6b), I will mark it for sharing in the DBL.

If you have completed the Resource Request form (6c), I will request that text on your behalf.

---

Actually, you can share “local” resources (a colleague’s project, ongoing or completed) simply by passing on a backup of them which people restore to their machine in PT. And a restored project like that can also be migrated. To me, that is a lot more hassle free than using S/R or DBL uploads.

Answer 3

Shegnada,

This went to the area level Language Technology Consultants. I’ve added it to the spreadsheet for you.

Blessings,
anon848905

Answer 4

Should the NET Bible and NLT be changed to “Available in PT8”? I downloaded them in PT8 from the DBL this week. REALLY glad they’re available now!

Thanks,

SIL+LSS+PNG

Comments

Thanks, I’ll update the sheet.

⁣Sent from TypeApp ​

---

I sure wish information like this wasn’t locked into some ‘cloud’ service thingy… I’ve been waiting over 15 minutes for ‘Smartsheet’ to load the list. Twice I have gotten the message:

“It is taking longer than normal to load Smartsheet. In certain cases, a network or internet anomaly will prevent Smartsheet from loading. Press the Refresh button on your browser to re-load Smartsheet. Please contact Smartsheet.com if this condition persists.”

There’s irony in the request for someone with a poor internet connection to navigate to a website to contact the service provider about connection issues with their site.
Is there another way to access this list? Thanks,
Paul

---

Hi Paul,

I’ve created a faster HTML only link: http://publish.smartsheet.com/98487b07b58f4d1aaadc49f4bbf468a5
Just for you!

---

Is this just for Paul, or can we use it too?

It loaded MUCH faster over here in PNG.

Thank you dhigby,

SIL+LSS+PNG

---

Well, PNG wins… I hope I don’t sound whiny, but how big is the page that the HTML link refers to? I’ve tried three times: first 4 minutes, then 5 minutes, and the third try I’m up to ten minutes, but still nothing. My internet is working, as is evident by that fact that I’ve been able to navigate to the support.paratext.org website (which took three minutes) and send this message.

Still looking for a solution…

Paul

---

I see Good News Arabic (GNA93) highlighted in green, but I cannot find it inside of PT8 as a downloadable resource. My license is through SIL Eurasia so I think I should be included in the FOBAI user category.

In general, if there is a resource we think ought to be included, who do we contact to ask about that?

---

Apparently when the language was named for this project in the DBL it was
labeled “Standard Arabic” rather than “Arabic Standard” like some of the
others. If you sort by “Full Name” you should be able to locate it under
"Good News Arabic".

This brings up an important issue - the language names are not always the
best way to look for resources. There has already been requests and
discussion for better search/filter capabilities in the download window.

anon848905
Americas Area Language Technology Coordinator
[Email Removed]
[Phone Removed] at JAARS)
[Phone Removed]Cell)
Skype name: anon848905

---

Thanks, I found it.

Is this sort of minor mistake–“Standard Arabic” and “Arabic (Standard)”–something we should report inside Paratext, or will it be corrected in some other way?

---

I know that the developers have already worked on this, so the feature to
filter results based on word(s) searched for is on its way… Hoping that
it will be released sooner rather than later.

---

Mark+P:

Hoping that it will be released sooner rather than later.

Unfortunately, this was pushed to 8.1 because of the amount of code changes needed to implement it (but the coding has already been done).

mnjames:

Is this sort of minor mistake–“Standard Arabic” and “Arabic (Standard)”–something we should report inside Paratext, or will it be corrected in some other way?

We’ve looked into options to standardize the language names inside Paratext by looking at the language codes, but none of the solutions have worked well. A lot of language codes are associated with multiple names, and the language codes in DBL seem to not be correct all the time, either.

I think this means that it has to be fixed in DBL on a case-by-case basis.

Answer 5

The Old Persian Version is available in YouVersion, but not in PT8. It was published in 1895, so must have been out of copyright for about a century. Is there any reason that it’s not been made available in PT8?

Comments

In order for a text to be added to Paratext it must be in the DBL. You can see what is in the DBL by going to: https://thedigitalbiblelibrary.org/whats-inside/

In this case someone would have to add the Old Persian text to the DBL and then share it with Paratext.

---

anon848905:

In order for a text to be added to Paratext it must be in the DBL.

If it’s in YouVersion, doesn’t that mean it must be in the DBL?

---

wdavidhj:

If it’s in YouVersion, doesn’t that mean it must be in the DBL?

YouVersion does get texts from the DBL and changes them into their internal format for use in their tools, but they don’t exclusively get their resources from the DBL.

---

Right, The Old Persian Version is not listed at the link that @anon848905 pointed me to (above).