kim, personally i think you should create a webpage; in principle a
wiki is a collaborative venture, with several to many different
people contributing/collaborating. although you can in fact control
access (password) and therefore decide who can edit or create/delete
pages etc, but you seem to need "fixed" data that will be updated
from time to time. a webpage on your site would be the best, then it
is also stylistically linked to the "look" of your site; each wiki
has its own style conventions, and even editing conventions.
that said, if you decide to go for a wiki, i would encourage you to look into:
http://pbwiki.com
i use it with some colleagues for administrative tasks and
information that we all edit (wiki is set to "private") and have also
built a number of pages on a publicly-available wiki for the CEC
<http://cecpublic.pbwiki.com> which helped me gather small bits of
information from a large variety of contributors that would have been
too diffifult and time consuming for me to do myself. the owners of
pbwiki are very good about communications and they are constantly
improving the interface and functionality. i found it a very easy to
use wiki.
DB programmes usually come with a number of templates that might
already be enough for your needs and therefore not require
undertaking any difficult training or whatever; i don't know Access,
but know it is an excellent programme but seems to have a steep
learning curve. in order to use filemaker (don't know for Access) on
a server you have to have FM Server, which is another programme, and
i think quite a bit more expensive as well, but not sure. your
server has to allow you to install programmes, or something; but i
don't know much about that end of things, really.
jef
_______________________________________________
Finale mailing list
[email protected]
http://lists.shsu.edu/mailman/listinfo/finale
