Probably posting this in the wrong place, but anyway.
(Moderators, move it to wherever you think is most appropriate.)
http://www.biblesupp...word-resources/
is a PDF. Personally, I can't read that PDF. The data it contains simply doesn't make sense to me.
(The data in the spreadsheet does make sense to me.)
Question 1:
Just how useful are resource lists that were created, and maintained in a spreadsheet.
What would make it easier for people to utilize the data in those lists.
[ AFAIK, Josh has a ban on file formats other than PDF, SQLite, and ZIP compression. ]
Creating/migrating resource lists to an SQLite file --- which is how they should have been done in the first place --- is an option. The major/only objection to distribution of the SQLite file, is the difficulty most (?) people have in reading data in SQLite files. The obvious solution --- write a program to read the database --- is not one that I want to engage in, at this point in time.
Asking, because I'm thinking seriously about creating lists of resources for several other Biblical Software programs. I will publicly distribute these lists, if other people can understand, and use them.
Question 2:
In an ideal world, which Biblical software programs would it be most useful to have a list of available resources, and where they could be obtained from?
### Caution: Tech Talk Ahead ###
Database specification:
Resource_Table:
- ID_Number: Autonumber. Used to track records. Makes it easier to add/edit/delete data;
- Program: Biblical software program the resource is for;
- Version_Number: Version number of the software that the resource is for;
- Resource_Name: Name of the resource. EG: KJVA, NRSV-CE;
- Resource_Type: Type of resource: Bible, Commentary, etc. Terms are restricted to the program the resource is used by;
- Cost: How much the resource sells for;
- Vendor: Who sells/distributes the resource;
- URL: Website that offers the resource;
- Date_Added: Date the resource was publicly released;
- Date_Removed: Date the resource was withdrawn from distribution;
- ID_Number: Autonumber. Used to track records. Makes it easier to add/edit/delete data;
- Date_of_Update: Date the database was last changed;
- What_was_updated: What was changed: Resources added, Resources verified, etc;
jonathon
