01c Editing Module Properties General Properties

This second part of the editing Module Properties Class will look at the essential information in the Module Properties tab. Once you right click on a module’s name in the module tab about it, then you will see the image below. Here in “Darby’s Dictionary” (posts November 12, 2017) from theword-dictionaries.com , you will see the Darby Dictionary information as an example.

More Articles from this Category





Cummings Through the Eternal Spirit: A Biblical Study on the Holy Ghost is a 25 chapter work on the Holy Spirit from 1896. NT and OT verses. Some Chapters: 4. The Spirit in the Word, 7. Pentecost: What it was, and what it did, 9. What Pentecost was for the church, 10. Pentecost in relation to the individual believer now, 11. "Baptism in the Spirit:" His being received, His "falling" on men, and other expressions. 21. Power. 23. Temples of the Holy Spirit. 315 pages.
theWord Format: Cummings Through the Eternal Spirit
PDF Format: Cummings Through the Eternal Spirit
eSword Format: Cummings Through the Eternal Spirit
MySword Format: Cummings Through the Eternal Spirit

The first thing that we note is some fields are locked (System properties), so these are information about the module that is not editable. Things such as its type, the content type, the actual route and filename of the module, and its size, is it encrypted, etc.

Now we proceed to the System properties section.

As I mentioned before, the first ones here are set by theWord reading the module and reporting what the status with the module. These fields are Type, Content type, Filename, Size, Encrypted.




Module Identifier.

This is a unique Identifier. If you make very many modules, I would suggest that you write Costas and get a block of module Identifier numbers. The module identifier is how theWord distinguishes one module from another module. It doesn’t use module names but rather the Module Identifier number within the module itself. By default, the filename is used until you put something else in there.




Why is a module Identifier Important.

Say you make a module of Arthur Pink’s Attributes of God work. You leave the module Identifier blank so the default is used.

Now later on you find somebody else’s module of Pink’s work, and somebody comments that your version has something different from his, or you just download it not remembering that you already made a module with that name (whether anything is in it or not doesn’t matter). theWord is now confused with two modules with the same identifier, and unpredictable results can happen. It may jump back and forth between the two modules, and if they are different in any way, again, things may get unpredictable.

If you try to make a link to that module without a module identifier, then tw will not let you make the link.

So putting in a module identifier is important. Costas will give you an identifier or a block of identifier numbers if you just ask, and it is free.




Category:

This field is for the general category of what the module is, say a work on Inspiration, then Bibliology would be a good category. This is used internally in your module layout sets only, so whatever you put is not really going to break anything if you miscategorize it or leave it blank.

Keywords:

I can say the same here. It is another subdivision of keywords that would help other people know what things are in the work so that they can know if it is valuable to them or not.

Module Creator:

If you created the module, this is where you would put your name and email. This is extremely important if you make a module and then encrypt it. Nobody else can make corrects if they find them, and since you have encrypted it, you lock the thing from anybody else making the corrections either. Bad!

Also if there are questions about copyright issues, there is nowhere to write if you leave this blank. Sometimes people just want to say thanks.




Editorial Comments and Version History:

Sometimes you may make a module quickly, and forget to format things, and then later on open it up and think, how horrible! So you fix it. This box allows people to know what you have done in a new version. In a very few cases, I have found it extremely helpful. For example, I made a module one time which the text that I found on the Internet, apparently was lacking 3 chapters, and the following chapters had their chapter numbers changed, and I never figured that out. Somebody wrote me (See field above), and I was able to add the missing chapters. In another case my original text was missing the last half of the last chapter. Somebody found a copy and sent it to me and I updated that module moving the version number to 1.2.

When I write something myself, I also come back later on, and add double the amount of material of the first version, and here I changed the version number to 2.0. All of this can be documented in this box, as to the details of what has been done editorially to the module. At times I pick up the footnotes and put them in paratheses or brackets in the text. That note should be in the editorial comments box.

Get this series of posts in PDF format

Guide 1040
Guide 1040 » Post
guide_1040.pdf
14.0 MiB
3942 Downloads
Details
Simple Bible Reader
Simple Bible Reader » Post
Simple_Bible_Reader_3.0.exe
Version: 3.0
1.4 MiB
6955 Downloads
Details
Simple-bible-reader-user-guide-v2-4
Simple-bible-reader-user-guide-v2-4 » Post
simple-bible-reader-user-guide-v2-4.pdf
Version: 2.4
1.1 MiB
3081 Downloads
Details
ToolTip NT
ToolTip NT » Post
ToolTip-NT-2.10.pdf
Version: 2.10
5.3 MiB
3940 Downloads
Details
ToolTipToolSetup
ToolTipToolSetup » Post
ToolTipToolSetup.zip
4.6 MiB
263 Downloads
Details