Web Site To Do List

[hrj]

Just for amusement value, here's this weeks Top 10 Web Site Projects
1. Finish the figure re-drawings for the Shepherd's purse article and get it on-line. (Someone on one of my e-mail lists was asking about the topic, hence the movement to top position.)
2. Continue working on g-g-grandpa Abiel's civil war diaries.
3. Learn how to convert Filemaker databases into the format my web server will handle.
4. Convert the surviving garments database and create a search interface.
5. Start creating the source-material pages for the medieval Welsh clothing section. (This will be a simple presentation of data with minimal commentary -- saving the analysis and synthesis for my planned expanded book.)
6. Create a "dress diary" (retrospectively) for the "party dress".
7. Finish expanding the class notes for the oat cakes class into a stand-alone article.
8. Finish up the research for the variants of the metrical medieval Welsh fealty oaths.
9. Create a site map and index.
10. anybody have requests for #10?

Comments

[wingedcorset.livejournal.com]

More baking for one?

[hrj.livejournal.com]

Hmm, that's a thought. I'm fairly certain I've got more stuff in my notebook that hasn't made it into web form yet. I haven't done any new experiments for a while, though.

[gunnora.livejournal.com]

Are you going to have an active, searchable database created out of your Filemaker stuff? Or more of a static, tabular-type-data thing?

I actually tend to use Excel for any kind of data collation that doesn't have to be relational. If there are no one-to-many relationships, I'm better at writing macros for Excel than for Access (which is the database tool I have on-hand). While I was working on building a database of better info on the Zurich Roll armory, I set up macros in Excel that would, in an automated way, spit out the whole table in a formatted HTML table without all of Microsoft's cr@p code.

But what I need desperately to do now is to learn enough PHP and SQL to allow me to set up a database with the info, then allow a user to search for, say, all the devices with red as a field color and bear(s) as charges. Or whatever. Because as a plain tabular document, the graphic make it enormously too large to look at. Sometime Real Soon Now, I need to break the big HTML table into smaller bits, or make the graphics an option, or something.

I have a sneaking suspicion that there are enough heralds out there who are über tech geeks as well who might be inveigled to help with this project, but I haven't found 'em yet. Or if I have found 'em, they're not susceptible to bribes of lingonberry melomel.

[hrj.livejournal.com]

Oh, definitely active and searchable. That's the whole point. Also, at this point the data is solidly organized as a relational database and it would be more of a pain to turn it into "flat" tables than to learn the necessary SQL. And then there's the matter that there are thousands of records involved ....