Hi Jim, yes! Very regular structure!
There would be 3 page types: - images; bug pages and river pages. Each insect get's a simple descriptive bug page with an embedded image; each river page is simply a collection of bug pages in a table (based upon what we have collected from that river). My plan would be to build a preloaded page that would simply launch and partly populate each new page. I'd like to predetermine the file path so that they all start with wikieducator.org/rivers/VTUSA/RiverX for example. The RiverX piece would be the river name for each new stream added and would be in a box filled in by the user. The /VTUSA piece would be in a different box and the whole lot would get strung together to give me some file structure discipline (not a feature of my previous W.E. project). Is there any additional file structure I should put above my "Rivers/" piece? Should I aim for shorter file names or more informative? The bug images come with a natural nested file structure (thanks to Linnaeus). My question: Does it make more sense to load all of the images to Wikimedia commons and use them from there? The Wikimedia folks have a structure for insect images and I'd slot into that. All images used will have been photographed in my lab and I'm willing to share without restriction - some I currently use will have to be rephotographed . If I recall correctly, it is a fairly easy matter to bring WikimediaCommons images into WE. The "Add a row" feature http://wikieducator.org/User:JimTittsler/Data would be very useful! It would give control to the teachers. Right now I make a static web site and if the schools find a new bug they must send it to me to get it added to their web site - so rather clumsy. Cheers, Declan -- You received this message because you are subscribed to the Google Groups "WikiEducator" group. To visit wikieducator: http://www.wikieducator.org To visit the discussion forum: http://groups.google.com/group/wikieducator To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected]
