I have just uploaded new packages for the Hebrew Lexicon and BDB Outline. I am about 40% finished with a systematic update, going through BDB, checking the BDB Outline and updating the lexicon. We now have over 70% of the BDB entries updated in one form or another.
Parts of speech are being added to all the entries, as I come across them. Some older entries have been expanded, especially adding stems to verbs that have more than one stem in BDB. In the BDB Outline, a few corrections have been necessary, but the main thrust is adding @aug to the augmented Strong numbers, to map to the lexicon and the WLC.
BdbOutline.xsd has been expanded accordingly.
On Apr 28, 4:59 pm, David Troidl <DavidTro...@aol.com> wrote:
> Hi All,
> I have just uploaded new packages for the Hebrew Lexicon and BDB
> Outline. I am about 40% finished with a systematic update, going
> through BDB, checking the BDB Outline and updating the lexicon. We now
> have over 70% of the BDB entries updated in one form or another.
> Parts of speech are being added to all the entries, as I come across
> them. Some older entries have been expanded, especially adding stems to
> verbs that have more than one stem in BDB. In the BDB Outline, a few
> corrections have been necessary, but the main thrust is adding @aug to
> the augmented Strong numbers, to map to the lexicon and the WLC.
> BdbOutline.xsd has been expanded accordingly.
Any chances for having script to make SQL friendly data?
> On Apr 28, 4:59 pm, David Troidl<DavidTro...@aol.com> wrote:
>> Hi All,
>> I have just uploaded new packages for the Hebrew Lexicon and BDB
>> Outline. I am about 40% finished with a systematic update, going
>> through BDB, checking the BDB Outline and updating the lexicon. We now
>> have over 70% of the BDB entries updated in one form or another.
>> Parts of speech are being added to all the entries, as I come across
>> them. Some older entries have been expanded, especially adding stems to
>> verbs that have more than one stem in BDB. In the BDB Outline, a few
>> corrections have been necessary, but the main thrust is adding @aug to
>> the augmented Strong numbers, to map to the lexicon and the WLC.
>> BdbOutline.xsd has been expanded accordingly.
> Any chances for having script to make SQL friendly data?
I don't really do SQL. Depending on what you're trying to achieve, it could be either simple of very intricate. If all you want is to be able to reference an entry stored in a database, that should be straightforward. If you want to be able to search all the fields, that would be a challenge. Neither BDB, nor my XML markup of it, has a very database-friendly structure. You might be better off thinking in terms of an XML database, if you want that level of control.
I have plans to write a Python script that will convert the XML into a
Python dictionary. From there, it is on my radar to import it into a SQL
database. I'm not sure when I'll have the time to put this together, but
it is something I'm looking to do.
On Tue, May 1, 2012 at 6:19 AM, David Troidl <DavidTro...@aol.com> wrote:
> Hi,
> On 4/30/2012 9:05 AM, evstevemd wrote:
>> Hi Dave,
>> On Apr 28, 4:59 pm, David Troidl<DavidTro...@aol.com> wrote:
>>> Hi All,
>>> I have just uploaded new packages for the Hebrew Lexicon and BDB
>>> Outline. I am about 40% finished with a systematic update, going
>>> through BDB, checking the BDB Outline and updating the lexicon. We now
>>> have over 70% of the BDB entries updated in one form or another.
>>> Parts of speech are being added to all the entries, as I come across
>>> them. Some older entries have been expanded, especially adding stems to
>>> verbs that have more than one stem in BDB. In the BDB Outline, a few
>>> corrections have been necessary, but the main thrust is adding @aug to
>>> the augmented Strong numbers, to map to the lexicon and the WLC.
>>> BdbOutline.xsd has been expanded accordingly.
>>> Any chances for having script to make SQL friendly data?
> I don't really do SQL. Depending on what you're trying to achieve, it
> could be either simple of very intricate. If all you want is to be able to
> reference an entry stored in a database, that should be straightforward.
> If you want to be able to search all the fields, that would be a
> challenge. Neither BDB, nor my XML markup of it, has a very
> database-friendly structure. You might be better off thinking in terms of
> an XML database, if you want that level of control.
> Peace,
> David
> Peace,
>>> David
> --
> You received this message because you are subscribed to the Google Groups
> "Open Scriptures" group.
> To post to this group, send email to openscriptures@googlegroups.**com<openscriptures@googlegroups.com>
> .
> To unsubscribe from this group, send email to openscriptures+unsubscribe@*
> *googlegroups.com <openscriptures%2Bunsubscribe@googlegroups.com>.
> For more options, visit this group at http://groups.google.com/** > group/openscriptures?hl=en<http://groups.google.com/group/openscriptures?hl=en>
> .
On Tuesday, May 1, 2012 8:55:24 AM UTC-6, JAG3773 wrote:
> I have plans to write a Python script that will convert the XML into a > Python dictionary. From there, it is on my radar to import it into a SQL > database. I'm not sure when I'll have the time to put this together, but > it is something I'm looking to do.
> Thanks, > Jesse
> On Tue, May 1, 2012 at 6:19 AM, David Troidl <DavidTro...@aol.com> wrote:
>> Hi,
>> On 4/30/2012 9:05 AM, evstevemd wrote:
>>> Hi Dave,
>>> On Apr 28, 4:59 pm, David Troidl<DavidTro...@aol.com> wrote:
>>>> Hi All,
>>>> I have just uploaded new packages for the Hebrew Lexicon and BDB >>>> Outline. I am about 40% finished with a systematic update, going >>>> through BDB, checking the BDB Outline and updating the lexicon. We now >>>> have over 70% of the BDB entries updated in one form or another.
>>>> Parts of speech are being added to all the entries, as I come across >>>> them. Some older entries have been expanded, especially adding stems to >>>> verbs that have more than one stem in BDB. In the BDB Outline, a few >>>> corrections have been necessary, but the main thrust is adding @aug to >>>> the augmented Strong numbers, to map to the lexicon and the WLC. >>>> BdbOutline.xsd has been expanded accordingly.
>>>> Any chances for having script to make SQL friendly data?
>> I don't really do SQL. Depending on what you're trying to achieve, it >> could be either simple of very intricate. If all you want is to be able to >> reference an entry stored in a database, that should be straightforward. >> If you want to be able to search all the fields, that would be a >> challenge. Neither BDB, nor my XML markup of it, has a very >> database-friendly structure. You might be better off thinking in terms of >> an XML database, if you want that level of control.
>> Peace,
>> David
>> Peace,
>>>> David
>> -- >> You received this message because you are subscribed to the Google Groups >> "Open Scriptures" group. >> To post to this group, send email to openscriptures@googlegroups.**com<openscriptures@googlegroups.com> >> . >> To unsubscribe from this group, send email to openscriptures+unsubscribe@ >> **googlegroups.com <openscriptures%2Bunsubscribe@googlegroups.com>. >> For more options, visit this group at http://groups.google.com/** >> group/openscriptures?hl=en<http://groups.google.com/group/openscriptures?hl=en> >> .
That is a start. That script only imports the definitions for words into a
Python dictionary. The next steps are importing all of the XML data into
the dictionary and then dumping that data into a database.
Technically the data could just go straight into a SQL database, but I have
some unrelated plans that would make use of the Python dictionary.
Mainly it's the amount of free time that I don't have which slows the
progress here. If you, or anyone else, wanted to augment that script, feel
free! The main change that needs to happen is that currently the word is
the dictionary key, but the entry id field should probably be the key.
> On Tuesday, May 1, 2012 8:55:24 AM UTC-6, JAG3773 wrote:
>> I have plans to write a Python script that will convert the XML into a
>> Python dictionary. From there, it is on my radar to import it into a SQL
>> database. I'm not sure when I'll have the time to put this together, but
>> it is something I'm looking to do.
>> Thanks,
>> Jesse
>> On Tue, May 1, 2012 at 6:19 AM, David Troidl <DavidTro...@aol.com> wrote:
>>> Hi,
>>> On 4/30/2012 9:05 AM, evstevemd wrote:
>>>> Hi Dave,
>>>> On Apr 28, 4:59 pm, David Troidl<DavidTro...@aol.com> wrote:
>>>>> Hi All,
>>>>> I have just uploaded new packages for the Hebrew Lexicon and BDB
>>>>> Outline. I am about 40% finished with a systematic update, going
>>>>> through BDB, checking the BDB Outline and updating the lexicon. We now
>>>>> have over 70% of the BDB entries updated in one form or another.
>>>>> Parts of speech are being added to all the entries, as I come across
>>>>> them. Some older entries have been expanded, especially adding stems
>>>>> to
>>>>> verbs that have more than one stem in BDB. In the BDB Outline, a few
>>>>> corrections have been necessary, but the main thrust is adding @aug to
>>>>> the augmented Strong numbers, to map to the lexicon and the WLC.
>>>>> BdbOutline.xsd has been expanded accordingly.
>>>>> Any chances for having script to make SQL friendly data?
>>> I don't really do SQL. Depending on what you're trying to achieve, it
>>> could be either simple of very intricate. If all you want is to be able to
>>> reference an entry stored in a database, that should be straightforward.
>>> If you want to be able to search all the fields, that would be a
>>> challenge. Neither BDB, nor my XML markup of it, has a very
>>> database-friendly structure. You might be better off thinking in terms of
>>> an XML database, if you want that level of control.
>>> Peace,
>>> David
>>> Peace,
>>>>> David
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Open Scriptures" group.
>>> To post to this group, send email to openscriptures@googlegroups.**co**m<openscriptures@googlegroups.com>
>>> .
>>> To unsubscribe from this group, send email to
>>> openscriptures+unsubscribe@**goo**glegroups.com<openscriptures%2Bunsubscrib e@googlegroups.com>
>>> .
>>> For more options, visit this group at http://groups.google.com/**group** >>> /openscriptures?hl=en<http://groups.google.com/group/openscriptures?hl=en>
>>> .
> To post to this group, send email to openscriptures@googlegroups.com.
> To unsubscribe from this group, send email to
> openscriptures+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/openscriptures?hl=en.
On Tuesday, May 1, 2012 9:28:05 AM UTC-6, JAG3773 wrote:
> Seth,
> That is a start. That script only imports the definitions for words into > a Python dictionary. The next steps are importing all of the XML data into > the dictionary and then dumping that data into a database.
> Technically the data could just go straight into a SQL database, but I > have some unrelated plans that would make use of the Python dictionary.
> Mainly it's the amount of free time that I don't have which slows the > progress here. If you, or anyone else, wanted to augment that script, feel > free! The main change that needs to happen is that currently the word is > the dictionary key, but the entry id field should probably be the key.
> Thanks, > Jesse
> On Tue, May 1, 2012 at 9:19 AM, Seth Washeck <swash...@gmail.com> wrote:
>> On Tuesday, May 1, 2012 8:55:24 AM UTC-6, JAG3773 wrote:
>>> I have plans to write a Python script that will convert the XML into a >>> Python dictionary. From there, it is on my radar to import it into a SQL >>> database. I'm not sure when I'll have the time to put this together, but >>> it is something I'm looking to do.
>>> Thanks, >>> Jesse
>>> On Tue, May 1, 2012 at 6:19 AM, David Troidl <DavidTro...@aol.com>wrote:
>>>> Hi,
>>>> On 4/30/2012 9:05 AM, evstevemd wrote:
>>>>> Hi Dave,
>>>>> On Apr 28, 4:59 pm, David Troidl<DavidTro...@aol.com> wrote:
>>>>>> Hi All,
>>>>>> I have just uploaded new packages for the Hebrew Lexicon and BDB >>>>>> Outline. I am about 40% finished with a systematic update, going >>>>>> through BDB, checking the BDB Outline and updating the lexicon. We >>>>>> now >>>>>> have over 70% of the BDB entries updated in one form or another.
>>>>>> Parts of speech are being added to all the entries, as I come across >>>>>> them. Some older entries have been expanded, especially adding stems >>>>>> to >>>>>> verbs that have more than one stem in BDB. In the BDB Outline, a few >>>>>> corrections have been necessary, but the main thrust is adding @aug to >>>>>> the augmented Strong numbers, to map to the lexicon and the WLC. >>>>>> BdbOutline.xsd has been expanded accordingly.
>>>>>> Any chances for having script to make SQL friendly data?
>>>> I don't really do SQL. Depending on what you're trying to achieve, it >>>> could be either simple of very intricate. If all you want is to be able to >>>> reference an entry stored in a database, that should be straightforward. >>>> If you want to be able to search all the fields, that would be a >>>> challenge. Neither BDB, nor my XML markup of it, has a very >>>> database-friendly structure. You might be better off thinking in terms of >>>> an XML database, if you want that level of control.
>>>> Peace,
>>>> David
>>>> Peace,
>>>>>> David
>>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Open Scriptures" group. >>>> To post to this group, send email to openscriptures@googlegroups.**co** >>>> m <openscriptures@googlegroups.com>. >>>> To unsubscribe from this group, send email to >>>> openscriptures+unsubscribe@**goo**glegroups.com<openscriptures%2Bunsubscrib e@googlegroups.com> >>>> . >>>> For more options, visit this group at http://groups.google.com/**group* >>>> */openscriptures?hl=en<http://groups.google.com/group/openscriptures?hl=en> >>>> .
>> To post to this group, send email to openscriptures@googlegroups.com. >> To unsubscribe from this group, send email to >> openscriptures+unsubscribe@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/openscriptures?hl=en.
